Closed mrsauravsahu closed 2 months ago
The update introduces a configuration template for enabling external access to Keycloak through an Ingress controller. This configuration outlines various settings including URL rewriting, service connection details, and specific annotations that enhance functionality, ensuring smoother and more secure access management.
File Path | Change Summary |
---|---|
.../config/externals/keycloak/ingress.values.tftpl |
Introduced settings for Keycloak's external access via an Ingress controller. |
🐇 A Poem by CodeRabbit
In the garden of code, under digital skies,
A new path we pave, as the old one lies.
🌟 With ingress set, and routes anew,
Keycloak's doors open, for me and you.
🚪🎉 Let's hop through this gateway, explore what's in store,
In realms of bytes, forevermore.
molecules/cluster-resources/config/externals/keycloak/ingress.values.tftpl (5)
`1-3`: The URL rewrite flag is set to false, which is appropriate if no URL rewriting is needed for Keycloak access. --- `4-8`: The service configuration for Keycloak is correctly set with the standard HTTP port 80. --- `9-12`: Annotations for Hajimari are well-defined, enabling the dashboard and setting the app name to "idp". --- `13-16`: Ingress settings are correctly configured with a subdomain and a root route path, ensuring proper external access routing for Keycloak. --- `17-20`: Dynamic host configuration using a loop is correctly implemented, allowing flexible host entries based on the `hosts` variable.
Summary by CodeRabbit