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; Helm will not do this for you. 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, use Helm to install Emissary-ingress 2.3.1. Start by making sure that your
datawireHelm repo is set correctly:bashhelm repo delete datawirehelm repo add datawire https://app.getambassador.iohelm repo update
Then, update your Emissary-ingress installation in the
emissarynamespace. If necessary for your installation (e.g. if you were running with
AMBASSADOR_SINGLE_NAMESPACEset), you can choose a different namespace.bashhelm upgrade -n emissary \emissary-ingress datawire/emissary-ingress && \kubectl rollout status -n emissary deployment/emissary-ingress -w