Upgrade
Upgrade Gloo Gateway to the next version.
Upgrade the gloo
control plane and any Gloo Gateway proxies that run in your cluster. During the upgrade, pods that run the new version of the control plane and proxies are created. Then, the old pods are terminated. Because zero downtime is not guaranteed, try testing the upgrade in a staging environment before upgrading your production environment.
Update the Gloo Gateway Helm repositories.
helm repo update
Set the version to upgrade Gloo Gateway to in an environment variable, such as the latest patch version for open source (
1.18.0-beta18
) or enterprise (1.17.1
).Apply the new and updated CRDs.
Get the Helm values files for your current version.
helm get values gloo-gateway -n gloo-system -o yaml > gloo-gateway.yaml open gloo-gateway.yaml
Make any changes to your Helm values file.
Upgrade the Helm release.
Verify that Gloo Gateway runs the upgraded version.
kubectl -n gloo-system get pod -l gloo=gloo -ojsonpath='{.items[0].spec.containers[0].image}'
Example output:
quay.io/solo-io/gloo-ee:1.17.1@sha256:582ab27a995e9526522f81a9325584aefb528fa4d939455fd285e5148615991b
Confirm that the Gloo Gateway control plane is up and running.
kubectl get pods -n gloo-system