From 07b85817b6b474203a0f04058ebe7d0915b4ad3b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Claus=20Pr=C3=BCfer?= Date: Tue, 5 Dec 2023 00:12:09 +0100 Subject: [PATCH] Update README.md --- docs/examples/auth/client-certs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/examples/auth/client-certs/README.md b/docs/examples/auth/client-certs/README.md index 876edf644..9c78c966c 100644 --- a/docs/examples/auth/client-certs/README.md +++ b/docs/examples/auth/client-certs/README.md @@ -79,7 +79,7 @@ Now we are able to reference the created secrets in the ingress definition. | Annotation | Description | Remark | |---------------------------------------------------------------------------|----------------------------|--------------------| | nginx.ingress.kubernetes.io/auth-tls-verify-client: "on" | Activate Client-Auth | If "on", verify client Certificate | -| nginx.ingress.kubernetes.io/auth-tls-secret: "default/ca-secret" | CA "secret" reference | Secret namespace and service / ingress namespace must match | +| nginx.ingress.kubernetes.io/auth-tls-secret: "namespace/ca-secret" | CA "secret" reference | Secret namespace and service / ingress namespace must match | | nginx.ingress.kubernetes.io/auth-tls-verify-depth: "1" | CA "chain" depth | How many CA levels should be processed | | nginx.ingress.kubernetes.io/auth-tls-pass-certificate-to-upstream: "true" | Pass Cert / Header | Pass Certificate to Web-App for e.g. parsing Client E-Mail Address x.509 Property |