Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

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

Open
tmc opened this issue Jun 12, 2017 · 1 comment
Open

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

tmc opened this issue Jun 12, 2017 · 1 comment

Comments

@tmc
Copy link

tmc commented Jun 12, 2017 •
edited
Loading

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 #708
@tmc tmc changed the title ingress: support one ingress and use hostnames/SNI (allows better let's encrypt support) ingress: support one ingress and use hostnames/SNI (allows better letsencrypt support) Jun 12, 2017
@Cryptophobia Cryptophobia mentioned this issue Mar 20, 2018
Open
@Cryptophobia
Copy link

This issue was moved to teamhephy/workflow#16

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tmc @Cryptophobia