Upgrade Emissary-ingress 3.7.Z (YAML)

Since Emissary-ingress's configuration is entirely stored in Kubernetes resources, upgrading between versions is straightforward.

Resources to check before migrating to 3.9.1.

Migration Steps

Migration is a two-step process:

1. Install new CRDs.

   Before installing Emissary-ingress 3.9.1 itself, you need to update the CRDs in your cluster. This is mandatory during any upgrade of Emissary-ingress.

   Emissary-ingress 3.9.1 includes a Deployment in the `emissary-system` namespace called emissary-apiext. This is the APIserver extension that supports converting Emissary-ingress CRDs between getambassador.io/v2and getambassador.io/v3alpha1. This Deployment needs to be running at all times.
   If the emissary-apiext Deployment's Pods all stop running, you will not be able to use getambassador.io/v3alpha1 CRDs until restarting the emissary-apiext Deployment.
   There is a known issue with the emissary-apiext service that impacts all Emissary-ingress 2.x and 3.x users. Specifically, the TLS certificate used by apiext expires one year after creation and does not auto-renew. All users who are running Emissary-ingress/Ambassador Edge Stack 2.x or 3.x with the apiext service should proactively renew their certificate as soon as practical by running kubectl delete --all secrets --namespace=emissary-system to delete the existing certificate, and then restart the emissary-apiext deployment with kubectl rollout restart deploy/emissary-apiext -n emissary-system. This will create a new certificate with a one year expiration. We will issue a software patch to address this issue well before the one year expiration. Note that certificate renewal will not cause any downtime.

2. Install Emissary-ingress 3.9.1.

   After installing the new CRDs, upgrade Emissary-ingress 3.9.1.

   Our emissary-emissaryns.yaml file uses the `emissary` namespace, since this is the default for Emissary-ingress. We also publish emissary-defaultns.yaml for the `default` namespace. For any other namespace, you should download one of these files and edit the namespaces manually.