Migrate to a new Ingress or gateway controller
Migrate from Community NGINX to F5 NGINX or Envoy Gateway to maintain supported traffic management.
Community NGINX is deprecated as of version 9.1.20.0. When you upgrade from an earlier version, you might experience brief downtime for existing Ingress rules because of updated template definitions. To avoid extended outages, run multiple controllers simultaneously during the transition.
- Resource naming
-
To avoid naming conflicts, the Helm chart generates distinct names for each controller:
- Community NGINX: Includes community-nginx in the name.
- F5 NGINX: Includes f5-nginx in the name.
- GKE: Includes gke in the name.
Migration Procedure
- Add both the old and new controllers to the ingress.ingressController list.
- Verify that traffic shifts to the new controller.
- Remove the old controller from the ingress.ingressController list.
ingress:
enabled: true
ingressController:
- nginx
- f5-nginx
cmc:
auth:
domain: cmc.demoqaauth.mycompany.com
communityNginxClass: ""
f5NginxClass: ""
live:
domain: cmc.demoqalive.mycompany.com
communityNginxClass: ""
f5NginxClass: ""
communityNginxCustomAnnotations: {}
f5NginxCustomAnnotations: {}- Using Gateway API (Optional)
- You can also use the Kubernetes Gateway API (such as Envoy Gateway) standalone or alongside Ingress controllers. This configuration uses the Gateway, HTTPRoute, and BackendTLSPolicy resources and is independent of the Ingress section.