-
Notifications
You must be signed in to change notification settings - Fork 82
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
Allow multiple loadBalancerProviders as the default and for a region #841
Allow multiple loadBalancerProviders as the default and for a region #841
Conversation
@lotharbach Thank you for your contribution. |
Thank you @lotharbach for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below. |
/reviewed ok-to-test |
/needs rebase |
1679f9e
to
650fee3
Compare
Co-authored-by: Konstantinos Angelopoulos <[email protected]>
Rebased & thanks for your suggestions @kon-angelo! |
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.
/lgtm
How to categorize this PR?
/area networking
/kind enhancement
/platform openstack
What this PR does / why we need it:
We are adding a new openstack region that uses the OVN networking stack, and also the octavia OVN loadbalancer provider that has some worthwhile advantages. But since OVN is also still missing features we want to also allow the well known amphora provider in parallel.
Currently the cloudprofile/controlplane validation does not allow multiple entries for a region.
The Shoot spec validation has always required to specify a loadBalancerProvider even when there is only a single choice, the behavior for a given shoot should stay the same, and the behavior with existing cloudprofiles should also be the same until you add multiple loadBalancerProviders.
Which issue(s) this PR fixes:
Fixes #862
Release note: