docs: fix patch command for adding TLS gateway listener (envoyproxy#4316

) docs: fix patch command adding TLS gateway listener Signed-off-by: Dean Coakley <dean.s.coakley@gmail.com>
guydc · Sep 23, 2024 · e5fe849 · e5fe849
1 parent 7f24294
commit e5fe849
Show file tree

Hide file tree

Showing 6 changed files with 12 additions and 12 deletions.
diff --git a/site/content/en/docs/tasks/security/tls-cert-manager.md b/site/content/en/docs/tasks/security/tls-cert-manager.md
@@ -76,7 +76,7 @@ EOF
 We now have to patch the example Gateway to reference cert-manager:
 
 ```console
-$ kubectl patch gateway/eg --patch-file - <<EOF
+$ kubectl patch gateway/eg --patch '
 metadata:
   annotations:
     cert-manager.io/cluster-issuer: selfsigned
@@ -92,7 +92,7 @@ spec:
       certificateRefs:
       - kind: Secret
         name: eg-https
-EOF
+' --type=merge
 ```
 
 You could instead create a new Gateway serving HTTPS, if you'd prefer.

diff --git a/site/content/en/latest/tasks/security/tls-cert-manager.md b/site/content/en/latest/tasks/security/tls-cert-manager.md
@@ -75,7 +75,7 @@ EOF
 We now have to patch the example Gateway to reference cert-manager:
 
 ```console
-$ kubectl patch gateway/eg --patch-file - <<EOF
+$ kubectl patch gateway/eg --patch '
 metadata:
   annotations:
     cert-manager.io/cluster-issuer: selfsigned
@@ -91,7 +91,7 @@ spec:
       certificateRefs:
       - kind: Secret
         name: eg-https
-EOF
+' --type=merge
 ```
 
 You could instead create a new Gateway serving HTTPS, if you'd prefer.

diff --git a/site/content/en/v0.5/user/tls-cert-manager.md b/site/content/en/v0.5/user/tls-cert-manager.md
@@ -76,7 +76,7 @@ EOF
 We now have to patch the example Gateway to reference cert-manager:
 
 ```console
-$ kubectl patch gateway/eg --patch-file - <<EOF
+$ kubectl patch gateway/eg --patch '
 metadata:
   annotations:
     cert-manager.io/cluster-issuer: selfsigned
@@ -92,7 +92,7 @@ spec:
       certificateRefs:
       - kind: Secret
         name: eg-https
-EOF
+' --type=merge
 ```
 
 You could instead create a new Gateway serving HTTPS, if you'd prefer.

diff --git a/site/content/en/v0.6/user/tls-cert-manager.md b/site/content/en/v0.6/user/tls-cert-manager.md
@@ -76,7 +76,7 @@ EOF
 We now have to patch the example Gateway to reference cert-manager:
 
 ```console
-$ kubectl patch gateway/eg --patch-file - <<EOF
+$ kubectl patch gateway/eg --patch '
 metadata:
   annotations:
     cert-manager.io/cluster-issuer: selfsigned
@@ -92,7 +92,7 @@ spec:
       certificateRefs:
       - kind: Secret
         name: eg-https
-EOF
+' --type=merge
 ```
 
 You could instead create a new Gateway serving HTTPS, if you'd prefer.

diff --git a/site/content/en/v1.0/tasks/security/tls-cert-manager.md b/site/content/en/v1.0/tasks/security/tls-cert-manager.md
@@ -76,7 +76,7 @@ EOF
 We now have to patch the example Gateway to reference cert-manager:
 
 ```console
-$ kubectl patch gateway/eg --patch-file - <<EOF
+$ kubectl patch gateway/eg --patch '
 metadata:
   annotations:
     cert-manager.io/cluster-issuer: selfsigned
@@ -92,7 +92,7 @@ spec:
       certificateRefs:
       - kind: Secret
         name: eg-https
-EOF
+' --type=merge
 ```
 
 You could instead create a new Gateway serving HTTPS, if you'd prefer.

diff --git a/site/content/en/v1.1/tasks/security/tls-cert-manager.md b/site/content/en/v1.1/tasks/security/tls-cert-manager.md
@@ -76,7 +76,7 @@ EOF
 We now have to patch the example Gateway to reference cert-manager:
 
 ```console
-$ kubectl patch gateway/eg --patch-file - <<EOF
+$ kubectl patch gateway/eg --patch '
 metadata:
   annotations:
     cert-manager.io/cluster-issuer: selfsigned
@@ -92,7 +92,7 @@ spec:
       certificateRefs:
       - kind: Secret
         name: eg-https
-EOF
+' --type=merge
 ```
 
 You could instead create a new Gateway serving HTTPS, if you'd prefer.