filename

hashicorp · Feb 22, 2023 · 17c4561 · 17c4561
1 parent 0ee5fc4
commit 17c4561
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/website/content/docs/k8s/connect/cluster-peering/usage/k8s-l7-traffic.mdx b/website/content/docs/k8s/connect/cluster-peering/usage/k8s-l7-traffic.mdx
@@ -25,7 +25,7 @@ To configure L7 traffic management behavior in deployments with cluster peering
 
   The following example updates the [`service-resolver` CRD](/docs/connect/config-entries/) in `cluster-01` so that Consul redirects traffic intended for the `frontend` service to a backup instance in peer `cluster-02` when it detects multiple connection failures.
 
-  <CodeBlockConfig heading="failover-resolver.yaml">
+  <CodeBlockConfig filename="failover-resolver.yaml">
 
   ```yaml
   apiVersion: consul.hashicorp.com/v1alpha1
@@ -54,7 +54,7 @@ To configure L7 traffic management behavior in deployments with cluster peering
 
   The following example splits traffic evenly between `frontend` and `frontend-peer`:
 
-  <CodeBlockConfig heading="splitter.yaml">
+  <CodeBlockConfig filename="splitter.yaml">
 
   ```yaml
   apiVersion: consul.hashicorp.com/v1alpha1
@@ -81,7 +81,7 @@ To configure L7 traffic management behavior in deployments with cluster peering
 
   The following example uses the name `frontend-peer` to define a redirect targeting the `frontend` service on the peer `cluster-02`:
 
-  <CodeBlockConfig heading="peer-resolver.yaml">
+  <CodeBlockConfig filename="peer-resolver.yaml">
 
   ```yaml
   apiVersion: consul.hashicorp.com/v1alpha1