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

consider opening HTTP/HTTPS listeners by default #4643

Open
skriss opened this issue Jul 27, 2022 · 0 comments
Open

consider opening HTTP/HTTPS listeners by default #4643

skriss opened this issue Jul 27, 2022 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@skriss
Copy link
Member

skriss commented Jul 27, 2022

Please describe the problem you have
[A clear, concise, description of the problem you are facing. What is the problem that feature X would solve for you?]

Currently, Contour does not open Envoy listeners until there is a vhost/route configured for the relevant protocol. This has caused some challenges with health-checking of LoadBalancers. The maintainers have discussed revisiting this decision and possibly always opening the ports/listeners on startup, regardless of whether there are routes.

xref. #389

@skriss skriss added kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. labels Jul 27, 2022
@sunjayBhatia sunjayBhatia added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Sep 26, 2022
@skriss skriss removed the lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. label Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
Status: No status
Development

No branches or pull requests

2 participants