Skip to content

ingress-nginx: the admission webhook CiliumNetworkPolicy breaks ingress on clusters without Cilium (isp-hosted) #4706

Closed

Description

packages/system/ingress-nginx/templates/admission-webhook-networkpolicy.yaml renders a cilium.io/v2 CiliumNetworkPolicy, guarded only by admissionWebhookPolicy.enabled (default true). The ingress application is unconditional in the system bundle, and isp-hosted runs on a host CNI without Cilium CRDs. So on isp-hosted, any tenant with ingress: true fails its ingress-nginx install with no matches for kind "CiliumNetworkPolicy", the same failure #3387 fixes for the tenant chart. Found while fixing #3387; the isp-hosted lane (#3390) will hit it as soon as a tenant enables ingress. Fix shape: render the policy only where Cilium is guaranteed, using the same variant key and capability check the #3387 fix uses, and decide explicitly what protects the webhook on a non-Cilium cluster (the policy exists because of CVE-2025-1974). The security consequence should be written in the PR, not dropped silently.

Activity

  1. added
    kind/bugCategorizes issue or PR as related to a bug
    area/networkingIssues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)
    on Oct 2, 2026
  2. added a commit that references this issue on Oct 27, 2026
    b366286
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/networkingIssues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)kind/bugCategorizes issue or PR as related to a bugtriage/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