From 1c610cb01d1d909f3e652a83af88e6e0f936f7af Mon Sep 17 00:00:00 2001 From: sarahalsmiller <100602640+sarahalsmiller@users.noreply.github.com> Date: Thu, 16 Jun 2022 15:36:27 -0500 Subject: [PATCH] Update upgrade-specific-versions.mdx --- .../content/docs/api-gateway/upgrade-specific-versions.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/api-gateway/upgrade-specific-versions.mdx b/website/content/docs/api-gateway/upgrade-specific-versions.mdx index 81901a1cf..a7312bde3 100644 --- a/website/content/docs/api-gateway/upgrade-specific-versions.mdx +++ b/website/content/docs/api-gateway/upgrade-specific-versions.mdx @@ -38,7 +38,7 @@ Ensure that the following requirements are met prior to upgrading: You should receive the following response: ```log - "hashicorp/consul-api-gateway:0.1.0" + "hashicorp/consul-api-gateway:0.2.1" ``` 1. Retrieve all gateways that have a secret in a different namespace. If you have installed the [`jq`](https://stedolan.github.io/jq/) utility, you can skip to [step 4](#jq-command-secrets). Otherwise, issue the following command to get all `Gateways` across all namespaces: @@ -430,7 +430,7 @@ This is the upgrade path to use when there are no version specific steps to take 1. Issue the following command to upgrade your Consul installation: ```shell-session - $ helm upgrade --values values.yaml --namespace consul --version hashicorp/consul + $ helm upgrade --values values.yaml --namespace consul --version hashicorp/consul ``` Note that the upgrade will cause the Consul API Gateway controller shut down and restart with the new version.