1. Articles
  2. Managed Kubernetes
  3. Technical Resources

Articles in this section

Kubernetes Plugins (CNI, CRI, CSI...), Software Versions, and Reserved Resources

Avatar
Michael M.
  • Updated
Follow

In this article, we list some details on the Control Panel, the plugins (CNI, CRI, CSI…), and software versions we use and the resources we reserve on each Node.

Kubernetes versions

Currently, we support the following Kubernetes releases:

  • 1.20 (deprecated)
  • 1.21 (deprecated)
  • 1.22 (deprecated)
  • 1.23
  • 1.24
  • 1.25

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 and Docker versions

The OS and Docker daemon version on your nodes will be regularly updated. The current versions are:

  • OS: Ubuntu 18.04 LTS
  • Docker: 19.03.15

CRI (Container Runtime Interface)

Since1.20, we use containerd as the default CRI:

  • 1.20: 1.5.11 (deprecated)
  • 1.21: 1.5.11 (deprecated)
  • 1.22: 1.5.11 (deprecated)
  • 1.23: 1.6.10
  • 1.24: 1.6.10
  • 1.25: 1.6.10

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.20: calico v3.10.3, flannel v0.11.0 (deprecated)
  • 1.21: calico v3.22.5, flannel v0.17.0 (deprecated)
  • 1.22: calico v3.22.5, flannel v0.17.0 (deprecated)
  • 1.23: calico v3.22.5, flannel v0.17.0
  • 1.24: calico v3.23.5, flannel v0.17.0
  • 1.25: calico v3.24.5, flannel v0.20.1

CSI (Container Storage Interface)

The CSI plugin installed is Cinder.

The versions depend on the Kubernetes cluster version:

  • 1.20: csi-plugin v1.21.0, csi-attacher v3.4.0, csi-provisioner v3.1.0, csi-snapshotter v5.0.1, snapshot-controller: v4.2.1, csi-resizer v1.4.0 (deprecated)
  • 1.21: csi-plugin v1.21.0, csi-attacher v3.4.0, csi-provisioner v3.1.0, csi-snapshotter v5.0.1, snapshot-controller: v4.2.1, csi-resizer v1.4.0 (deprecated)
  • 1.22: csi-plugin v1.21.0, csi-attacher v3.4.0, csi-provisioner v3.1.0, csi-snapshotter v5.0.1, snapshot-controller: v4.2.1, csi-resizer v1.4.0 (deprecated)
  • 1.23: csi-plugin v1.21.0, csi-attacher v3.4.0, csi-provisioner v3.1.0, csi-snapshotter v5.0.1, snapshot-controller: v4.2.1, csi-resizer v1.4.0
  • 1.24: csi-plugin v1.21.0, csi-attacher v3.5.0, csi-provisioner v3.2.1, csi-snapshotter v6.0.1, snapshot-controller: v6.0.1, csi-resizer v1.5.0
  • 1.25: csi-plugin v1.21.0, csi-attacher v3.5.0, csi-provisioner v3.2.1, csi-snapshotter v6.0.1, snapshot-controller: v6.0.1, csi-resizer v1.5.0

Other components

The versions are:

  • 1.20: coredns v1.10.0, metrics-server v0.6.2 deprecated)
  • 1.21: coredns v1.10.0, metrics-server v0.6.2 (deprecated)
  • 1.22: coredns v1.10.0, metrics-server v0.6.2 (deprecated)
  • 1.23: coredns v1.10.0, metrics-server v0.6.2
  • 1.24: coredns v1.10.0, metrics-server v0.6.2
  • 1.25: coredns v1.10.0, metrics-server v0.6.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 for v1.23+, parameter removed in v1.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

This table sums up the reserved resources on b2 flavors:

plugins1.png

Related articles