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

GCE Multizone: Cannot create volumes in non-master zones #27657

Closed
justinsb opened this issue Jun 18, 2016 · 1 comment
Closed

GCE Multizone: Cannot create volumes in non-master zones #27657

justinsb opened this issue Jun 18, 2016 · 1 comment
Assignees
@justinsb
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.3

Comments

@justinsb
Copy link
Member

Due to #27656, users are unable to create volumes in non-master zones. The volume cannot be found, and so effectively only one zone is usable for persistent storage (or, in the case of HA master, none of them are).

Fix coming in the next hour or so...
@justinsb justinsb mentioned this issue Jun 18, 2016
Closed
@justinsb justinsb added this to the v1.3 milestone Jun 18, 2016
@justinsb justinsb added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 18, 2016
@justinsb
Copy link
Member Author

Fix in #27553

@roberthbailey roberthbailey assigned ghost and justinsb Jun 18, 2016
@justinsb justinsb mentioned this issue Jun 20, 2016
Merged
chrislovecnm pushed a commit to chrislovecnm/kubernetes that referenced this issue Jun 21, 2016
@justinsb @chrislovecnm
GCE Multizone: Allow volumes to be created in non-master zone
57ce130 
We had a long-lasting bug which prevented creation of volumes in
non-master zones, because the cloudprovider in the volume label
admission controller is not initialized with the multizone setting
(issue kubernetes#27656).

This implements a simple workaround: if the volume is created with the
failure-domain zone label, we look for the volume in that zone.  This is
more efficient, avoids introducing a new semantic, and allows users (and
the dynamic provisioner) to create volumes in non-master zones.

Fixes kubernetes#27657
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justinsb justinsb

Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.3
Development

No branches or pull requests
1 participant
@justinsb