Skip to content

feat(keycloakx): add namespaceOverride and service.internalTrafficPolicy#909

Open
teddy0605 wants to merge 1 commit into
codecentric:masterfrom
teddy0605:feat/keycloakx-namespace-override-and-service-fields
Open

feat(keycloakx): add namespaceOverride and service.internalTrafficPolicy#909
teddy0605 wants to merge 1 commit into
codecentric:masterfrom
teddy0605:feat/keycloakx-namespace-override-and-service-fields

Conversation

@teddy0605

Copy link
Copy Markdown

Summary

  • Adds namespaceOverride value so umbrella charts can deploy multiple aliased keycloakx instances each into their own namespace. A keycloakx.namespace helper centralises the logic; all templates use it instead of .Release.Namespace directly.
  • Adds service.internalTrafficPolicy to values.yaml and service-http.yaml. Previously there was no way to set this field without a post-renderer workaround.

Motivation

When deploying keycloakx as a subchart multiple times in the same umbrella chart (using Helm aliases), all instances land in the release namespace. namespaceOverride lets each alias target a different namespace independently.

internalTrafficPolicy is needed to control routing for internal cluster traffic (e.g. Local to keep traffic node-local), which is a standard Kubernetes Service field not currently exposed by the chart.

Backwards compatibility

Both changes are additive. Default values (namespaceOverride: "", internalTrafficPolicy: "") preserve existing behaviour — charts that don't set these values render identically to before.

Adds a `namespaceOverride` value that lets umbrella charts deploy multiple
aliased keycloakx instances each into their own namespace. A new
`keycloakx.namespace` helper template centralises the logic and is used in
place of `.Release.Namespace` across all resource templates.

Adds `service.internalTrafficPolicy` to values.yaml and wires it into
service-http.yaml so callers no longer need a post-renderer workaround to
set this field.

Signed-off-by: teddy0605 <teddy0605@users.noreply.github.com>
@teddy0605 teddy0605 requested a review from a team as a code owner June 26, 2026 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant