“Kubernetes Cluster” is a service for allocating cloud infrastructure for a Kubernetes cluster and performing its initial deployment with the specified parameters. Instead of creating virtual machines manually, configuring networking between nodes, attaching storage, and installing Kubernetes components by hand, the user receives a ready-to-use cluster deployed on dedicated cloud resources and prepared for hosting containerised applications.
This approach reduces the time required to put the environment into operation and lowers the likelihood of errors during the initial configuration stage. When the service is provided, the cluster parameters are defined: the composition and number of nodes, their specifications, the Kubernetes version, network parameters, and basic storage parameters. After that, the necessary resources are allocated in the cloud infrastructure, and the cluster control plane and worker nodes are deployed.
In our case, the Kubernetes cluster is deployed on top of cloud infrastructure based on OpenStack. OpenStack provides the virtual machines, networks, and storage volumes on which the cluster components run. Kubernetes, in turn, provides orchestration of containerised applications and manages their placement on these resources. In this way, the cloud infrastructure serves as the base layer, and Kubernetes serves as the management layer for the container environment.
Unlike fully managed Kubernetes services, the “Kubernetes Cluster” service includes only infrastructure allocation and the initial cluster deployment. After the environment is handed over to the user, further administration is carried out independently. This includes updating Kubernetes and its components, configuring cluster policies and networking, installing additional components, managing workloads, monitoring, backup, and incident handling. Cluster support at the level of its internal configuration and lifecycle is not included in the service.
To work with the cluster, the user uses standard Kubernetes tools: the API, the kubeconfig file, the kubectl utility, resource manifests, Helm, and their own automation tools. This makes it possible to integrate cluster management into existing CI/CD processes and apply the “infrastructure as code” approach already at the level of describing applications, services, policies, and configurations.
The documentation for the “Kubernetes Cluster” service provides information about deployment parameters, the procedure for granting access to the cluster, and the specifics of interaction with the underlying cloud infrastructure. If there are restrictions on network ports and IP addresses at the cloud environment level, they also apply to the cluster hosted in that environment.
You can deploy a Kubernetes cluster in your existing Servermall Cloud Services (SMCS) cloud infrastructure using Terraform. The step-by-step process is described in the “Deploying a Kubernetes cluster with Terraform” guide.
If the required cloud infrastructure has not yet been set up, refer to the “How to Order a Kubernetes Cluster” guide. It explains how to order a Kubernetes cluster through the control panel and automatically deploy it together with all the required cloud infrastructure.
Please note that SMCS’s cloud infrastructure includes security measures such as blocking certain network ports and IP addresses. These measures prevent unauthorized access, reduce the risk of attacks, and ensure stable service operation. A list of blocked ports and IP address ranges is available in the “Blocked Ports and IPs” section.
