-
Notifications
You must be signed in to change notification settings - Fork 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 same FQDN for both ingresses #24320
Comments
addming full
|
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/keycloak:19.3.0
What architecture are you using?
amd64
What steps will reproduce the bug?
I'm trying to configure and setup keycloak using bitnami/keycloak:19.3.0 helm chart with below given command
and trying to setup ingresses for both normal
ingress
andadminIngress
using same FQDN. However, it seems to loop forever or does not work completely.Background:
We use bitnami/keycloak for on-prem based deployments where using 2 different FQDNs is completely NOT an option and routing using same FQDN is mandatory requirement.
Are you using any custom parameters or values?
What is the expected behavior?
the
adminIngress
never works.What do you see instead?
Ideally, the requirement of separate FQDN should not block using same FQDN but with different ingress routes.
Additional information
No response
The text was updated successfully, but these errors were encountered: