-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/keycloak] KEYCLOAK_HOSTNAME present even if KEYCLOAK_PROXY_HEADERS is set #30368
base: main
Are you sure you want to change the base?
Conversation
…o the config map should not be set. Signed-off-by: Renaud Demarneffe <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @RDemarneffe for your contribution.
I've just left a comment. Maybe I didn't understand the issue but I think the condition you set is almost the opposite. BTW Could you provide an scenario to reproduce the issue and test your changes?
# Conflicts: # bitnami/keycloak/CHANGELOG.md # bitnami/keycloak/Chart.yaml
Signed-off-by: Renaud Demarneffe <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @RDemarneffe for your contribution!
I reproduced the issue you mentioned in #30368 and how these changes fix it. But I have a couple of doubts below, Could you give them a glance?
@@ -35,7 +35,7 @@ data: | |||
{{- include "common.tplvalues.render" (dict "value" $path "context" $) }} | |||
{{- end }} | |||
{{- end }} | |||
{{- if and .Values.ingress.enabled .Values.ingress.hostname }} | |||
{{- if and .Values.ingress.enabled .Values.ingress.hostname (empty .Values.proxyHeaders) }} | |||
KEYCLOAK_HOSTNAME: |- | |||
{{ ternary "https://" "http://" ( or .Values.ingress.tls (eq .Values.proxy "edge") (not (empty .Values.proxyHeaders)) ) -}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here proxyHeaders
will be always empty, so we can remove it:
{{ ternary "https://" "http://" ( or .Values.ingress.tls (eq .Values.proxy "edge") (not (empty .Values.proxyHeaders)) ) -}} | |
{{ ternary "https://" "http://" ( or .Values.ingress.tls (eq .Values.proxy "edge") ) -}} |
@@ -35,7 +35,7 @@ data: | |||
{{- include "common.tplvalues.render" (dict "value" $path "context" $) }} | |||
{{- end }} | |||
{{- end }} | |||
{{- if and .Values.ingress.enabled .Values.ingress.hostname }} | |||
{{- if and .Values.ingress.enabled .Values.ingress.hostname (empty .Values.proxyHeaders) }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it apply to KEYCLOAK_HOSTNAME_ADMIN also?
charts/bitnami/keycloak/templates/configmap-env-vars.yaml
Lines 24 to 25 in 6ec5f91
{{- if and .Values.adminIngress.enabled .Values.adminIngress.hostname }} | |
KEYCLOAK_HOSTNAME_ADMIN: |- |
Description of the change
When the helm proxyHeaders variable is set, the KEYCLOAK_HOSTNAME into the config map should not be set.
Benefits
Improve chart to respect the keycloak documentation.
Possible drawbacks
None
Applicable issues
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm