reformulation about multi-attach

maxime.hubert · maxime.hubert · commit c280eefb1a12 · 2025-06-05T12:09:36.000+02:00
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.de-de.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.de-de.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-asia.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-asia.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-au.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-au.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-ca.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-ca.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-gb.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-gb.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-ie.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-ie.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-sg.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-sg.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-us.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-us.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.es-es.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.es-es.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.es-us.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.es-us.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.fr-ca.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.fr-ca.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.fr-fr.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.fr-fr.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.it-it.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.it-it.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.pl-pl.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.pl-pl.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.pt-pt.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.pt-pt.md
@@ -108,7 +108,7 @@ MKS Premium only supports two out of the [three Storage Classes on OVHcloud Mana
 
 They allow to create **zone specific** volumes: a PVC provisioned on a zone `X` will only be accessible from the nodes on the zone `X`.
 
-The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported for MKS clusters yet, since the supported file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions.
+The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
 To create a volume on MKS Premium, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
