Skip to content

# Upgrading

Important

No matter the method you use for upgrading, if you use template overrides, make sure your templates are compatible with the new version of ingress-nginx.

## Without Helm

To upgrade your ingress-nginx installation, it should be enough to change the version of the image in the controller Deployment.

I.e. if your deployment resource looks like (partial example):

    kind: Deployment
    metadata:
      name: nginx-ingress-controller
      namespace: ingress-nginx
    spec:
      replicas: 1
      selector: ...
      template:
        metadata: ...
        spec:
          containers:
            - name: nginx-ingress-controller
              image: k8s.gcr.io/ingress-nginx/controller:v0.34.0@sha256:56633bd00dab33d92ba14c6e709126a762d54a75a6e72437adefeaaca0abb069
              args: ...

simply change the `0.34.0` tag to the version you wish to upgrade to. The easiest way to do this is e.g. (do note you may need to change the name parameter according to your installation):

    kubectl set image deployment/nginx-ingress-controller \
      nginx-ingress-controller=k8s.gcr.io/ingress-nginx/controller:v0.34.1@sha256:0e072dddd1f7f8fc8909a2ca6f65e76c5f0d2fcfb8be47935ae3457e8bbceb20 \
      -n ingress-nginx

For interactive editing, use `kubectl edit deployment nginx-ingress-controller -n ingress-nginx`.

## With Helm

If you installed ingress-nginx using the Helm command in the deployment docs so its name is `ngx-ingress`, you should be able to upgrade using

    helm upgrade --reuse-values ngx-ingress ingress-nginx/ingress-nginx

### Migrating from stable/nginx-ingress

See detailed steps in the upgrading section of the `ingress-nginx` chart README.