title | excerpt | updated |
---|---|---|
Kubernetes Plugins (CNI, CRI, CSI...) & softwares versions and reserved resources |
2025-02-26 |
We list here some details on the Control Panel, the plugins (CNI, CRI, CSI...) & software versions we use and the resources we reserve on each Node.
Currently, we support the following Kubernetes releases:
1.27
1.28
1.29
1.30
1.31
1.32
If you run a Managed Kubernetes Service using an older version we strongly encourage you to use the version upgrade feature to receive official support for your cluster.
You will find more details about our End-of-Sale, End-of-Service and End-of-life-Policy in the dedicated section.
We will closely follow the Kubernetes releases, and new versions will be regularly available.
The OS, kernel and Docker demon version on your nodes will be regularly updated. Current versions are:
- OS: Ubuntu 22.04 LTS
- Kernel: 5.15-generic
- Docker: 23.0.1
We use containerd
as the default CRI
1.27
: 1.7.181.28
: 1.7.181.29
: 1.7.181.30
: 1.7.181.31
: 1.7.181.32
: 1.7.25
The CNI plugin installed is canal{.external} which embedded calico{.external} for policy and flannel{.external} for networking.
The versions installed depends on the Kubernetes version:
1.27
: calico v3.28.0, flannel v0.24.31.28
: calico v3.28.0, flannel v0.24.31.29
: calico v3.28.0, flannel v0.24.31.30
: calico v3.28.0, flannel v0.24.31.31
: calico v3.28.1, flannel v0.24.41.32
: calico v3.29.1, flannel v0.24.4
Our cloud-controller-manager (CCM) is based on the OpenStack cloud-controller-manager (OpenstackCCM) available in the Cloud provider openstack repository.
1.27
: OVH IOLB CCM based on OpenstackCCM 1.18, OVH Octavia CCM based on OpenstackCCM 1.291.28
: OVH IOLB CCM based on OpenstackCCM 1.18, OVH Octavia CCM based on OpenstackCCM 1.291.29
: OVH IOLB CCM based on OpenstackCCM 1.18, OVH Octavia CCM based on OpenstackCCM 1.291.30
: OVH IOLB CCM based on OpenstackCCM 1.18, OVH Octavia CCM based on OpenstackCCM 1.291.31
: OVH IOLB CCM based on OpenstackCCM 1.18, OVH Octavia CCM based on OpenstackCCM 1.291.32
: OVH IOLB CCM based on OpenstackCCM 1.18, OVH Octavia CCM based on OpenstackCCM 1.29
The CSI plugin installed is cinder.
The versions depend on the Kubernetes cluster version:
1.27
: csi-plugin v1.29.0, csi-attacher v4.3.0, csi-provisioner v3.5.0, csi-snapshotter v6.2.2, snapshot-controller: v6.2.2, csi-resizer v1.8.01.28
: csi-plugin v1.29.0, csi-attacher v4.4.2, csi-provisioner v3.6.2, csi-snapshotter v6.3.2, snapshot-controller: v6.3.2, csi-resizer v1.9.21.29
: csi-plugin v1.29.0, csi-attacher v4.5.0, csi-provisioner v3.6.3, csi-snapshotter v6.3.3 snapshot-controller: v6.3.3, csi-resizer v1.10.01.30
: csi-plugin v1.29.0, csi-attacher v4.5.0, csi-provisioner v3.6.3, csi-snapshotter v6.3.3 snapshot-controller: v6.3.3, csi-resizer v1.10.01.31
: csi-plugin v1.29.0, csi-attacher v4.5.0, csi-provisioner v3.6.3, csi-snapshotter v6.3.3 snapshot-controller: v6.3.3, csi-resizer v1.10.01.32
: csi-plugin v1.29.0, csi-attacher v4.5.0, csi-provisioner v3.6.3, csi-snapshotter v6.3.3 snapshot-controller: v6.3.3, csi-resizer v1.10.0
The versions are:
1.26
: coredns v1.11.1, metrics-server v0.6.41.27
: coredns v1.11.3, metrics-server v0.7.21.28
: coredns v1.11.3, metrics-server v0.7.21.29
: coredns v1.11.3, metrics-server v0.7.21.30
: coredns v1.11.3, metrics-server v0.7.21.31
: coredns v1.11.3, metrics-server v0.7.21.32
: coredns v1.12.0, metrics-server v0.7.2
- Network policies{.external}
- Resource quotas{.external}
- Limit range{.external}
Authorization modes:
- Node{.external}: Authorise API requests made by Kubelets.
- RBAC{.external}: Role-Based Access Control is a method of regulating access to computer or network resources based on the roles of individual users within an organisation.
Feature gates:
TTLAfterFinished
: Allow a TTL controller to clean up resources after they finish execution. (enabled by default forv1.23+
, parameter removed inv1.25
)
protect-kernel-defaults
: Protect tuned kernel parameters from overriding kubelet default kernel parameter values.
Each worker node has a certain amount of CPU, RAM and storage reserved for Kubernetes components.
These reserved quotas may evolve in the future; the page will be updated accordingly.
To guarantee the availability of a customer's node, the amount of reserved resources depends on the instance flavor.
-
CPU reservation is defined through this formula:
15 % of 1 CPU + 0,5% of all CPU cores
-
RAM reservation is defined through this formula:
1024 MB + 5% of total memory
-
Storage reservation is defined through this formula:
log10(total storage in GB) * 10 + 10% of total storage
This table sums up the reserved resources on b2 and b3 flavors:
Flavor | vCore | Reserved CPU (ms) | Total RAM | Reserved RAM (GB) | Total storage (GB) | Reserved storage (GB) |
---|---|---|---|---|---|---|
b2-7 | 2 | 160 | 7 | 1,98 | 50 | 22 |
b2-15 | 4 | 170 | 15 | 2,4 | 100 | 30 |
b2-30 | 8 | 190 | 30 | 3,16 | 200 | 43 |
b2-60 | 16 | 230 | 60 | 4,7 | 400 | 66 |
b2-120 | 32 | 310 | 120 | 7,77 | 400 | 66 |
b3-8 | 2 | 160 | 8 | 2 | 50 | 22 |
b3-16 | 4 | 170 | 16 | 2,44 | 100 | 30 |
b3-32 | 8 | 190 | 32 | 3,26 | 200 | 43 |
b3-64 | 16 | 230 | 64 | 4,9 | 400 | 66 |
b3-128 | 32 | 310 | 128 | 8,18 | 400 | 66 |
b3-256 | 64 | 470 | 256 | 14,73 | 400 | 66 |
-
If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link 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.