Skip to content
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

nginx: support multidomain certificates #548

Closed
webattitude opened this issue Apr 3, 2017 · 7 comments · Fixed by #886
Closed

nginx: support multidomain certificates #548

webattitude opened this issue Apr 3, 2017 · 7 comments · Fixed by #886
Assignees

Comments

@webattitude
Copy link

While I think I've understood CN should contains the FQDN, what about alternate subject ?
I can't get my multi wildcard certificate working with all subdomains I want to cover. Typically we have several levels, with few subdomains at each level. How to handle this ?
TIA

@lihan
Copy link
Contributor

lihan commented Apr 13, 2017

+1

@aledbf aledbf self-assigned this Apr 22, 2017
@lihan
Copy link
Contributor

lihan commented Apr 24, 2017

@webattitude How can one generate such a certificate for testing, either using openssl or anything else.

@webattitude
Copy link
Author

I'm using right now Let's encrypt with kube lego, it's awesome.

@lihan
Copy link
Contributor

lihan commented Apr 24, 2017

@webattitude How do you reproduce this issue? Do you mean sub of subdomain like ..example.com or multiple top level domains? Eg. a.com and b.com in one cert?

@webattitude
Copy link
Author

@lihan every type you define can be secured with https, every level of subdomains.

@aledbf
Copy link
Member

aledbf commented Jun 21, 2017

@webattitude please check if the image quay.io/aledbf/nginx-ingress-controller:0.147 solves the issue

@webattitude
Copy link
Author

Ok thanks, I've just replaced the controller with yours, I'll check asap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants