-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[nginx-ingress-controller] Readiness probe that works behind a CP lb #1749
[nginx-ingress-controller] Readiness probe that works behind a CP lb #1749
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome! thanks just the one nit
@@ -265,6 +265,12 @@ http { | |||
{{ end }} | |||
|
|||
{{ if eq $server.Name "_" }} | |||
# health checks in cloud providers require the use of port 80 | |||
location /ingress-controller-healthz { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you make this the default, and allow people to config it through yaml?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using a flag with /ingress-controller-healthz
as default is ok?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason it shouldn't be a flag? if i have an ingress controller behind an ingress controller how would i modify it :)
048251c
to
9cbcf36
Compare
Thanks LGTM, modifying title to note have wip |
oh please add a todo to scrub incoming ingresses for the url passed through the arg (can come laters, or just file a bug so we can track it) |
done #1754 |
recomputing cla status... |
Automatic merge from submit-queue |
…heck Automatic merge from submit-queue [nginx-ingress-controller] Readiness probe that works behind a CP lb fixes kubernetes-retired#1507
fixes #1507
This change is