Add multizone limitations regarding dynamic provisioning (#4706)
This commit is contained in:
committed by
Zachary Corleissen
parent
cc7cadb138
commit
c835bfc68d
@@ -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
|
located in a single zone. Users that want a highly available control
|
||||||
plane should follow the [high availability](/docs/admin/high-availability) instructions.
|
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
|
## Walkthrough
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user