Docs right arrow Emissary-ingress2.0Upgrading Emissary-ingress

1 min • read

Upgrading Emissary-ingress

To migrate from Emissary-ingress 1.X to Emissary-ingress 2.X, see the Emissary-ingress 2.X Migration Guide. This guide will not work for that, due to changes to the configuration resources used for Emissary-ingress 2.X.

We're pleased to introduce Emissary-ingress 2.0! The 2.X family introduces a number of changes to allow Emissary-ingress to more gracefully handle larger installations (including multitenant or multiorganizational installations), reduce memory footprint, and improve performance. For more information on 2.X, please check the release notes.

Since Emissary-ingress's configuration is entirely stored in Kubernetes resources, no special process is necessary to upgrade Emissary-ingress.

The steps to upgrade depend on the method that was used to install Emissary-ingress, as indicated below.

Which upgrade method should I use?

To check if you installed Emissary-ingress with Helm, run the following command to see if it returns resources:

If Helm reports a release of Emissary-ingress in your cluster, you should upgrade with the help of Helm.

Otherwise, you should follow the YAML upgrade guide

.css-1e2dcm1{z-index:1500;pointer-events:none;}.css-okvapm{z-index:1500;pointer-events:none;}Upgrading Emissary-ingress

.css-1e2dcm1{z-index:1500;pointer-events:none;}.css-okvapm{z-index:1500;pointer-events:none;}Which upgrade method should I use?

Upgrading Emissary-ingress

Which upgrade method should I use?