use first load balancer class as default if no class with name "default" provided #74
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Co-authored-by: Uwe Krueger uwe.krueger@sap.com
What this PR does / why we need it:
If multiple load balancer classes are defined in a floating pool of the cloud profile constraints, currently the default class must be named "default". If no "default" LB class is provided, the Openstack CCM chooses one by random. With this PR the first load balancer class is used instead.
Additionally it is ensured that the floating network ID from the infrastructure is used for all LB classes.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: