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

Update docs with topology aware dynamic provisioning #9939

Merged
merged 5 commits into from
Sep 11, 2018
Merged

Update docs with topology aware dynamic provisioning #9939

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9bdfeae
Document topology aware volume binding feature
msau42 Sep 7, 2018
6655d3f
update for readability
zparnold Sep 9, 2018
c11b1de
Update storage-classes.md
zparnold Sep 9, 2018
8f7001f
comma splice
zparnold Sep 9, 2018
9988866
don't abbreviate
msau42 Sep 10, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
comma splice
  • Loading branch information
@zparnold
zparnold authored Sep 9, 2018
commit 8f7001f024c02ff34573c0999eef71a5007b02a7
2 changes: 1 addition & 1 deletion content/en/docs/setup/multiple-zones.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ The following limitations are addressed with [topology-aware volume binding](/do
may not provide a uniform distribution of storage across zones.

* When specifying multiple PVCs in a Deployment or Pod spec, the StorageClass
needs to be configured for a specific, single zone, or the PVs need to be
needs to be configured for a specific single zone, or the PVs need to be
statically provisioned in a specific zone. Another workaround is to use a
StatefulSet, which will ensure that all the volumes for a replica are
provisioned in the same zone.
Expand Down