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.

Sign up for GitHub

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

Jump to bottom

ingress: support one ingress and use hostnames/SNI (allows better letsencrypt support) #16

Open
Cryptophobia opened this issue Mar 20, 2018 · 0 comments
Open

ingress: support one ingress and use hostnames/SNI (allows better letsencrypt support) #16

Cryptophobia opened this issue Mar 20, 2018 · 0 comments

Comments

@Cryptophobia
Copy link
Member

From @tmc on June 12, 2017 2:50

Right now the experimental native ingress creates an ingress per app, this typically implies manual steps, dns records, etc -- lowering the utility and ease.

If native ingress support allowed the utilization of a single ingress in SNI mode converting a deis installation to use letsencrypt via kube-lego would be a single annotation and dns record configuration.

Refs deis/workflow#708

Copied from original issue: deis/workflow#824
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Cryptophobia