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.

Sign up for GitHub

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

Jump to bottom

Remove zone from ControlPlaneConfig #61

Closed
rfranzke opened this issue Apr 14, 2020 · 2 comments · Fixed by #65
Closed

Remove zone from ControlPlaneConfig #61

rfranzke opened this issue Apr 14, 2020 · 2 comments · Fixed by #65
Assignees
@rfranzke
Labels
kind/enhancement Enhancement, improvement, extension

Comments

@rfranzke
Copy link
Member

What would you like to be added:
The zone field should be removed from the ControlPlaneConfig. It was taken over during extensibility from the in-tree behaviour, but it is not needed. In fact, it only influences the zone parameter in the default StorageClass that gets installed to the shoot cluster, though, this does not work well with multi-zone shoots. The default behaviour of the Cinder volume plugin - if no zone parameter is specified - is to randomize the zones.

Why is this needed:
Better default configuration for OpenStack shoots.
@rfranzke rfranzke added the kind/enhancement Enhancement, improvement, extension label Apr 14, 2020
@rfranzke
Copy link
Member Author

cc @timuthy

@rfranzke
Copy link
Member Author

FYI: Similar PR for Alicloud was opened: gardener/gardener-extension-provider-alicloud#64

@rfranzke rfranzke self-assigned this Apr 16, 2020
@rfranzke rfranzke mentioned this issue Apr 17, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rfranzke rfranzke

Labels
kind/enhancement Enhancement, improvement, extension
Projects
None yet
Milestone
No milestone
1 participant
@rfranzke