
Kubernetes setup and support: a cluster sized for your load
We build Kubernetes clusters and keep them running: EKS on AWS, or self-managed Kubernetes on Hetzner and other providers. Your services get Helm charts, autoscaling and rollouts without downtime. The cluster is described in code, so it can be rebuilt and upgraded.
When you need this
- 1
Services run in Docker Compose on one server and it no longer copes
- 2
A cluster exists, but nobody dares to upgrade it
- 3
Pods restart or get evicted and the cause is unclear
- 4
Load is uneven and you pay for peak capacity all the time
- 5
Deploys to the cluster are done with kubectl by hand
What's included
Cluster choice and setup
We pick the option for the task: EKS on AWS with managed node groups, or self-managed Kubernetes on EC2, Hetzner or your own servers. The VPC, nodes and storage are created with Terraform.
Helm charts for your services
Each service gets a chart with resource requests and limits, health probes and per-environment values. Probes and rolling updates let a new version replace the old one without downtime.
Ingress, TLS and network policies
An ingress controller, certificates that renew automatically, and network policies that limit which services can talk to each other.
Autoscaling
HPA scales services by CPU, memory or custom metrics. KEDA scales workers by queue depth, down to zero when the queue is empty. Node pools follow the pods.
Upgrades
Kubernetes versions and cluster add-ons are upgraded on a schedule: checked on staging first, then applied to production node by node.
Support and incidents
Monitoring of nodes and workloads, alerts, and analysis of failures: evictions, failed rollouts, exhausted resources. Provided as a monthly service.
The whole system on one screen
Service health, traffic, deploys and alerts — the dashboards we set up for every project.
Service overview
- Services
- 12
- Healthy
- 12 / 12
- Deploys today
- 7
- Open alerts
- 0
Requests per second
All services, 5 min average
p95 latency, ms
Alarm threshold 250 ms
Service health
| Service | Status | Pods | CPU |
|---|---|---|---|
| api-gateway | Healthy | 6 / 6 | 41% |
| billing | Healthy | 3 / 3 | 28% |
| worker-pool | Healthy | 9 / 9 | 63% |
| postgres-main | Healthy | 2 / 2 | 35% |
Recent deploys
- api-gatewayv2.14.112 min ago
- worker-poolv1.9.01 h ago
- billingv3.2.43 h ago
Illustration with sample data. Every project gets dashboards built around its own services.
How the work goes
- 1
Call and access
You describe the services and the load. If a cluster already exists, we get read access and look at its real state.
- 2
Design and price
EKS or self-managed, node sizes, how environments are split, what autoscales. You get the list of work and a price before we start.
- 3
Build and move services
The cluster is created from code. Services move over one at a time, each checked on staging before production.
- 4
Hand over or support
Your team gets the repository, documentation and access. Or we stay and operate the cluster for a monthly fee.
Questions
- Kubernetes
- AWS EKS
- Helm
- KEDA
- Traefik
- cert-manager
- Argo CD
- Terraform
- AWS
- Hetzner
Describe the task — get a plan and a price
Write what you have and what you need. We answer within one business day with questions or a concrete proposal.