SSL client certificate authentication at kubernetes level and nginx ingress as a Defaultbackend

kubernetes / ingress-nginx

Ingress-NGINX Controller for Kubernetes

https://kubernetes.github.io/ingress-nginx/

Apache License 2.0

16.91k stars 8.14k forks source link

SSL client certificate authentication at kubernetes level and nginx ingress as a Defaultbackend #11507

Open rahulsyal92 opened 3 days ago

rahulsyal92 commented 3 days ago

Hello,

I want to do SSL client certificate authentication at pod level when using nginx ingress controller as a default backend. I referred the document (https://github.com/kubernetes/ingress-nginx/blob/main/docs/examples/auth/client-certs/ingress.yaml) and still not able to get pop up to insert my certificate. At logs level i got certificate required and error code as 404 found. Please suggest to proceed beyond this. Sharing my nginx ingress yaml file as:

apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: env-ingress namespace: ns annotations: nginx.ingress.kubernetes.io/backend-protocol: HTTPS nginx.ingress.kubernetes.io/ssl-passthrough: 'true' spec: defaultBackend: service: name: svc-name port: number: 9443 ingressClassName: nginx

k8s-ci-robot commented 3 days ago

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

longwuyuan commented 3 days ago

/remove-kind feature /kind support /triage needs-information

Hi @rahulsyal92

Please click on the button to create a new bug report and look at the template there that asks many questions
Then edit this issue and use that template to answer those questions in the description of this issue
Make sure to add commands and outputs of your cluster that produced the problem. For example, incluse the kubectl describe commands and the outputs of all related resources like
- controller pod, svc, secrets
- app pod, svc, secrets, ingress
- curl command or browser request
- logs of controller
- anything else that is related
- how you obtained certificates
- screenshots if using browser