diff --git a/pages/index.md b/pages/index.md index 1ed1f95408c..1777ab191c0 100644 --- a/pages/index.md +++ b/pages/index.md @@ -977,7 +977,7 @@ + [Kubernetes Plugins (CNI, CRI, CSI...) & softwares versions and reserved resources](public_cloud/containers_orchestration/managed_kubernetes/software-versions-reserved-resources) + [Managed Kubernetes End-of-Sale, End-of-Service and End-of-Life policies](public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) + [Exposed APIs, Kubernetes configuration and Feature gates](public_cloud/containers_orchestration/managed_kubernetes/exposed-apis) - + [MKS Premium Plan](public_cloud/containers_orchestration/managed_kubernetes/premium) + + [MKS Standard Plan](public_cloud/containers_orchestration/managed_kubernetes/premium) + [Cluster](public-cloud-containers-orchestration-managed-kubernetes-k8s-cluster) + [Configuring kubectl on an OVHcloud Managed Kubernetes cluster](public_cloud/containers_orchestration/managed_kubernetes/configuring-kubectl-on-an-ovh-managed-kubernetes-cluster) + [Configuring the API server flags on an OVHcloud Managed Kubernetes cluster](public_cloud/containers_orchestration/managed_kubernetes/apiserver-flags-configuration) diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.de-de.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.de-de.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.de-de.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.de-de.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-asia.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-asia.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-asia.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-asia.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-au.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-au.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-au.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-au.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ca.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ca.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ca.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ca.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-gb.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-gb.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-gb.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-gb.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ie.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ie.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ie.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ie.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-sg.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-sg.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-sg.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-sg.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-us.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-us.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-us.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-us.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.es-es.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.es-es.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.es-es.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.es-es.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.es-us.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.es-us.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.es-us.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.es-us.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.fr-ca.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.fr-ca.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.fr-ca.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.fr-ca.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.fr-fr.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.fr-fr.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.fr-fr.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.fr-fr.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.it-it.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.it-it.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.it-it.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.it-it.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.pl-pl.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.pl-pl.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.pl-pl.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.pl-pl.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.pt-pt.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.pt-pt.md index 488f2329143..07683eb9357 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.pt-pt.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.pt-pt.md @@ -26,7 +26,7 @@ updated: 2025-04-30 > [!primary] -> This documentation covers the limitations of the Managed Kubernetes Service Standard Plan. For additional details on the Managed Kubernetes Service Premium plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). +> This documentation covers the limitations of the Managed Kubernetes Service Free Plan. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium). ## Nodes and pods 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 248703aadd6..90e48acff20 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, 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 -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..90e48acff20 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, 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 -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..9690007173b 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | | etcd | Shared, up to 400MB | Dedicated, up to 8GB | | Max cluster size | Up to 100 nodes | Up to 500 nodes | -| Regional availability | Single-zone regions (3-AZ regions planned for 2025) | 3-AZ region for now | +| Regional availability | Single-zone regions | 3-AZ region for now | ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. - -This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. - -### Cluster upgrade - -Upgrading an existing cluster is not supported at the moment, we'll deliver this functionality once we support the next Kubernetes release (1.33). - -### Logs Data Platform integration - -Audit logs forwarding to the [Logs Data Platform](/pages/public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) is not supported at the moment. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. ### ETCD Quota @@ -67,12 +57,6 @@ Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel openstack router show ROUTER_ID -c external_gateway_info ``` -### Anti-affinity - -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). - -We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. - ### Ports The OpenStack security group for worker nodes is the `default` one. It allows all egress and ingress traffic by default on your private network. @@ -104,19 +88,23 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). + +### Reset kubeconfig + +At the moment, it is not possible to reset your kubeconfig file. ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +124,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +149,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +199,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +259,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..9690007173b 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | | etcd | Shared, up to 400MB | Dedicated, up to 8GB | | Max cluster size | Up to 100 nodes | Up to 500 nodes | -| Regional availability | Single-zone regions (3-AZ regions planned for 2025) | 3-AZ region for now | +| Regional availability | Single-zone regions | 3-AZ region for now | ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. - -This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. - -### Cluster upgrade - -Upgrading an existing cluster is not supported at the moment, we'll deliver this functionality once we support the next Kubernetes release (1.33). - -### Logs Data Platform integration - -Audit logs forwarding to the [Logs Data Platform](/pages/public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) is not supported at the moment. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. ### ETCD Quota @@ -67,12 +57,6 @@ Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel openstack router show ROUTER_ID -c external_gateway_info ``` -### Anti-affinity - -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). - -We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. - ### Ports The OpenStack security group for worker nodes is the `default` one. It allows all egress and ingress traffic by default on your private network. @@ -104,19 +88,23 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). + +### Reset kubeconfig + +At the moment, it is not possible to reset your kubeconfig file. ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +124,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +149,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +199,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +259,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file 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 248703aadd6..baa1709b606 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-06-05 +title: MKS Standard Plan +excerpt: 'Features and limitations of the MKS Standard Plan in Beta version' +updated: 2025-09-10 --- > [!primary] -> This document describes the features and "how-to" for the Managed Kubernetes Service Premium Plan currently in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). +> This document describes the features and "how-to" for the Managed Kubernetes Service Standard Plan currently in beta version. For additional details on the Managed Kubernetes Service Free plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). -## Standard vs Premium comparison +## Free vs Standard comparison -| Plan | Standard | Premium | +| Plan | Free | Standard | | --------------------- | --------------------------------------------------- | ----------------------------------------- | | ControlPlane | Managed | Managed & Cross-AZ resilient | | Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | @@ -40,7 +40,7 @@ updated: 2025-06-05 ## Limitations / Upcoming features -In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features. This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025. @@ -69,7 +69,7 @@ openstack router show ROUTER_ID -c external_gateway_info ### Anti-affinity -This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Premium Plan (region EU-WEST-PAR). +This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR). We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ. @@ -104,19 +104,19 @@ 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`. +MKS Standard 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). +To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume). ## Getting started ### Prerequisites -To create an MKS Premium cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. +To create an MKS Standard cluster, a private network and subnet with an attached [OVHcloud Gateway](/links/public-cloud/gateway) (an OpenStack router) is mandatory. Before starting the cluster creation process, please make sure that you have an existing subnet that meets these requirements or create a new one accordingly. If you want to use an use an existing subnet: @@ -136,9 +136,9 @@ If you want to use an use an existing subnet: > ![network-creation](images/network-creation01.png){.thumbnail} > -### Create a MKS Premium cluster +### Create a MKS Standard cluster -The following methods are supported to create an MKS Premium cluster: +The following methods are supported to create an MKS Standard cluster: > [!tabs] > Using the OVHcloud Control Panel @@ -161,7 +161,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> ![Location](images/creating-a-cluster4.png){.thumbnail} >> ->> Select the `Premium`{.action} plan and click `Next`{.action}. +>> Select the `Standard`{.action} plan and click `Next`{.action}. >> >> ![Plan](images/creating-a-cluster5.png){.thumbnail} >> @@ -211,7 +211,7 @@ The following methods are supported to create an MKS Premium cluster: >> >> Refer to the [dedicated documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/creating-a-cluster) to create a Managed Kubernetes cluster. >> ->> Here is a sample Terraform file that creates an MKS Premium cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. +>> Here is a sample Terraform file that creates an MKS Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. >> >> ```bash >> terraform { @@ -271,4 +271,4 @@ The following methods are supported to create an MKS Premium cluster: - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. -- Join our [community of users on Discord](https://discord.gg/ovhcloud)! +- Join our [community of users on Discord](https://discord.gg/ovhcloud)! \ No newline at end of file diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster5.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster5.png index b334280b2a7..9d07999f885 100644 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster5.png and b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster5.png differ 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 1d302ed01d8..5a0521f09d1 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 a7029451234..76dacc6b1cd 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 3865b78576c..67f785c34ec 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 fdc1ec53ce7..72f5fe04a71 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 ca80fade928..19c609e2925 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 ec2d9011851..13262c0a27a 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 fd9fe37970e..a9a72b46c4d 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 048bf6c0b33..5b929c06658 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 c71b2ea7686..91d299b34d2 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 5e4c3e0368f..d7983903c74 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 c11c6b6369e..b2d0a80eabb 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 cf0cb604d4f..14aa4ca853c 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 801869bf3d4..dd51402fdaa 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 c20fbfe97ed..1a0771db808 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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 446bef98526..c9e39675bf7 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 @@ -182,7 +182,7 @@ We currently support the following [Storage Classes](https://kubernetes.io/docs/ * `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). (Not supported yet on [MKS Premium plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium#storage-classes)). +* `csi-cinder-classic` uses traditional spinning disks (200 IOPS guaranteed, Up to 64 MB/s per volume). (Not supported yet on [MKS Standard 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.