...

Kubernetes
cluster

Deploy a production-ready Kubernetes cluster on our infrastructure in just a few steps. Select your cluster profile, Kubernetes version, and node resources: we provision the virtual machines, configure the network, and bootstrap Kubernetes automatically, delivering a ready-to-use environment from day one.

Our team is available to support you while your architecture and cluster lifecycle remain in your hands.

How it works

Build a controlled and scalable Kubernetes environment on our infrastructure with virtual networks, cluster nodes tailored to your architecture.

Configure Your Cluster

Select your cluster configuration: Kubernetes version, node size (vCPU/RAM), disk type (hybrid or All-flash) and volume.

Review and Deploy

Complete your order using your preferred billing option.

Access and Operate

Receive a ready-to-use Kubernetes cluster with control plane access and start deploying workloads.

Tasks we handle

The Server Mall Cloud platform provides convenient and flexible management of Kubernetes clusters and offers:

  • Virtual machine deployment
  • Cluster and node‑group upgrades
  • Data storage and hardware security
  • Network configuration
  • Master availability
  • Service integration
  • Operating system and software installation
  • Backup

What opportunities open up for you

Scale your cluster by adding resources and nodes through Terraform or OpenStack CLI, in line with your architecture.

Cluster lifecycle operations remain under your control: upgrades and patching, node scaling after initial deployment, backups and restores, and post-deployment network or add-on changes.

  • СI/CD

    Build a CI/CD pipeline to accelerate your release cycle.

    Gitlab Gitlab
    Travis CI Travis CI
    Jenkins Jenkins
    CircleCI CircleCI
  • Service Mesh

    Control data flows in your application without touching the code.

    Istio Istio
    Consul Consul
  • Infrastructure as Code

    Easily manage cloud-native applications in Kubernetes

    Terraform Terraform
    Helm Helm
  • Serverless

    Store and run serverless functions in containers.

    OpenFaaS OpenFaaS
    OpenWhisk OpenWhisk
  • Monitoring and Analytics

    Track application performance through metrics, logging and tracing

    Prometheus Prometheus
    Fluentd Fluentd
    Opentracing Opentracing

Where to start with kubernetes

Create a standalone Kubernetes project

Get a fully isolated Kubernetes environment from the ground up. Simply select your cluster configuration: choose the version that best fits your workload, define vCPU and RAM for your nodes, and select between hybrid or all-flash volumes.

Get started

Deploy in an existing IaaS project

Build a Kubernetes cluster directly on your existing Servermall infrastructure. Design your virtual networks, define compute resources, and provision the environment that will host your control plane and worker nodes.

Which Kubernetes Profile Fits Your Workload?

Plan: 1 control plane + 1 worker

Starts from: 2 vCPU / 2 GiB RAM (per node)

Recommended for

  • Proof of concept, demos, and feature spikes.
  • CI experiments (lightweight pipelines, test deployments).
  • Personal or small team dev environments.
  • Learning Kubernetes and validating Helm charts or GitOps flows.

Typical workloads

  • Small web apps and simple APIs.
  • Lightweight background jobs.
  • Minimal observability stack and ingress testing.

Plan: 1 control plane + 2 workers

Starts from: 2 vCPU / 8 GiB RAM (per node)

Recommended for

  • Small production workloads with modest traffic.
  • Internal services and small SaaS backends.
  • Dev + staging environments closer to production.
  • Basic separation of workloads across worker nodes.

Typical workloads

  • Several microservices with ingress and monitoring.
  • Light-to-moderate logging and metrics stack.

Plan: 3 control plane + 3 workers (HA control plane)

Starts from: 4 vCPU / 8 GiB RAM (per node)

Recommended for

  • Production environments with control plane resilience.
  • Multi-service platforms and multiple namespaces.
  • Multi-team clusters with RBAC and policies.
  • Workloads requiring observability and platform add-ons.

Typical workloads

  • Microservices platforms and event-driven workloads.
  • Monitoring, logging, tracing stacks and GitOps tooling.

Plan: 3 control plane + 6 workers

Starts from: 4 vCPU / 8 GiB RAM (per node)

Recommended for

  • Production platforms with higher capacity needs.
  • Larger teams and heavier CI/CD workloads.
  • Clusters requiring more scheduling flexibility.

Typical workloads

  • Multi-tenant clusters.
  • Large observability and platform tooling stacks.
  • Higher traffic services and many microservices.

Other products that may interest you

Container Registry

Accelerate your application development process with the Container Registry cloud service. We offer fast access to containers, high upload speed, and flexibility when managing images.

Read more

Object Storage (S3)

Ensure continuous protection and instant access to rapidly growing data sets. The storage operates very economically, and it easily scales and integrates into your application scenarios.

Read more

FAQ

What is Managed Kubernetes and why is it needed?

Managed Kubernetes is a service that oversees the maintenance of your Kubernetes cluster, ensuring it remains healthy and efficient. Kubernetes itself is a container orchestration system designed to automate the deployment, scaling, and operation of containerized applications. By using Managed Kubernetes, customers can focus more on developing applications rather than managing the underlying cluster infrastructure.

What are the responsibilities divided between the client and the service provider?

Our responsibilities include:

  • Ensuring deployment, availability, scaling, recovery, and updates of the cluster.
  • Managing connectivity within the cluster and to the internet.
  • Providing user technical support.
  • Maintaining control panel availability.
  • Integrating with other services we offer.
  • Securing data storage and updating cluster software.

Clients are responsible for:

  • General management of the Kubernetes cluster.
  • Managing worker nodes and applications.
  • Initiating scaling and software upgrades.

Do clients need to monitor the health of the cluster?

No, our service automatically monitors and maintains the cluster's health, addressing:

  • Core and filesystem issues.
  • Communication problems, both internet and intra-cluster.
  • Kubernetes component issues. Restoration of cluster functionality is managed by our team.

Which version of the Kubernetes CLI should be used with the cluster?

We recommend using the latest version of Kubernetes CLI (kubectl) to ensure compatibility and access to the latest features.

How frequently are new Kubernetes versions released, and will resources be idle during upgrades?

Kubernetes typically releases new versions every three months, including minor updates in between. During upgrades, control plane nodes may be temporarily idle, and certain operations could be unavailable. However, application loads continue to be processed, and node group updates are handled seamlessly with minimal downtime.

Is it effective to host databases like MySQL or PostgreSQL on a Kubernetes cluster?

While it is technically feasible to host databases using StatefulSet controllers in Kubernetes, we recommend using our managed database services for MySQL or PostgreSQL for better efficiency and ease of use.

How are updates to Kubernetes versions managed?

Customers can select from supported Kubernetes versions and initiate upgrades when convenient. This flexibility allows for thorough testing of application compatibility with new Kubernetes versions before full implementation.