8000 yawol should ignore services with different loadBalancerClass · Issue #164 · stackitcloud/yawol · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

yawol should ignore services with different loadBalancerClass #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

Closed
malt3 opened this issue Apr 27, 2023 · 0 comments · Fixed by #217
Closed

yawol should ignore services with different loadBalancerClass #164

malt3 opened this issue Apr 27, 2023 · 0 comments · Fixed by #217
Assignees

Comments

@malt3
Copy link
Contributor
malt3 commented Apr 27, 2023

When deploying multiple loadbalancer controllers / providers in the same cluster, it is possible to set the loadBalancerClass of the Service spec.

Expected behavior

Yawol should ignore any services that have a loadBalancerClass of a different controller already set.

Actual behavior

Yawol creates a yawollet based on the Service, even if it should belong to a different controller.

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