Managed Kubernetes Service [MKS] Standard Plan
Managed Kubernetes Service [MKS] Standard Plan
In addition to our existing plan on Managed Kubernetes Service (Standard) available in our historical regions, we are launching a new 'Standard' plan that will first be accessible in our new Paris 3AZ region.
✅ Failure proof your clusters
✅ Dedicated Control Plane ressources
✅ Large choice of worker node flavors
📆 Beta start : 30/04
📍 Paris Region (EU-WEST-PAR)
💬 Discord channel :Container & orchestration beta
New level of resilience for your production workloads
We’re excited to announce the Beta launch of our new Managed Kubernetes Service – Standard Plan: a powerful solution designed for critical workloads, high availability, and enterprise-grade production environments.
Built on a multi-AZ control plane deployed across three availability zones, this new plan ensures native fault tolerance against zonal failures. With a 99.99% SLA*, dedicated etcd (up to 8 GB), and support for clusters scaling up to 500 nodes, the Standard Plan delivers unmatched resilience and scalability for your cloud-native applications.
💡 Beta access is completely free** — giving you the opportunity to test our new plan under real-world conditions with zero cost.
Whether you're running mission-critical systems or scaling modern microservices architectures, MKS Standard gives you the performance and guarantees you need — while letting you shape the future of the product through your feedback.
* At General Availabilty stage
** Managed Service/Control Plane is free of charge, only pay your nodepool (instances, storage) and network (LB, Gateway, ...) resources.
All inclusive MKS Standard experience
In addition to the free control plane during the entire beta phase, claim your limited quantities voucher to deploy a whole 3AZ cluster at not cost
(including compute, storage and network).
Contact our customer support team to get it soon.
Compare our Kubernetes plans:
| Free | Standard | ||
| Control Plane | Managed | Managed & Cross-AZ resilient | |
| Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | |
| etcd | Shared, up to 400MB | Dedicated, up to 8GB | |
| Max cluster size | Up to 100 nodes | Up to 500 nodes | |
| Regional availability | Single-zone regions (3-AZ regions planed for 2025) | 3-AZ region for now |
Failure-proof your cloud native application
Deploy highly resilient cloud native application on our multi zonal region. Kubernetes control plane is deployed regionally and data plane is multi zonal.
You will have the full control on how to deploy your worker node in our new 3AZ region. Deploying your cloud-native applications in our new Paris 3-AZ region also means enjoying the full range of services available to muscle up your application :
- Well architectured appplication relying on resilient managed services (MKS + Loadbalancer + gateway + DBaaS + object storage ...),
- Advanced internal cluster networking with a new CNI (Cillium)
- Better API server performances and scaling capacity
- And much more to come !
FAQ
What is the difference between single and multi-zone clusters for Managed Kubernetes?
In a Standard cluster on a multi-AZ region , the control plane components are deployed in high availability and are automatically replicated across all three areas of the region. For a Free cluster, control plane components are deployed in high availability within a single zone. For node pools, you can manually define the zones where your nodes will be deployed, as long as they belong to the same region as the control plane.
What are the availability guarantees for the Managed Kubernetes Service control plane?
For the Free version of the Managed Kubernetes Service, the SLO is 99.5% monthly availability. For the Standard version you will have access after the beta to a 99.99% SLA.
Which resources are managed by OVHcloud?
In accordance with our responsibility matrix, OVHcloud manages the installation and keeps it in operational condition of the Kubernetes control plane (API Server, storage and other controllers). These components run on resources and in a project owned by OVHcloud. The customer is responsible for securing their worker nodes, containers and pods. He is also responsible for correctly sizing the infrastructure managed by Kubernetes, and backing up his data.
-
Alpha
-
Beta
-
General Availability