Since Emissary-ingress's configuration is entirely stored in Kubernetes resources, upgrading between minor versions is straightforward.
Migration is a two-step process:
Install new CRDs.
Before installing Emissary-ingress 2.3.1 itself, you need to update the CRDs in your cluster. This is mandatory during any upgrade of Emissary-ingress.shellkubectl apply -f https://app.getambassador.io/yaml/emissary/2.3.1/emissary-crds.yamlkubectl wait --timeout=90s --for=condition=available deployment emissary-apiext -n emissary-system
Install Emissary-ingress 2.3.1.
After installing the new CRDs, upgrade Emissary-ingress 2.3.1.bashkubectl apply -f https://app.getambassador.io/yaml/emissary/2.3.1/emissary-emissaryns.yaml && \kubectl rollout status -n emissary deployment/emissary-ingress -w