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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
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
index 81b3068a0a0..248703aadd6 100644
--- 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
@@ -1,7 +1,7 @@
 ---
 title: MKS Premium Plan
 excerpt: 'Features and limitations of the MKS Premium Plan in Beta version'
-updated: 2025-05-27
+updated: 2025-06-05
 ---
 
 <style>
@@ -102,6 +102,16 @@ The following ranges are used by the cluster, and should not be used elsewhere o
 
 These ranges will be configurable in a future version.
 
+### Storage classes
+
+MKS Premium only supports two out of the [three Storage Classes on OVHcloud Managed Kubernetes](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume#storage-classes): `csi-cinder-high-speed` and `csi-cinder-high-speed-gen2`.
+
+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 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).
+
 ## Getting started
 
 ### Prerequisites
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.de-de.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.de-de.md
index 25733e4e295..cbd91972682 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.de-de.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-asia.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-asia.md
index 7a92c7a9601..2a5963d1e5c 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-asia.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-au.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-au.md
index 4cb5e1e23f3..dba6c52e0ed 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-au.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ca.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ca.md
index 0a375a54a5d..1c0c7811454 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ca.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-gb.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-gb.md
index 01752eaf2e6..534a6dccccc 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-gb.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ie.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ie.md
index 1605c625296..92990dc96f6 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ie.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-sg.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-sg.md
index 629674ad89a..08de4c940e5 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-sg.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-us.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-us.md
index 43ef53000cc..2982579fdc1 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-us.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-es.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-es.md
index 3b84cbe4e5a..d6875797a40 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-es.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-us.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-us.md
index 0275fa9a68b..e2d6027b6f8 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-us.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-ca.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-ca.md
index 336206eabe0..85cbaea025e 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-ca.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-fr.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-fr.md
index a2b8fc450f1..b57a9466b57 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-fr.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.it-it.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.it-it.md
index 628682ab132..5098608fcb1 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.it-it.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pl-pl.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pl-pl.md
index 3f3636ee92c..4d14a2f3e13 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pl-pl.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.
 
diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pt-pt.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pt-pt.md
index 4ed6e4150c7..bf3ac991856 100644
--- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pt-pt.md
+++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: Setting-up a Persistent Volume on OVHcloud Managed Kubernetes
 excerpt: 'Find out how to create Persistent Volume Claim (PVC) and Persistent Volumes (PV), attach a Pod to a PVC, change PV reclaim policy and delete created objects'
-updated: 2024-08-14
+updated: 2025-06-05
 ---
 
 In this tutorial we are going to guide you through a simple example of setting-up a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on your OVHcloud Managed Kubernetes Service.
@@ -178,11 +178,11 @@ Events:
 
 ## Storage Classes
 
-We currently support three [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:
+We currently support the following [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) on OVHcloud Managed Kubernetes:s
 
 * `csi-cinder-high-speed-gen2` storage class is based on hardware that includes SSD disks with NVMe interfaces. The performance allocation is progressive and linear (30 IOPS allocated per GB and 0.5MB/s allocated per GB) with a maximum of 20k IOPS and 1GB/s per volume. The IOPS and bandwidth performance will increase as  scale up the storage space.
 * `csi-cinder-high-speed` performance is fixed. You will get up to 3,000 IOPS per volume, regardless of the volume size. 
-* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). 
+* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)).
 
 All these `Storage Classes` are based on Cinder, the OpenStack block storage service. The difference between them is the associated physical storage device. They are distributed transparently, on three physical local replicas.