2 min • read

Upgrade Ambassador Edge Stack 2.2.X to Ambassador Edge Stack 2.3.1 (YAML)

This guide covers migrating from Ambassador Edge Stack 2.2.2 or 2.2.0 to Ambassador Edge Stack 2.3.1. If this is not your exact situation, see the migration matrix.

This guide is written for upgrading an installation made without using Helm. If you originally installed with Helm, see the Helm-based upgrade instructions.

Since Ambassador Edge Stack'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 Ambassador Edge Stack 2.3.1 itself, you need to update the CRDs in your cluster. This is mandatory during any upgrade of Ambassador Edge Stack.
shell
```
kubectl apply -f https://app.getambassador.io/yaml/edge-stack/2.3.1/aes-crds.yaml
kubectl wait --timeout=90s --for=condition=available deployment emissary-apiext -n emissary-system
```
Ambassador Edge Stack 2.3.1 includes a Deployment in the `emissary-system` namespace called edge-stack-apiext. This is the APIserver extension that supports converting Ambassador Edge Stack CRDs between getambassador.io/v2and getambassador.io/v3alpha1. This Deployment needs to be running at all times.
If the edge-stack-apiext Deployment's Pods all stop running, you will not be able to use getambassador.io/v3alpha1 CRDs until restarting the edge-stack-apiext Deployment.

Install Ambassador Edge Stack 2.3.1.

After installing the new CRDs, upgrade Ambassador Edge Stack 2.3.1:

kubectl apply -f https://app.getambassador.io/yaml/edge-stack/2.3.1/aes.yaml && \
kubectl rollout status -n ambassador deployment/edge-stack -w