Fix yaml and docs for verifyClient in ingressMTLS

nginx · Oct 2, 2020 · b735d5d · b735d5d
1 parent 9040697
commit b735d5d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs-web/configuration/policy-resource.md b/docs-web/configuration/policy-resource.md
@@ -275,7 +275,7 @@ For example, the following policy will verify a client certificate using the CA
 ```yaml
 ingressMTLS:
   clientCertSecret: ingress-mtls-secret
-  verifyClient: on
+  verifyClient: "on"
   verifyDepth: 1
 ```
 
@@ -314,7 +314,7 @@ We use the `requestHeaders` of the [Action.Proxy](/nginx-ingress-controller/conf
      - ``string``
      - Yes
    * - ``verifyClient``
-     - Verification for the client. Possible values are ``on``, ``off``, ``optional``, ``optional_no_ca``. The default is ``on``.
+     - Verification for the client. Possible values are ``"on"``, ``"off"``, ``"optional"``, ``"optional_no_ca"``. The default is ``"on"``.
      - ``string``
      - No
    * - ``verifyDepth``

diff --git a/examples-of-custom-resources/ingress-mtls/ingress-mtls.yaml b/examples-of-custom-resources/ingress-mtls/ingress-mtls.yaml
@@ -5,5 +5,5 @@ metadata:
 spec:
   ingressMTLS:
     clientCertSecret: ingress-mtls-secret
-    verifyClient: on
+    verifyClient: "on"
     verifyDepth: 1