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.

Documentation

How it works

Get started

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

  1. Configure Your Cluster

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

  2. Review and Deploy

    Complete your order using your preferred billing option.

  3. Access and Operate

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

What We Manage

We automate Kubernetes cluster provisioning on our infrastructure, including initial OS and Kubernetes setup, so your team can start deploying workloads immediately.

Our engineers are available when needed, while you retain full operational control of the cluster.

Network setup

Virtual machines deployment

OS and software installation

Integration with services

Storage and hardware security

Wizard Availability

Processes

What you control

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.

CI/CD Build a CI/CD pipeline to speed up the release cycle
Icon to Gitlab
Gitlab
Icon to Travis CI
Travis CI
Icon to Circle CI
Circle CI
Service Mesh Control the flow of data in the application without changing the code
Icon to Istio
Istio
Icon to Consul
Consul
Infrastructure as code Easily Manage Cloud-Native Applications in Kubernetes
Icon to Terraform
Terraform
Icon to Helm
Helm
Serverless Store and process Serverless features in containers
Icon to OpenFaaS
OpenFaaS
Icon to OpenWhisk
OpenWhisk
Monitoring and analysis Monitor application performance with metrics, logging and tracing
Icon to Prometheus
Prometheus
Icon to Fluentd
Fluentd
Icon to 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 Peerobyte 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

  1. Proof of concept, demos, and feature spikes.
  2. CI experiments (lightweight pipelines, test deployments).
  3. Personal or small team dev environments (single-namespace or light multi-namespace).
  4. Learning Kubernetes, validating Helm charts, operators, or basic GitOps flows.

Typical workloads

  1. Small web apps, simple APIs, lightweight background jobs.
  2. Minimal observability stack (or none), basic ingress/controller testing.

Plan: 1 control plane + 2 workers

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

Recommended for

  1. Small production workloads with modest traffic
  2. Internal services (dashboards, automation tools, small SaaS backends)
  3. Dev + staging where you want closer-to-prod behaviour than “dev”
  4. Teams that need basic separation of workloads across worker nodes

Typical workloads

  1. A few microservices + ingress + metrics/logging (light-to-moderate)
  2. Small databases only if you know what you’re doing (generally better externalise state)

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

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

Recommended for

  1. Production environments where control plane resilience matters
  2. Multi-service platforms with multiple environments/namespaces
  3. Multi-team usage with shared cluster governance (RBAC, quotas, policies)
  4. Workloads that need room for observability, ingress, and platform add-ons

Typical workloads

  1. Microservices platforms, event-driven workloads, internal developer platforms
  2. Proper monitoring/logging/tracing stack, GitOps tooling, policy controllers

Plan: 3 control plane + 6 workers (HA control plane + more capacity)

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

Recommended for

  1. Production platforms with higher capacity needs and more parallel workloads
  2. Larger teams, heavier CI/CD workloads, more add-ons and operational tooling
  3. Services that benefit from spreading workloads across more worker nodes (scheduling flexibility, blast-radius reduction)

Typical workloads

  1. Multi-tenant clusters (several teams/products)
  2. More demanding observability and platform tooling
  3. Higher traffic services or many small services running concurrently

Resources & Documentation

Kubernetes Documentation

Step-by-step guides, configuration references, and operational instructions for deploying and managing Kubernetes on our OpenStack infrastructure.

Study

Insights & Articles

Engineering expertise and business perspectives on cloud infrastructure and Kubernetes for technical teams and decision-makers shaping their cloud strategy.

Read

FAQ

Can't find an answer to your question? Ask us and we'll tall you!

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.