Fix formatting

hashicorp · Jan 25, 2021 · 83e43fc · 83e43fc
1 parent 990c814
commit 83e43fc
Show file tree

Hide file tree

Showing 3 changed files with 23 additions and 23 deletions.
diff --git a/website/content/docs/k8s/crds/upgrade-to-crds.mdx b/website/content/docs/k8s/crds/upgrade-to-crds.mdx
@@ -8,7 +8,7 @@ description: >-
 
 # Upgrade An Existing Cluster to CRDs
 
-Upgrading to consul-helm versions >= `0.29.0` will require some changes if
+Upgrading to consul-helm versions >= `0.30.0` will require some changes if
 you utilize the following:
 
 - [`connectInject.centralConfig.enabled`](#central-config-enabled)
@@ -206,27 +206,27 @@ manage it from Kubernetes:
 
 1. Once you've determined the `kind` and `name`, query Consul to get its contents:
 
-```shell-session
-$ config config read -kind <kind> -name <name>
-```
+   ```shell-session
+   $ consul config read -kind <kind> -name <name>
+   ```
 
-This will require `kubectl exec`'ing into a Consul server or client pod. If
-you're using ACLs, you will also need an ACL token passed via the `-token` flag.
-
-For example:
-
-```shell-session
-$ kubectl exec consul-server-0 -- consul config read -name foo -kind service-defaults
-{
-    "Kind": "service-defaults",
-    "Name": "foo",
-    "Protocol": "http",
-    "MeshGateway": {},
-    "Expose": {},
-    "CreateIndex": 60,
-    "ModifyIndex": 60
-}
-```
+   This will require `kubectl exec`'ing into a Consul server or client pod. If
+   you're using ACLs, you will also need an ACL token passed via the `-token` flag.
+
+   For example:
+
+   ```shell-session
+   $ kubectl exec consul-server-0 -- consul config read -name foo -kind service-defaults
+   {
+       "Kind": "service-defaults",
+       "Name": "foo",
+       "Protocol": "http",
+       "MeshGateway": {},
+       "Expose": {},
+       "CreateIndex": 60,
+       "ModifyIndex": 60
+   }
+   ```
 
 1. Now we're ready to construct a Kubernetes resource for the config entry.
 

diff --git a/website/content/docs/k8s/installation/multi-cluster/kubernetes.mdx b/website/content/docs/k8s/installation/multi-cluster/kubernetes.mdx
@@ -161,7 +161,7 @@ guide to upgrade your cluster and then come back to the [Federation Secret](#fed
 
 #### ProxyDefaults
 
-If you are using consul-helm 0.29.0+ you must also create a [`ProxyDefaults`](/docs/connect/config-entries/proxy-defaults)
+If you are using consul-helm 0.30.0+ you must also create a [`ProxyDefaults`](/docs/connect/config-entries/proxy-defaults)
 resource to configure Consul to use the mesh gateways for service mesh traffic.
 
 ```yaml

diff --git a/website/content/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx b/website/content/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx
@@ -292,7 +292,7 @@ to install Consul on your secondary cluster(s).
 
 ## Next Steps
 
-After installation, if you're using consul-helm 0.29.0+, remember to [create the
+After installation, if you're using consul-helm 0.30.0+, remember to [create the
 `ProxyDefaults` resource](/docs/k8s/installation/multi-cluster/kubernetes#proxydefaults)
 to allow traffic between datacenters.