-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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] Admin URL no longer works for chart versions higher than 21.0.2 #25963
Comments
Hi, Here are the chart values used: httpRelativePath: /auth/
ingress:
annotations:
kubernetes.io/ingress.class: nginx
nginx.org/location-snippets: |
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Forwarded-Port 443;
nginx.org/proxy-buffer-size: 128k
nginx.org/proxy-buffers: 4 256k
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
cert-manager.io/issuer: cert-issuer
enabled: true
hostname: …
path: /
pathType: Prefix
tls:
- hosts:
- ...
secretName: cert-secret
adminIngress:
annotations:
kubernetes.io/ingress.class: nginx
enabled: true
hostname: …
path: /auth/admin
pathType: Prefix
tls:
- hosts:
- …
secretName: cert-secret Thanks for your help. |
I just reviewed the changes from 21.0.4 to 21.1.0 and saw that since then the env variables
If I'm not mistaken, it seems that the path defined in the ingress or in httpRelativePath is not used in this context. Is this an oversight, or am I misunderstanding the configuration of the environment variables? |
Any update ? |
Thanks for the investigation you did, @bjsee. I can see this in Keycloak's documentation:
Have you tried adding your |
Hi @alemorcuq, I've been trying all morning to adjust the values but nothing works, even adjusting httpRelativePath to KC_HOSTNAME_ADMIN_URL... Can you reproduce my environment? |
Hi, it is introduced by the commit: #25386. I'm impacted too. |
No updates? |
Waiting too. In the meantime, Keycloak updates are blocked... |
Name and Version
bitnami/keycloak:21.2.1
What architecture are you using?
None
What steps will reproduce the bug?
Here is my values.yaml :
What do you see instead?
https://keycloak-dr-admin.company.net/admin/ returns :
404: Not Found
Additional information
I tried to upgrade from bitnami/keycloak:21.0.2 to bitnami/keycloak:21.2.1.
This added a new discovery port as well as a change on the tls part of the admin ingress, however I do not notice any typo.
Here are the pod startup logs :
Thanks for your help.
The text was updated successfully, but these errors were encountered: