|
| 1 | +--- |
| 2 | +title: MKS Premium Plan Beta |
| 3 | +excerpt: 'Features and limitations of the MKS Premium Plan in Beta version' |
| 4 | +updated: 2025-04-29 |
| 5 | +--- |
| 6 | + |
| 7 | +<style> |
| 8 | + pre { |
| 9 | + font-size: 14px; |
| 10 | + } |
| 11 | + pre.console { |
| 12 | + background-color: #300A24; |
| 13 | + color: #ccc; |
| 14 | + font-family: monospace; |
| 15 | + padding: 5px; |
| 16 | + margin-bottom: 5px; |
| 17 | + } |
| 18 | + pre.console code { |
| 19 | + b font-family: monospace !important; |
| 20 | + font-size: 0.75em; |
| 21 | + color: #ccc; |
| 22 | + } |
| 23 | + .small { |
| 24 | + font-size: 0.75em; |
| 25 | + } |
| 26 | +</style> |
| 27 | + |
| 28 | +> [!primary] |
| 29 | +> This document describes the features for the Managed Kubernetes Service Premium Plan in beta version. For additional details on the Managed Kubernetes Service Standard plan, refer to the [following documentation](/pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits). |
| 30 | +
|
| 31 | +## Standard vs Premium comparison |
| 32 | + |
| 33 | +| Plan | Standard | Premium | |
| 34 | +| --------------------- | -------------------------------------------------- | ----------------------------------------- | |
| 35 | +| ControlPlane | Managed | Managed & Cross-AZ resilient | |
| 36 | +| Availability | 99,5% SLO | 99,99 SLA (at General Availability stage) | |
| 37 | +| etcd | Shared, up to 400MB | Dedicated, up to 8GB | |
| 38 | +| Max cluster size | Up to 100 nodes | Up to 500 nodes | |
| 39 | +| Regional availability | Single-zone regions (3-AZ regions planed for 2025) | 3-AZ region for now | |
| 40 | + |
| 41 | +## Upcoming features |
| 42 | + |
| 43 | +In order to help you make the best use of our new Managed Kubernetes Service (MKS) Premium Plan, we have listed some limitations and guidelines related to specific features. |
| 44 | + |
| 45 | +This list is subject to change as new features will be introduced during the Beta. |
| 46 | + |
| 47 | +### Cluster update |
| 48 | + |
| 49 | +Updating an existing cluster is not supported at the moment. |
| 50 | + |
| 51 | +### Cluster rename |
| 52 | + |
| 53 | +Renaming an existing cluster is not supported at the moment. |
| 54 | + |
| 55 | +### Logs LDP / LDP forward |
| 56 | + |
| 57 | +Audit logs forwarding to the [Logs Data Platform](/pages/public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) is not supported at the moment. |
| 58 | + |
| 59 | +### ETCD Quota |
| 60 | + |
| 61 | +Real-time monitoring the etcd storage usage is not supported at the moment, currently the storage is limited to 8GB per cluster. |
| 62 | + |
| 63 | +### API server admission plugins configuration |
| 64 | + |
| 65 | +The configuration of the [API server admission plugins](/pages/public_cloud/containers_orchestration/managed_kubernetes/apiserver-flags-configuration) is not available at the moment. |
| 66 | + |
| 67 | +### Anti-affinity |
| 68 | + |
| 69 | +This feature allows worker nodes to will be deployed on different hypervisors (physical servers), guaranteeing better fault tolerance. It is not currently available on the regions offering the MKS Premium Plan. |
| 70 | + |
| 71 | +We recommend using multiple Availability Zones (AZs) instead |
| 72 | + |
| 73 | +### Ports |
| 74 | + |
| 75 | +The openstack security group for worker nodes is the `default` one. It allows all egress and ingress traffic by default on your private network. |
| 76 | + |
| 77 | +```bash |
| 78 | +openstack security group rule list default |
| 79 | ++--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ |
| 80 | +| ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | |
| 81 | ++--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ |
| 82 | +| 0b31c652-b463-4be2-b7e9-9ebb25d619f8 | None | IPv4 | 0.0.0.0/0 | | egress | None | None | |
| 83 | +| 25628717-0339-4caa-bd23-b07376383dba | None | IPv6 | ::/0 | | ingress | None | None | |
| 84 | +| 4b0b0ed2-ed16-4834-a5be-828906ce4f06 | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | |
| 85 | +| 9ac372e3-6a9f-4015-83df-998eec33b790 | None | IPv6 | ::/0 | | egress | None | None | |
| 86 | ++--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ |
| 87 | +``` |
| 88 | + |
| 89 | +It is recommended to leave these security rules as-is or the nodes could be disconnected from the cluster. |
| 90 | + |
| 91 | +### Reserved IP ranges |
| 92 | + |
| 93 | +The following ranges are used by the cluster, and should not be used on the private network attached to the cluster. |
| 94 | + |
| 95 | +```text |
| 96 | +10.240.0.0/13 # Subnet used by pods |
| 97 | +10.3.0.0/16 # Subnet used by services |
| 98 | +``` |
| 99 | + |
| 100 | +These ranges will be configurable in a future version. |
| 101 | + |
| 102 | +## Go further |
| 103 | + |
| 104 | +- 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. |
| 105 | + |
| 106 | +- Join our [community of users on Discord](https://discord.com/channels/850031577277792286/1366761790150541402)! |
0 commit comments