Learn some details about the Control Panel, plugins (CNI, CRI, CSI…), software versions we use, and resources we reserve on each Node.
Kubernetes versions
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 Policies in the dedicated section.
We will closely follow the Kubernetes releases and new versions will be regularly available.
OS, kernel, and Docker versions
The OS, kernel, and Docker daemon versions on your nodes will be regularly updated. The current versions are:
- OS: Ubuntu 22.04 LTS
- Kernel: 5.15-generic
- Docker: 23.0.1
CRI (Container Runtime Interface)
We use containerd as the default CRI:
-
1.27
: 1.7.18 -
1.28
: 1.7.18 -
1.29
: 1.7.18 -
1.30
: 1.7.18 -
1.31
: 1.7.18 -
1.32
: 1.7.25
CNI (Cluster Network Interface)
The CNI plugin installed is canal which embeds calico for policy and flannel for networking.
The versions installed depend on the Kubernetes version:
-
1.27
: calico v3.28.0, flannel v0.24.3 -
1.28
: calico v3.28.0, flannel v0.24.3 -
1.29
: calico v3.28.0, flannel v0.24.3 -
1.30
: calico v3.28.0, flannel v0.24.3 -
1.31
: calico v3.28.1, flannel v0.24.4 -
1.32
: calico v3.29.1, flannel v0.24.4
CCM (Cloud-Controller-Manager)
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.29 -
1.28
: OVH IOLB CCM based on OpenStackCCM 1.18, OVH Octavia CCM based on OpenStackCCM 1.29 -
1.29
: OVH IOLB CCM based on OpenStackCCM 1.18, OVH Octavia CCM based on OpenStackCCM 1.29 -
1.30
: OVH IOLB CCM based on OpenStackCCM 1.18, OVH Octavia CCM based on OpenStackCCM 1.29 -
1.31
: OVH IOLB CCM based on OpenStackCCM 1.18, OVH Octavia CCM based on OpenStackCCM 1.29 -
1.32
: OVH IOLB CCM based on OpenStackCCM 1.18, OVH Octavia CCM based on OpenStackCCM 1.29
CSI (Container Storage Interface)
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.0 -
1.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.2 -
1.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.0 -
1.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.0 -
1.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.0 -
1.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
Other components
The versions are:
-
1.27
: coredns v1.11.1, metrics-server v0.7.2 -
1.28
: coredns v1.11.1, metrics-server v0.7.2 -
1.29
: coredns v1.11.1, metrics-server v0.7.2 -
1.30
: coredns v1.11.1, metrics-server v0.7.2 -
1.31
: coredns v1.11.3, metrics-server v0.7.2 -
1.32
: coredns v1.12.0, metrics-server v0.7.2
Enabled policies
Authorization modes:
- Node: Authorize API requests made by Kubelets.
- RBAC: Role-Based Access Control is a method of regulating access to computer or network resources based on the roles of individual users within an organization.
Feature gates:
-
TTLAfterFinished
: Allow a TTL controller to clean up resources after they finish execution. (enabled by default forv1.23+
, parameter removed inv1.25
)
Kubelet
-
protect-kernel-defaults
: Protect tuned kernel parameters from overriding kubelet default kernel parameter values.
Reserved resources
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 1CPU+ 0,5% of all CPU cores -
RAM reservation is defined through this formula:
> 1024MB+ 5% of total memory -
Storage reservation is defined through this formula:
> log10 (total storage in GB) * 10 + 10% of total storage
Go further
For more information and tutorials, please see our other Managed Kubernetes or Platform as a Service guides. You can also explore the guides for other OVHcloud products and services.