8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
When deploying multiple loadbalancer controllers / providers in the same cluster, it is possible to set the loadBalancerClass of the Service spec.
loadBalancerClass
Service
Yawol should ignore any services that have a loadBalancerClass of a different controller already set.
Yawol creates a yawollet based on the Service, even if it should belong to a different controller.
The text was updated successfully, but these errors were encountered:
service.spec.loadBalancerClass
dergeberl
Successfully merging a pull request may close this issue.
When deploying multiple loadbalancer controllers / providers in the same cluster, it is possible to set the
loadBalancerClass
of theService
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.The text was updated successfully, but these errors were encountered: