diff --git a/pages/index.md b/pages/index.md index 94e8de20140..2b75ada978e 100644 --- a/pages/index.md +++ b/pages/index.md @@ -1050,7 +1050,6 @@ + [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 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/migration-from-free-to-standard/guide.en-gb.md b/pages/public_cloud/containers_orchestration/managed_kubernetes/migration-from-free-to-standard/guide.en-gb.md index 8c0a459ac00..42f30abcd01 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/migration-from-free-to-standard/guide.en-gb.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/migration-from-free-to-standard/guide.en-gb.md @@ -28,7 +28,7 @@ To successfully update your Kubernetes cluster plan within OVHcloud, ensure you While this guide focuses on your current plan, it can be helpful to understand the differences between the Free and Standard plans. The Standard plan offers additional features such as cross-AZ resilience, higher availability SLA, dedicated etcd, and larger maximum cluster size. -For a complete overview, including a detailed comparison table between Free and Standard, please refer to the **Free vs Standard comparison** part of our [MKS Standard Plan](/pages/public_cloud/containers_orchestration/managed_kubernetes/premium) guide. The table in that guide provides a clear side-by-side comparison of key features. +For a complete overview, including a detailed comparison table between Free and Standard, please refer to the **Free vs Standard comparison** part of our guide [Choosing the right OVHcloud Managed Kubernetes Plan: Free or Standard](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide. The table in that guide provides a clear side-by-side comparison of key features. ## Instructions 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.de-de.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-asia.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-au.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-ca.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 1bcc9fe569d..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-gb.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! \ 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-ie.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-sg.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-us.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.es-es.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.es-us.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.fr-ca.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.fr-fr.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.it-it.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.pl-pl.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! 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 deleted file mode 100644 index 30a635c80e3..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.pt-pt.md +++ /dev/null @@ -1,262 +0,0 @@ ---- -title: MKS Standard Plan -excerpt: 'Features and limitations of the MKS Standard' -updated: 2025-09-10 ---- - - - -> [!primary] -> 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). - -## Free vs Standard comparison - -| 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 region for now | - -## Limitations / Upcoming 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. - -### ETCD Quota - -Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster. - -### API Server IP restrictions - -To enable IP filtering on the API server, the IP of the gateway in the cluster's OpenStack subnet should be specified. -This allows worker nodes to communicate with the API server. - -Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel](/links/manager), or by using the following command: - -```bash -openstack router show ROUTER_ID -c external_gateway_info -``` - -### 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. - -```bash -openstack security group rule list default -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | -| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | -| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | -| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | -+--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ -``` - -For now it is recommended to leave these security rules in their "default" configuration or the nodes could be disconnected from the cluster. - -### Reserved IP ranges - -The following ranges are used by the cluster, and should not be used elsewhere on the private network attached to the cluster. - -```text -10.240.0.0/13 # Subnet used by pods -10.3.0.0/16 # Subnet used by services -``` - -These ranges will be configurable in a future version. - -### Storage classes - -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 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 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: - -- **If the Subnet's GatewayIP is already used by an OVHcloud Gateway**, nothing needs to be done. The current OVHcloud Gateway (OpenStack Router) will be used. -- **If the subnet does not have an IP reserved for a Gateway**, you will have to provide or create a compatible subnet. Two options are available: - - Edit an existing subnet to reserve an IP for a Gateway: please refer to the [Update a subnet properties](/pages/public_cloud/public_cloud_network_services/configuration-04-update_subnet) documentation, then create a gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) -- **If the GatewayIP is already assigned to a non-OVHcloud Gateway (OpenStack Router)**. - - Provide another compatible subnet: a subnet with an existing OVHcloud Gateway ([Creating a private network with Gateway](/links/public-cloud/gateway)) - -> [!primary] -> Please remember to avoid the MKS Reserved IP ranges (cf above) for your networkd CIDR - -> [!primary] -> Using the OVHcloud Control Panel, make sure to check the `Declare the first address of a CIDR given as the default gateway (DHCP option 3)` and `Assign a Gateway and connect to the private network` boxes at network creation. -> -> ![network-creation](images/network-creation01.png){.thumbnail} -> - -### Create a MKS Standard cluster - -The following methods are supported to create an MKS Standard cluster: - -> [!tabs] -> Using the OVHcloud Control Panel ->> ->> Log in to the [OVHcloud Control Panel](/links/manager), go to `Public Cloud`{.action} and select the Public Cloud project where you want to deploy the cluster. ->> ->> Access the OVHcloud Managed Kubernetes Service by clicking on `Managed Kubernetes Service`{.action} under Containers & Orchestration in the left-hand menu and click on `Create a cluster`{.action}. ->> ->> ![Create a cluster](images/creating-a-cluster1.png){.thumbnail} ->> ->> Enter a name for your cluster. ->> ->> ![Enter a name](images/creating-a-cluster2.png){.thumbnail} ->> ->> Select '3-AZ Region' as deployment mode. ->> ->> ![Deployment mode](images/creating-a-cluster3.png){.thumbnail} ->> ->> Select 'Paris (EU-WEST-PAR)' as location. ->> ->> ![Location](images/creating-a-cluster4.png){.thumbnail} ->> ->> Select the `Standard`{.action} plan and click `Next`{.action}. ->> ->> ![Plan](images/creating-a-cluster5.png){.thumbnail} ->> ->> Choose the minor version of Kubernetes and the Security Policy. ->> ->> > [!primary] ->> > We recommend to always use the lastest stable version. ->> > Please read our [End of life / end of support](/pages/public_cloud/containers_orchestration/managed_kubernetes/eos-eol-policies) page to understand our version policy. ->> ->> ![Version](images/creating-a-cluster6.png){.thumbnail} ->> ->> Select a private network for your cluster. ->> ->> ![Version](images/creating-a-cluster7.png){.thumbnail} ->> ->> Select a private subnet for your cluster. ->> ->> ![Version](images/creating-a-cluster8.png){.thumbnail} ->> ->> (Optional) Now you can configure your nodepools. A node pool is a group of nodes sharing the same configuration, allowing you a lot of flexibility in your cluster management. Enter a name and select the instance flavor. ->> ->> ![Version](images/creating-a-cluster9.png){.thumbnail} ->> ->> Select the Availability Zone for your node pool. ->> ->> ![Version](images/creating-a-cluster10.png){.thumbnail} ->> ->> Define the size of your first node pool. ->> ->> You can enable the `Autoscaling`{.action} feature for the cluster. Define the minimum and maximum pool size in that case. ->> ->> ![Version](images/creating-a-cluster12.png){.thumbnail} ->> ->> Click `Add node pool`{.action}. ->> ->> ![Version](images/creating-a-cluster13.png){.thumbnail} ->> ->> If you want to create a nodepool on each Availability Zone you can repeat this operation by clicking the `Add node pool`{.action} button again and changing the AZ parameter. ->> ->> Finally, click the `Confirm cluster`{.action} button. ->> ->> ![Version](images/creating-a-cluster14.png){.thumbnail} ->> ->> The cluster creation is now in progress. It should be available within a few minutes in your OVHcloud Control Panel. ->> -> Using Terraform ->> ->> 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 Standard cluster and three nodepools on three different availability zones in the `EU-WEST-PAR` region. ->> ->> ```bash ->> terraform { ->> required_providers { ->> ovh = { ->> source = "ovh/ovh" ->> } ->> } ->> } ->> ->> provider "ovh" { ->> endpoint = "ovh-eu" ->> application_key = "" ->> application_secret = "" ->> consumer_key = "" ->> } ->> ->> resource "ovh_cloud_project_kube" "my_kube_cluster" { ->> service_name = var.service_name ->> name = "lgr-terraform-test-3az" ->> region = "EU-WEST-PAR" ->> version = "1.31" ->> private_network_id = "" ->> nodes_subnet_id = "" ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_a" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-a-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-a"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_b" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-b-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-b"] ->> desired_nodes = 1 ->> } ->> resource "ovh_cloud_project_kube_nodepool" "node_pool_c" { ->> service_name = var.service_name ->> kube_id = ovh_cloud_project_kube.my_kube_cluster.id ->> name = "my-pool-c-1" ->> flavor_name = "b3-8" ->> availability_zones = ["eu-west-par-c"] ->> desired_nodes = 1 ->> } ->> output "kubeconfig_file" { ->> value = ovh_cloud_project_kube.my_kube_cluster.kubeconfig ->> sensitive = true ->> } ->> ``` - -## Go further - -- 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)! diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster1.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster1.png deleted file mode 100644 index e19fd240de1..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster1.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster10.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster10.png deleted file mode 100644 index c778fd947c5..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster10.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster11.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster11.png deleted file mode 100644 index 260d3253cb3..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster11.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster12.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster12.png deleted file mode 100644 index 56b7a42e7ee..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster12.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster13.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster13.png deleted file mode 100644 index bc1afd5187e..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster13.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster14.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster14.png deleted file mode 100644 index 44266bfb037..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster14.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster2.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster2.png deleted file mode 100644 index c1a34fdfdf9..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster2.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster3.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster3.png deleted file mode 100644 index fe1194a8314..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster3.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster4.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster4.png deleted file mode 100644 index 73551d2aea3..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster4.png and /dev/null differ 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 deleted file mode 100644 index 9d07999f885..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster5.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster6.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster6.png deleted file mode 100644 index 637cc35c99d..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster6.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster7.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster7.png deleted file mode 100644 index b06f4aa6378..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster7.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster8.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster8.png deleted file mode 100644 index 32f7f770d82..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster8.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster9.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster9.png deleted file mode 100644 index 2a0c445c178..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/creating-a-cluster9.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/network-creation01.png b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/network-creation01.png deleted file mode 100644 index 1a16ac98c1b..00000000000 Binary files a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/images/network-creation01.png and /dev/null differ diff --git a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/meta.yaml b/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/meta.yaml deleted file mode 100755 index 17faf7aa08e..00000000000 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/premium/meta.yaml +++ /dev/null @@ -1,2 +0,0 @@ -id: c182645c-a86b-4d18-bb98-40db61dfc797 -full_slug: public-cloud-kubernetes-premium \ No newline at end of file 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.de-de.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.de-de.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-asia.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-au.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ca.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 de66917b77f..f57ac7868b8 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-gb.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ie.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-ie.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-sg.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-us.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-es.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-es.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-us.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.es-us.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-ca.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-ca.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-fr.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.it-it.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.it-it.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pl-pl.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pl-pl.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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 0d88629e791..b223b4eec86 100644 --- a/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pt-pt.md +++ b/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume/guide.pt-pt.md @@ -1,7 +1,7 @@ --- title: Persistent Volumes on OVHcloud Managed Kubernetes Service excerpt: 'Learn how to create Persistent Volume Claims (PVCs) and Persistent Volumes (PVs), attach a Pod to a PVC, modify the PV reclaim policy, and delete the created objects.' -updated: 2025-09-29 +updated: 2025-12-08 --- This tutorial goes through the setup of a [Persistent Volume (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) on an OVHcloud Managed Kubernetes Service. @@ -173,7 +173,7 @@ The following storage classes are currently supported on OVHcloud Managed Kubern * `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 Standard 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 yet supported on the MKS Standard plan. Please refer to the limitations described in the `Multi availability zones deployments` section of our [Known limits](/pages/public_cloud/containers_orchestration/managed_kubernetes/mks_plans) guide). * `*-luks` storage classes add a layer of encryption on top of the storage class. It is only available in specific regions: see the [related GitHub issue](https://github.com/ovh/public-cloud-roadmap/issues/307) for more information. 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.