Available datacenters, worker nodes and persistent storage flavors

Available datacenters, worker nodes and persistent storage flavors

Available regions / datacenters

A Managed Kubernetes Service deploys a Kubernetes Master within a given OVHcloud datacenter. All its worker nodes and persistent volumes are then deployed by the cloud controller in the same region.

Currently the service is available in all OVHcloud Public Cloud geographies. Note that projects with older regions (such as SBG1 or GRA1 for example) will be invited to transparently activate the latest regions in this zone to benefit from Managed Kubernetes Service.

OVHcloud US customers can also deploy the service in both our East and West American datacenters.

Regional availability by MKS plan

OVHcloud Managed Kubernetes Service availability varies depending on your chosen plan (Free or Standard). The table below shows which regions support each plan and their deployment architecture:

Available worker nodes flavors

When adding a worker node, Managed Kubernetes Service will deploy a managed Public Cloud instance in the same region/datacenter. The worker nodes types correspond to the standard OVHcloud Public Cloud catalog offered in this region and are billed at standard price.

We currently support several types of instances with guaranteed and constant resources.

Here is a comparative table of flavours available by region:

Each family offers contains different flavors, consisting of a five amount of vCores, RAM and local storage.
For more information, please refer to the following page: OVHcloud Public Cloud instances

Note that we are both compatible with the standard and flex variations (Flex offering the same disk size for each flavor). Note however that Managed Kubernetes Service does not currently offer worker nodes resize.

Using our API, you shall use the flavor name such as b2-7 as parameter of the POST /cloud/project/{serviceName}/kube/{kubeId}/node endpoint.
This is detailed in the quickstart with OVH API guide.

GPU (T1-*) instances are now supported! If you want to know how to deploy GPU applications on Kubernetes Managed Service, please read our tutorial.

Available persistent storage classes

When adding a persistent volume though Kubernetes API (or kubectl), it will actually be deployed using Public Cloud additional disks (Cinder Volumes). We support the following storage classes:

• 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 you 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).

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.

High Speed performance is theoretically best for volumes up to 100GB. Above 100GB per volume, you will get enhanced performance with a High Speed Gen2 volume. This is detailed in the Persistent Volumes guide.

LUKS encrypted storage classes

OVHcloud Managed Kubernetes also supports LUKS encrypted block storage volumes using OVHcloud Managed Keys (OMK). The following encrypted storage classes are available in supported regions:

• csi-cinder-high-speed-gen2-luks - Encrypted version of High Speed Gen2 (progressive performance, SSD NVMe)
• csi-cinder-high-speed-luks - Encrypted version of High Speed (fixed 3,000 IOPS)
• csi-cinder-classic-luks - Encrypted version of Classic (spinning disks, 200 IOPS)

For more information:

• Choosing the right Block Storage class
• Create encrypted Persistent Volumes on OVHcloud Managed Kubernetes clusters with LUKS (Complete tutorial)

We will support future classes as soon they are made available in OVHcloud Public Cloud.