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

Clarify port clash failure mode #56

Closed
bprashanth opened this issue Dec 13, 2016 · 0 comments · Fixed by #1239
Closed

Clarify port clash failure mode #56

bprashanth opened this issue Dec 13, 2016 · 0 comments · Fixed by #1239
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@bprashanth
Copy link
Contributor

If an ingress controller can't start because of port conflict (eg: #54 (comment)) it should throw an event and log. This is not an issue if the controller doesn't need a host port (100% cloud-provider).

@bprashanth bprashanth added bug help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Dec 13, 2016
@aledbf aledbf added this to TODO in nginx 0.9-beta.11 Jun 30, 2017
@aledbf aledbf moved this from TODO to In Progress in nginx 0.9-beta.11 Jul 2, 2017
@aledbf aledbf moved this from In Progress to TODO in nginx 0.9-beta.11 Jul 14, 2017
@aledbf aledbf added this to TODO in nginx 0.9-beta.12 Jul 14, 2017
@aledbf aledbf moved this from TODO to done in nginx 0.9-beta.12 Aug 27, 2017
haoqing0110 referenced this issue in stolostron/management-ingress Mar 5, 2021
Co-authored-by: Song Song Li <ssli@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
No open projects
1 participant