Upgrade NGINX Ingress Controller LTS

This document describes how to upgrade F5 NGINX Ingress Controller LTS to a new patch release.

Many of the nuances in upgrade paths relate to how custom resource definitions (CRDs) are managed.

Upgrading to a new LTS patch release

Upgrade NGINX Ingress Controller LTS CRDs

To upgrade the CRDs, pull the Helm chart source, then use kubectl apply:

helm pull oci://ghcr.io/nginx/charts/nginx-ingress --untar --version 2.6.0
kubectl apply -f crds/

Alternatively, CRDs can be upgraded without pulling the chart by running:

kubectl apply -f https://raw.githubusercontent.com/nginx/kubernetes-ingress/v5.5.0/deploy/crds.yaml

In the above command, v5.5.0 represents the version of the NGINX Ingress Controller LTS release rather than the Helm chart version.

The following warning is expected and can be ignored: Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply.

Check the release notes for a new release for any special upgrade procedures.

Upgrade NGINX Ingress Controller LTS charts

Once the CRDs have been upgraded, you can then upgrade the release chart.

The command depends on if you installed the chart using the registry or from source.

To upgrade a release named my-release, use the following command:

helm upgrade my-release oci://ghcr.io/nginx/charts/nginx-ingress --version 2.6.0

helm upgrade my-release .