Repository navigation
Unify CA certificates and cover the OIDC provider - #442
Open
Bohreromir wants to merge 2 commits into
Open
Bohreromir wants to merge 2 commits into
Bohreromir wants to merge 2 commits into
Conversation
Replace the per-service CA settings for Trino, PostgreSQL and S3 with STACKABLE_COCKPIT_TLS_CA_CERTS (Helm: tls.caCerts, tls.secretClasses). The CAs are added to the process-wide default trust store, so every outgoing TLS connection, including the OIDC provider, trusts them while publicly trusted endpoints keep working. A missing or invalid certificate now stops the server at startup. Add /readyz, used by the Helm readiness probe: it fails until the OIDC discovery document has been fetched once, and the log names the cause, e.g. an untrusted provider certificate. Warn in production when Trino TLS verification is disabled. Closes #383
Bohreromir
marked this pull request as ready for review
November 9, 2026 09:52
Bohreromir
changed the title
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
labrenbe
self-requested a review
November 10, 2026 15:33
labrenbe
requested changes
Nov 11, 2026
labrenbe
left a comment
labrenbe
left a comment
Member
There was a problem hiding this comment.
Looks good in general, but I'm not so sure about the readiness gate. Maybe that should also be a separate PR?
| /** | ||
| * Fetches the discovery document. Returns true once it has succeeded: afterwards | ||
| * better-auth has (or retries) the provider metadata, so a later outage of the | ||
| * provider doesn't take the cockpit out of service for users with a session. |
Member
There was a problem hiding this comment.
This is only true if the cockpit Pod doesn't restart. If the Pod restarts while the OIDC provider is not available it won't become ready and users can't continue their sessions. It might be ok to just error on misconfiguration.
Member
Author
There was a problem hiding this comment.
Yes, makes sense regarding the readyz. That probably deserves another more intense look so I removed it.
labrenbe
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the per-service CA settings for Trino, PostgreSQL and S3 with STACKABLE_COCKPIT_TLS_CA_CERTS (Helm: tls.caCerts, tls.secretClasses). The CAs are added to the process-wide default trust store, so every outgoing TLS connection, including the OIDC provider, trusts them while publicly trusted endpoints keep working.
Closes #383
Description
Docs
Release note
Checklist
Author
Reviewer
Acceptance