-
Notifications
You must be signed in to change notification settings - Fork 164
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
ingress/routesrv: Makes skipper_routesrv_enabled a three state switch #4940
Conversation
@@ -1,4 +1,4 @@ | |||
{{ if ne .ConfigItems.skipper_routesrv_enabled "true" }} | |||
{{ if ne .ConfigItems.skipper_routesrv_enabled "false" }} |
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.
Fixes a wrong condition introduced by #4937
# skipper_routesrv_enabled is a three state switch: | ||
# - "false" - routesrv deployment is removed, skipper uses own k8s dataclient | ||
# - "pre" - routesrv is deployed, skipper uses own k8s dataclient | ||
# - "exec" - routesrv is deployed, skipper uses routesrv |
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.
Used exec
instead of true
similar to nlb_switch
and to hint that its a three state config
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.
no that's not needed here. skipper-ingress waits for first successful route load and routesrv has the time to startup before it hurts skipper-ingress.
Signed-off-by: Alexander Yastrebov <[email protected]>
eddb7f8
to
d4f18a1
Compare
👍 |
1 similar comment
👍 |
Signed-off-by: Alexander Yastrebov [email protected]