Skip to content

Conversation

nevlkv
Copy link

@nevlkv nevlkv commented Oct 10, 2025

I use dynamic url with multiple fqdn in the ingress

spec:
  ingressClassName: nginx
  rules:
  - host: keycloak.<subd1>.dev
    http:
      paths:
      - backend:
          service:
            name: keycloak
            port:
              name: http
        path: /
        pathType: ImplementationSpecific
  - host: keycloak.<subd2>.dev
    http:
      paths:
      - backend:
          service:
            name: keycloak
            port:
              name: http
        path: /
        pathType: ImplementationSpecific
  tls:

aka
image

Template force sets KC_HOSTNAME to defined first ingress.hostname but

Additionally if hostname is configured, then hostname-strict is ignored

image

I can set KC_HOSTNAME manual from ENV, from ingress or set undefined for dynamic

Signed-off-by: Nikolay Volkov <[email protected]>
@nevlkv nevlkv force-pushed the change_keycloak_hostname_settings branch from b09c344 to 98e8e5b Compare October 10, 2025 13:17
bitnami-bot and others added 3 commits October 10, 2025 13:28
Signed-off-by: Bitnami Bot <[email protected]>
Signed-off-by: Bitnami Bot <[email protected]>
@carrodher
Copy link
Member

Thank you for initiating this pull request. We appreciate your effort. This is just a friendly reminder that signing your commits is important. Your signature certifies that you either authored the patch or have the necessary rights to contribute to the changes. You can find detailed information on how to do this in the “Sign your work” section of our contributing guidelines.

Feel free to reach out if you have any questions or need assistance with the signing process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

keycloak triage Triage is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants