Support and related documentation for ingress controller other than nginx about keycloak-operator

[andreaTP]

Hi @shailsirohi ,

as you already noticed currently this operator only supports a default nginx ingress.

The (warmly)suggested approach(especially for production) is to disable the "provided default ingress" and spin up your own referring to the Keycloak created Service.

Let me know if this works for you.

[andreaTP]

As this issue has been around for a long time we are closing this issue as out of date. If the issue is still valid, please verify with the latest version of the Keycloak operator, feel free to reopen and provide details to why it is still valid.

[danielwegener]

How about allowing the CR to add annotations to the generated ingress (e.g. the by traefik required ingress.kubernetes.io/protocol: https). This could work similar like keycloakDeploymentSpec (suggestion: keycloakIngress) and merge fields provided in the CR over the generated ingress object.

[andreaTP]

Hi @danielwegener , do you have any specific requirement to re-use the "default" ingress?
You are encouraged to spin your own Ingress and this allow to completely customize it.