Update TLS/DNSPolicy guides with v1 apiVersion

Signed-off-by: David Martin <[email protected]>
Kuadrant · Dec 12, 2024 · 59e9999 · 59e9999
1 parent c8e1c06
commit 59e9999
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/doc/overviews/dns.md b/doc/overviews/dns.md
@@ -170,7 +170,7 @@ When a DNSPolicy targets a Gateway, the policy will be enforced on all gateway l
 Target a Gateway by setting the `spec.targetRef` field of the DNSPolicy as follows:
 
 ```yaml
-apiVersion: kuadrant.io/v1beta2
+apiVersion: kuadrant.io/v1
 kind: DNSPolicy
 metadata:
   name: <DNSPolicy name>
@@ -186,7 +186,7 @@ spec:
 A DNSPolicy can target a specific listener in a gateway using the `sectionName` property of the targetRef configuration. When you set the `sectionName`, the DNSPolicy will only affect that listener and no others. If you also have another DNSPolicy targeting the entire gateway, the more specific policy targeting the listerner will be the policy that is applied.
 
 ```yaml
-apiVersion: kuadrant.io/v1beta2
+apiVersion: kuadrant.io/v1
 kind: DNSPolicy
 metadata:
   name: <DNSPolicy name>

diff --git a/doc/overviews/tls.md b/doc/overviews/tls.md
@@ -50,7 +50,7 @@ When a TLSPolicy targets a Gateway, the policy will be enforced on all gateway l
 Target a Gateway by setting the `spec.targetRef` field of the TLSPolicy as follows:
 
 ```yaml
-apiVersion: kuadrant.io/v1beta2
+apiVersion: kuadrant.io/v1
 kind: TLSPolicy
 metadata:
   name: <TLSPolicy name>