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

ingress/routesrv: Makes skipper_routesrv_enabled a three state switch #4940

Merged
merged 1 commit into from
Jan 27, 2022

Conversation

AlexanderYastrebov
Copy link
Member

Signed-off-by: Alexander Yastrebov [email protected]

@@ -1,4 +1,4 @@
{{ if ne .ConfigItems.skipper_routesrv_enabled "true" }}
{{ if ne .ConfigItems.skipper_routesrv_enabled "false" }}
Copy link
Member Author

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
Copy link
Member Author

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

Copy link
Member

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.

@AlexanderYastrebov AlexanderYastrebov mentioned this pull request Jan 26, 2022
@AlexanderYastrebov AlexanderYastrebov force-pushed the routesrv-three-state-config branch from eddb7f8 to d4f18a1 Compare January 27, 2022 09:56
@aryszka
Copy link
Contributor

aryszka commented Jan 27, 2022

👍

1 similar comment
@mikkeloscar
Copy link
Contributor

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants