Support for Dual Load Balancer IPs (Internal + External) in Keycloak.X Helm Chart

[amritarani-aryaka]

Hi Codecentric / Keycloak Community,

First off, thanks for your excellent work maintaining the keycloakx Helm chart. It’s been a solid solution for deploying Keycloak with Kubernetes.

I’m reaching out to get some guidance on a deployment pattern we’re trying to implement:

Use Case

We need Keycloak.X to be accessible via two distinct Load Balancer IPs/interfaces:

1. Internal/Core Access: Restricted to internal microservices or admin-level traffic.

2. External (Public) Access: Open to external applications and end-user traffic.

This separation is critical for improved security, segmented network policies, and reduced attack surface exposure.

---

What I’ve Observed

• The Helm chart for keycloakx seems to support only a single Service type (e.g., LoadBalancer or Ingress), configured for one external interface. Implementation examples and values are oriented around one hostname/IP configuration. GitHub+1

• There are no native chart parameters to specify dual service endpoints or separate interfaces for internal vs external clients.

---

Request for Enhancement or Alternatives

Would it be possible to expand the keycloakx chart’s flexibility to support:

• Multiple Load Balancer services (e.g., internalService + externalService), each with independent configurations (IP, annotations, selectors, etc.).

• Ingress configurations that can target different services based on internal vs external routing.

Alternatively, if such enhancements are out of scope, could someone advise on best practices or community-accepted patterns

[bumarcell]

By "Internal/Core Access Interface", do you mean the admin interface?