Skip to main content
Managed Kubernetes Product Description

Managed Kubernetes Product Description

Servercore's Managed Kubernetes simplifies the process of deploying, scaling and maintaining your Kubernetes container infrastructure. Servercore is responsible for version updates, security and uptime of Control Plane Kubernetes.

The product supports user types and roles, projects and project limits and quotas.

Versions⁠

Managed Kubernetes clusters support versions 1.29.x, 1.30.x, 1.31.x

How Managed Kubernetes works⁠

Managed Kubernetes is powered by of Servercore's cloud platform and uses it resources for cluster nodes: cloud servers, load balancers, networks, disks.

As a container execution environment (CRI) is used containerd. As. CNI Managed Kubernetes clusters use Calico.

You can work with a Managed Kubernetes cluster in the control panels and through the Managed Kubernetes API.

Cluster composition⁠

Managed Kubernetes clusters consist of:

  • of master nodes — contain the management components of the cluster, Control Plane. The number of master nodes depends on cluster type. Master nodes are not displayed in the control panel, for them Servercore responds;

  • groups of work nodes — contain containers of user applications. The work nodes are displayed in the control panel, for them user replies.

A group of working nodes must be in the same accessibility zone with master nodes. Read more in the section Working with groups of nodes.

Types of cluster⁠

Servercore provides two types of Managed Kubernetes clusters: fault-tolerant and basic.

You can only select a cluster type when cluster creation. Once a cluster is created, the cluster type cannot be changed.

Fault-tolerantBasic
Number of master notes31
Master Node Allocation
  • in different pool segments — if there are multiple segments in the pool;
  • or in the same pool segment on different hosts — if there is only one segment in the pool
In one. pool segment
Fault toleranceIf one of the three master nodes is unavailable, Control Plane will continue to runIf the master node is unavailable, Control Plane will not work
SLA✓ (99,98%)✗
FunctionalityAll functionalities are availableAuto-update of patch versions is not available
What tasks are suitable forFor the working environment (production)
  • for the developer's environment (development);
  • test environment (testing and staging);
  • pet projects

Limits⁠

Maximum number of fault-tolerant Kubernetes clusters in one pool for one project10
Maximum number of Kubernetes base clusters in one pool for one project10
Maximum number of node groups in one pool for one project100
Maximum number of nodes in one node group15
Maximum number of vCPU nodes32*
Maximum number of RAM nodes256*GB
Maximum size of the node boot disk1.2 TB.
Maximum number of pods on one node100
Maximum number permanent volumes (PV) on the same node256
Minimum size of one constant volume (PV)1 GB

*You can create nodes with more vCPUs and RAM — use the fixed cloud server configurations.

Cluster limitations on dedicated servers⁠

Managed Kubernetes clusters on dedicated servers are in beta testing.

Not supported during beta testing:

  • use of custom configurations of dedicated servers;
  • adding existing dedicated servers to the cluster;
  • adding multiple groups of nodes when creating a cluster;
  • increasing the number of nodes in the group;
  • updating minor versions of Kubernetes;
  • automation: auto-update of patch versions, auto-scaling and auto-recovery;
  • adding, modifying, and deleting labels and tints after the cluster is created;
  • connection constant volume (PV) based on the cloud platform's network disks;
  • use of user data;
  • Creating Managed Kubernetes clusters with GPUs;
  • Terraform usage.

Areas of responsibility⁠

Servercore provides⁠

  • creation and accessibility of master notes;
  • creation of working nodes;
  • updating versions of the Managed Kubernetes cluster;
  • masternode monitoring;
  • possibility of autoscaling of nodes;
  • Node auto-recovery capability;
  • integration with Servercore services;
  • technical support.

Servercore is not responsible for⁠

  • for managing the Managed Kubernetes cluster;
  • node management;
  • application creation;
  • initiating scaling and upgrades.