docs - redo cherry pick from Consul K8s upgrade doc #17760 (#17787)

* no-op commit due to failed cherry-picking * manual cherry-pick --------- Co-authored-by: temp <[email protected]> Co-authored-by: Luke Kysow <[email protected]>
hashicorp · Jun 16, 2023 · 1f04ed0 · 1f04ed0
1 parent 5642bc6
commit 1f04ed0
Showing 1 changed file with 1 addition and 3 deletions.
diff --git a/website/content/docs/k8s/upgrade/index.mdx b/website/content/docs/k8s/upgrade/index.mdx
@@ -228,15 +228,13 @@ If you upgrade Consul from a version that uses client agents to a version the us
         type: OnDelete
   ```
 
-1. Add `consul.hashicorp.com/consul-k8s-version: 1.0.0` to the annotations for each pod you upgrade.  
-
 1. Follow our [recommended procedures to upgrade servers](#upgrade-consul-servers) on Kubernetes deployments to upgrade Helm values for the new version of Consul.
 
 1. Run `kubectl rollout restart` to restart your service mesh applications. Restarting service mesh application causes Kubernetes to re-inject them with the webhook for dataplanes.
 
 1. Restart all gateways in your service mesh.
 
-1. Disable client agents in your Helm chart by deleting the `client` stanza or setting `client.enabled` to `false`. 
+1. Disable client agents in your Helm chart by deleting the `client` stanza or setting `client.enabled` to `false` and running a `consul-k8s` or Helm upgrade.
 
 ## Configuring TLS on an existing cluster