Upgrading Ambassador Edge Stack

Since Ambassador Edge Stack's configuration is entirely stored in Kubernetes resources, no special process is necessary to upgrade Ambassador Edge Stack.

The steps to upgrade depend on the method that was used to install Ambassador Edge Stack, as indicated below.

Installed via the Operator?

If you installed using the Operator, then you'll need to use the Operator to perform the upgrade. To verify whether the Operator was used to install Ambassador Edge Stack, run the following command to see if it returns resources:

Installed via Helm?

If you installed using the Helm chart or edgectl install, then you should upgrade with the help of Helm. To verify this, run the following command to see if it returns resources:

Installed via YAML Manifests?

Finally, if you installed using YAML manifests, simply run the commands in the following section. To verify whether manifests were used to install Ambassador Edge Stack, run the following command to see if it returns resources:

If none of the commands above return resources, you probably have an old installation and you should follow the instructions for upgrading to Ambassador Edge Stack.

Upgrading an Installation with YAML Manifests

If you previously installed Edge Stack using YAML manifests, you can upgrade with these commands:

This will trigger a rolling upgrade of Ambassador Edge Stack.

If you're using your own YAML, check our YAML to be sure of other changes. At a minimum you'll need to change the pulled image for the Ambassador Edge Stack container and redeploy.

Set Up Service Catalog

Upgrading to version 1.12 or higher adds support for Service Catalog. Set up Service Catalog to view all of your service metadata in Ambassador Cloud.