Skip to content

feat(helm): expose Service IP-family settings - #3678

Open
kquinsland01 wants to merge 1 commit into
kagent-dev:mainfrom
kquinsland01:feat/helm-service-ip-families
Open

kquinsland01 wants to merge 1 commit into
kagent-dev:mainfrom
kquinsland01:feat/helm-service-ip-families

Conversation

@kquinsland01

Copy link
Copy Markdown

The UI and controller can listen on IPv6 while its chart-managed Service remains IPv4-only because the Helm chart does not expose Service IP-family settings.

This is a simple PR to add an optional ipFamilyPolicy and ordered ipFamilies values independently under ui.service and controller.service.

Empty defaults omit both fields, preserving Kubernetes defaulting and the chart's existing rendered output.

This also has a bit of documentation explaining how to use any of the three possible configurations: IPv4-only, IPv6-only and dual-stack usage.

Validation:

  • Full Helm suite: 373 tests across 32 suites pass with the CI Helm version, 3.18.0.
  • Focused Service suites: 41 tests pass, including default omission, both single-stack families, both dual-stack orders, independent components and independently optional fields.
  • helm lint helm/kagent passes.
  • Full default chart rendering is byte-identical to the unmodified base.
  • Eight explicitly configured Service renders pass strict Kubernetes schema validation.
  • git diff --check passes.

Signed-off-by: Karl Quinsland <github@karlquinsland.com>
@kquinsland01
kquinsland01 requested a review from a team as a code owner November 14, 2026 00:05
@github-actions github-actions Bot added the enhancement New feature or request label Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant