From 4a04547c0a57e2023e184936892259debe8a62e4 Mon Sep 17 00:00:00 2001 From: Hassan BENHZAINE Date: Fri, 26 Jan 2024 21:43:54 +0100 Subject: [PATCH] Modified storage access for zone and deleted PersistentVolumeLabel since its deprecated s --- .../en/docs/setup/best-practices/multiple-zones.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/content/en/docs/setup/best-practices/multiple-zones.md b/content/en/docs/setup/best-practices/multiple-zones.md index 3bce1669372fe..f9ff827946783 100644 --- a/content/en/docs/setup/best-practices/multiple-zones.md +++ b/content/en/docs/setup/best-practices/multiple-zones.md @@ -95,13 +95,16 @@ such as Deployment, StatefulSet, or Job. ## Storage access for zones -When persistent volumes are created, the `PersistentVolumeLabel` -[admission controller](/docs/reference/access-authn-authz/admission-controllers/) -automatically adds zone labels to any PersistentVolumes that are linked to a specific -zone. The {{< glossary_tooltip text="scheduler" term_id="kube-scheduler" >}} then ensures, +When persistent volumes are created, Kubernetes automatically adds zone labels +to any PersistentVolumes that are linked to a specific zone. +The {{< glossary_tooltip text="scheduler" term_id="kube-scheduler" >}} then ensures, through its `NoVolumeZoneConflict` predicate, that pods which claim a given PersistentVolume are only placed into the same zone as that volume. +Please note that the method of adding zone labels can depend on your +cloud provider and the storage provisioner you’re using. Always refer to the specific +documentation for your environment to ensure correct configuration. + You can specify a {{< glossary_tooltip text="StorageClass" term_id="storage-class" >}} for PersistentVolumeClaims that specifies the failure domains (zones) that the storage in that class may use.