Fix keycloak ingress #33
Closed
Conversation
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
Signed-off-by: Omri Shiv <[email protected]>
omrishiv
force-pushed
the
fix-keycloak-ingress
branch
from
08ee79d to
dc6ce07
Compare
nabuskey
reviewed
Apr 11, 2024
Comment on lines
+24
to
+31
| number: 8080 | ||
| - path: / | ||
| pathType: Exact | ||
| pathType: Prefix | ||
| backend: | ||
| service: | ||
| name: keycloak | ||
| port: | ||
| number: 8081 | ||
| number: 8080 |
There was a problem hiding this comment.
These are set to 8081 and exact is to make sure the Keycloak admin UI is not accessible from anywhere. E.g. you have to use port-foward to access it. I could have used a SG to block access but it's difficult when I cannot be reasonably sure where users are access accessing ingress from.
There was a problem hiding this comment.
That makes sense, thank you for the clarification. The issue I was having was with the UI not rendering correctly (missing images), but also not forwarding to the admin ui even with port forwarding.
|
Closing this due to inactivity. Please feel free to re-open. |
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.
On deploying CNOE, the keycloak ingress does not work properly. To fix the issue:
KC_HOSTNAMEto the subdomain forkeycloakkeycloakservice. Switch to port 8080/forkeycloakingress to match a Prefix, otherwise path based routing doesn't work.These changes are tested working in my EKS environment.
I'm still trying to sort out how all the templating works, so please check my work on whether the value for
KC_HOSTNAMEis set correctly