-
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
Client Certificate Auth does not work in 0.12.0 #2259
Comments
can you paste the diff of nginx.conf that generated by two version of ingress-nginx? |
I am also seeing this issue after upgrading from 0.11.0 to 0.12.0 My environment is slightly different: Environment: And my Ingress resource has the following annotations:
The diff between the 0.11.0 and 0.12.0 nginx.conf looks like (just showing the
To me, that indicates that at template rendering time |
@ant1441 thank you for finding the issue. That removal was a mistake. |
@ant1441 please use |
Looks good, thanks 👍 |
NGINX Ingress controller version: 0.12.0
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-09T21:51:06Z", GoVersion:"go1.9.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.7", GitCommit:"b30876a5539f09684ff9fde266fda10b37738c9c", GitTreeState:"clean", BuildDate:"2018-01-16T21:52:38Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
uname -a
): 4.9.0-5-amd64What happened:
i have some ingresses annotated to use client certificate authentication:
these work in the controller in version 0.11.0 but not in 0.12.0
What you expected to happen:
client auth to be configured for the host
How to reproduce it (as minimally and precisely as possible):
Configure an ingress with client certificate auth and check if it is enabled
Anything else we need to know:
Downgrading to 0.11.0 solved my problem, i was trying to track down the changes from 0.11.0 to 0.12.0 but did not figure out why this is not working anymore :-|
The text was updated successfully, but these errors were encountered: