-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation for Client-Cert Authentication misleading #10687
Comments
@clauspruefer Please open a PR to fix the documentation, and we will get it updated. |
/triage accepted |
On the way... |
It is not true, my tests proof, both ways work exact the same:
@strongjz But please review my PR, the updated documentation should be fine now. |
…#10705) * Update README.md Update / restructure "Client Cert Authentication" Documentation sub-section * Update README.md * Update README.md * Update README.md * Update README.md Add openssl subjectAltName and remark for future releases. * Update README.md Moved subjectAltName to new topic "Remarks", i think it is not annotation / ingress related * Update README.md Typo
What happened:
Documentation @ https://kubernetes.github.io/ingress-nginx/examples/auth/client-certs/ contains wrong information about Creating Certificate Secrets.
kubectl create secret generic tls-secret --from-file=tls.crt=server.crt --from-file=tls.key=server.key
does not work in general (2 = signs), also creates a secret of wrong type (correct type should be: tls).What you expected to happen:
kubectl create secret tls tls-secret-name --cert server.crt --key server.key
works fine.NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
NGINX Ingress controller
Release: v1.8.0
Build: 35f5082
Repository: https://github.com/kubernetes/ingress-nginx
nginx version: nginx/1.21.6
Kubernetes version (use
kubectl version
):Client Version: v1.28.4
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.7
Environment:
How to reproduce this issue:
Not required, just documentation fix needed in my oppinion.
The text was updated successfully, but these errors were encountered: