fix(helm): let the backend fetch Keycloak keys from inside the cluster - #257
Merged
Conversation
The backend looked up its login keys at the public address (auth.<domain>), which only works once DNS, the ingress and the TLS certificate all exist. On a fresh cluster none of them do, so the lookup failed and every logged-in request was rejected — while the pod still looked healthy. It now asks Keycloak directly, pod to pod. The issuer url stays public, because that is the address written inside the tokens. Fails at install time with a clear message if Keycloak is not part of the release, since then there is no pod to ask.
sabinem
marked this pull request as draft
August 27, 2026 05:00
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
2 participants
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.
The backend looked up its login keys at the public address (auth.), which only works once DNS, the ingress and the TLS certificate all exist. On a fresh cluster none of them do, so the lookup failed and every logged-in request was rejected — while the pod still looked healthy.
It now asks Keycloak directly, pod to pod. The issuer url stays public, because that is the address written inside the tokens.
Fails at install time with a clear message if Keycloak is not part of the release, since then there is no pod to ask.