Migrate from the ingress-nginx subchart in CloudBees CI

Last Reviewed:2025-11-06()
2 minute readKnowledge base

Issue

The use of the ingress-nginx subchart in the CloudBees CI chart is no longer supported. If you are using the ingress-nginx subchart, you must migrate to the official ingress-nginx chart prior to upgrading CloudBees CI on modern cloud platforms.

Environment

Resolution

To migrate from the unsupported ingress-nginx subchart:

  1. Check if the deprecated subchart is enabled:

    helm get values <release-name> -n <namespace>(1)
    ▼
    1 Replace <release-name> and <namespace> with your CloudBees CI on modern cloud platforms release name and namespace, respectively.

    If ingress-nginx.Enabled is true, migration is required:

    ingress-nginx:
  Enabled: true
    ▼

    If the value is missing or false, no further action is needed.

  2. To migrate:

    1. Copy all values under ingress-nginx.controller to a new file named ingress-nginx-values.yaml. The following sample shows the base content provided by the subchart. If you wish to preserve the same behavior as before, use these values as your starting point and override them only as needed for your environment:

      ingress-nginx:
  Enabled: true
  controller:
    allowSnippetAnnotations: false(1)
    ingressClassResource:
      name: nginx(2)
    nodeSelector:
      kubernetes.io/os: linux(3)
    service:
      externalTrafficPolicy: Local(4)
    admissionWebhooks:
      enabled: false(5)
  defaultBackend:
    nodeSelector:
      kubernetes.io/os: linux
      ▼
      1 Typically obsolete in current chart releases.
      2 Should match your CloudBees CI chart configuration. nginx is the default value for non-ALB/Red Hat OpenShift Container Platform (OCP).
      3 Required for mixed-OS clusters.
      4 Important for source IP handling; required if lax source IP enforcement is not enabled on crumb issuer.
      5 Optional; enabling admission webhooks may cause issues in some environments.

    In most cases, this migration removes the existing LoadBalancer service and creates a new one. In cloud environments, this typically means the old LoadBalancer is deleted and a new one is provisioned. If you use static IPs, you may need to update your DNS records accordingly.

    1. Validate the formatting against the official ingress-nginx documentation.

    2. Remove the ingress-nginx section from the CloudBees CI Helm values and apply those values.

    3. Install the official ingress-nginx chart in its own namespace, following the ingress-nginx documentation.

    4. Upgrade CloudBees CI on modern cloud platforms.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.