From c835bfc68d19051c11eb3f46ac3ebd5c3745100e Mon Sep 17 00:00:00 2001 From: Michelle Au Date: Thu, 10 Aug 2017 16:04:02 -0700 Subject: [PATCH] Add multizone limitations regarding dynamic provisioning (#4706) --- docs/admin/multiple-zones.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/admin/multiple-zones.md b/docs/admin/multiple-zones.md index acb5cb7061..8963259213 100644 --- a/docs/admin/multiple-zones.md +++ b/docs/admin/multiple-zones.md @@ -73,6 +73,18 @@ available and can tolerate the loss of a zone, the control plane is located in a single zone. Users that want a highly available control plane should follow the [high availability](/docs/admin/high-availability) instructions. +* StatefulSet volume zone spreading when using dynamic provisioning is currently not compatible with +pod affinity or anti-affinity policies. + +* If the name of the StatefulSet contains dashes ("-"), volume zone spreading +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 +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. + ## Walkthrough