Skip to content

chore(cilium): drop externalIPs.enabled and nodePort.enabled, the Cilium chart does not read them #4816

Open

Description

packages/system/cilium/values.yaml sets two Cilium switches that do nothing: cilium.externalIPs.enabled: true and cilium.nodePort.enabled: true. The vendored chart in packages/system/cilium/charts/cilium reads neither of them, on main (1.19.5) and on the 1.20.2 bump in #3343.

The configmap template only reads nodePort.range, nodePort.addresses, nodePort.directRoutingDevice and nodePort.enableHealthCheck. There is no externalIPs key in the upstream values.yaml at all.

Nothing changes at runtime. The problem is a reader who sees these keys and assumes they turn the features on or off. I'd delete both.

Activity

  1. added
    kind/cleanupCategorizes issue or PR as related to cleanup of code, process, or technical debt
    area/ciliumIssues or PRs related to Cilium (agent, operator, Gateway API, network policy, LB-IPAM)
    on Oct 8, 2026
  2. GitNimay commented on Oct 19, 2026

    @GitNimay

    Hi! I'd like to take this one. I checked the vendored chart at 1.20.2 and confirmed externalIPs.enabled and nodePort.enabled aren't read anywhere in charts/cilium/templates, so I'll remove both keys from packages/system/cilium/values.yaml and open a PR shortly.

  3. added a commit that references this issue on Nov 13, 2026
    700600e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/ciliumIssues or PRs related to Cilium (agent, operator, Gateway API, network policy, LB-IPAM)kind/cleanupCategorizes issue or PR as related to cleanup of code, process, or technical debttriage/needs-triageIndicates an issue needs triage by a maintainer

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions