-
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
enable-ssl-chain-completion=false not respected #1977
Comments
@magowant please use |
@magowant i'd go back to using 0.9.0 until this fix is merged into a newer 0.10 release. |
I've tested quay.io/aledbf/nginx-ingress-controller:0.321 and it fixed the issue - thanks |
@magowant are you going to stick with this quay.io/aledbf/nginx-ingress-controller:0.321 or wait for the official release? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
NGINX Ingress controller version: 0.10.1
Kubernetes version (use
kubectl version
): 1.8.3Environment:
uname -a
):3.10.0-693.2.2.el7.x86_64nginx-ingress-controller argument:
--enable-ssl-chain-completion=false
What happened:
Upgrading from 0.8.3 to 0.10.1 failed to generate certs for all of our ingress rules, with the following error:
E0125 07:17:42.342892 5 backend_ssl.go:146] unexpected error generating SSL certificate with full intermediate chain CA certs: Get ldap:///***redacted Active Directory DN*** : unsupported protocol scheme "ldap"
Our x509 certs do not include the full cert chain (which I know is not correct, but 0.8.3 handled this gracefully). The certs do contain the following AIA
It seems that the nginx-ingress-controller is attempting to download the cert from the ldap URL despite
--enable-ssl-chain-completion=false
.What you expected to happen:
No attempt should be made to automatically complete the certificate chain, just use the certificate as supplied in the ingress secret.
How to reproduce it (as minimally and precisely as possible):
I can supply a test certificate / key pair on request.
Anything else we need to know:
The text was updated successfully, but these errors were encountered: