diff --git a/website/content/docs/k8s/l7-traffic/route-to-virtual-services.mdx b/website/content/docs/k8s/l7-traffic/route-to-virtual-services.mdx
index c8951d356c..0852f81196 100644
--- a/website/content/docs/k8s/l7-traffic/route-to-virtual-services.mdx
+++ b/website/content/docs/k8s/l7-traffic/route-to-virtual-services.mdx
@@ -20,7 +20,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.
@@ -119,4 +119,4 @@ You can query the KubeDNS if the real and virtual services are in the same Kuber
 http://virtual-api.<namespace>.svc.cluster.local
 ```
 
-Note that you cannot use KubeDNS if a corresponding Kubernetes service and pod do not exist. 
\ No newline at end of file
+Note that you cannot use KubeDNS if a corresponding Kubernetes service and pod do not exist.