1.10.0+ Upgrade Notice
Follow these steps to upgrade your Gloo Edge or Gloo Edge Enterprise deployments to version 1.10 from previous verisions.
This upgrade guide assumes that you installed Gloo Edge with Helm or
glooctl. You can verify this installation by checking for a Helm chart release named
gloo in the output of
helm ls --all-namespaces.
For steps to avoid downtime during upgrades, check out the Recommended settings.
Helm Breaking Changes
- Prior to Gloo Edge Enterprise version v1.10,
license_secret_namecould be specified at the top level of your helm
values.yamlfile. However, in order to use this option now, this must be specified under
--- values.yaml --- license_secret_name: some-license-secret # the above becomes --- new-values.yaml --- gloo: license_secret_name: some-license-secret
Upgrade Gloo Edge
Upgrade Gloo Edge.
<p>helm repo update helm upgrade -n gloo-system gloo gloo/gloo –version=1.10.0</p>
<p>helm repo update helm upgrade -n gloo-system gloo glooe/gloo-ee –version=1.10.0</p>
To verify that your upgrade was successful, let’s first check the version:
You should see the expected version for all the server components.
Let’s also check that your Gloo Edge installation is healthy by running:
If everything went well, you should see the following output:
Checking deployments... OK Checking pods... OK Checking upstreams... OK Checking upstream groups... OK Checking auth configs... OK Checking rate limit configs... OK Checking VirtualHostOptions... OK Checking RouteOptions... OK Checking secrets... OK Checking virtual services... OK Checking gateways... OK Checking proxies... OK No problems detected.