From 06c0d7d312603d8bf635cca100896c03be5632e0 Mon Sep 17 00:00:00 2001 From: John Murret Date: Thu, 22 Aug 2024 13:48:12 -0600 Subject: [PATCH] revert change to website/content/docs/connect/config-entries/mesh.mdx (#21645) --- website/content/docs/connect/config-entries/mesh.mdx | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/website/content/docs/connect/config-entries/mesh.mdx b/website/content/docs/connect/config-entries/mesh.mdx index 544c21e1cc..f83c129805 100644 --- a/website/content/docs/connect/config-entries/mesh.mdx +++ b/website/content/docs/connect/config-entries/mesh.mdx @@ -336,17 +336,6 @@ Note that the Kubernetes example does not include a `partition` field. Configura }, ], }, - { - name: 'ValidateClusters', - type: 'bool: false', - description: - `Controls whether the clusters the route table refers to are validated. The default value is false. When set to - false and a route refers to a cluster that does not exist, the route table loads and routing to a non-existent - cluster results in a 404. When set to true and the route is set to a cluster that do not exist, the route table - will not load. For more information, refer to - [HTTP route configuration in the Envoy docs](https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route.proto#envoy-v3-api-field-config-route-v3-routeconfiguration-validate-clusters) - for more details. `, - }, { name: 'TLS', type: 'TLSConfig: ',