Skip to content

Commit 40144d8

Browse files
authored
Merge pull request #196446 from tony-schndr/patch-1
Add closing quote to verify egress lockdown command
2 parents 5b56c62 + 0322f9e commit 40144d8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/openshift/concepts-egress-lockdown.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Egress lockdown is enabled by default for new cluster creation. However, to enab
3939
To verify whether egress lockdown is enabled on a cluster, sign in to your Azure cluster and run the following command:
4040

4141
```azurecli
42-
$ oc get cluster.aro.openshift.io cluster -o go-template='{{ if .spec.gatewayDomains }}{{ "Egress Lockdown Feature Enabled" }}{{ else }}{{ "Egress Lockdown Feature Disabled" }}{{ end }}{{ "\n" }}
42+
$ oc get cluster.aro.openshift.io cluster -o go-template='{{ if .spec.gatewayDomains }}{{ "Egress Lockdown Feature Enabled" }}{{ else }}{{ "Egress Lockdown Feature Disabled" }}{{ end }}{{ "\n" }}'
4343
```
4444
Depending on whether egress lockdown is enabled or disabled, you'll see one of the following messages:
4545

@@ -48,4 +48,4 @@ Depending on whether egress lockdown is enabled or disabled, you'll see one of t
4848

4949
## Next steps
5050

51-
For more information on controlling egress traffic on your Azure Red Hat OpenShift cluster, see [Control egress traffic for your Azure Red Hat OpenShift (ARO) cluster (preview)](howto-restrict-egress.md).
51+
For more information on controlling egress traffic on your Azure Red Hat OpenShift cluster, see [Control egress traffic for your Azure Red Hat OpenShift (ARO) cluster (preview)](howto-restrict-egress.md).

0 commit comments

Comments
 (0)