From 4c617ccc92dcf68d7119f8f6d9ed090f38211b43 Mon Sep 17 00:00:00 2001 From: David Yu Date: Tue, 11 Jul 2023 00:35:40 +0000 Subject: [PATCH] backport of commit e76ec0a1937e7722edc554d96fa3e792bd1f56a0 --- website/content/docs/k8s/l7-traffic/failover-tproxy.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/k8s/l7-traffic/failover-tproxy.mdx b/website/content/docs/k8s/l7-traffic/failover-tproxy.mdx index 81bdc5e8672d..c08d8c3ac5d8 100644 --- a/website/content/docs/k8s/l7-traffic/failover-tproxy.mdx +++ b/website/content/docs/k8s/l7-traffic/failover-tproxy.mdx @@ -18,7 +18,7 @@ Complete the following steps to configure failover service instances in Consul o ## Requirements -- `consul-k8s` v1.2.0-beta1 or newer. +- `consul-k8s` v1.2.0 or newer. - Consul service mesh must be enabled. Refer to [How does Consul Service Mesh Work on Kubernetes](/consul/docs/k8s/connect). - Proxies must be configured to run in transparent proxy mode. - To query virtual DNS names, you must use Consul DNS.