logo

Kubernetes

Kubernetes that your team can run with confidence

Cluster design, upgrades, security hardening, GitOps and monitoring for Kubernetes on AWS, Azure, Google Cloud, Hetzner or your own servers. Your developers release faster, and upgrades become routine work.

Talk to a Kubernetes expert Ways to start

We reply within one business day.

Any cloud

EKS, AKS, GKE, Hetzner, on-prem

GitOps

every change through Git and Argo CD

Assessment first

a clear plan before anything is built

Commit → pipeline → GitOps → cluster, with monitoring on every step

Commit → pipeline → GitOps → cluster, with monitoring on every step

Works with

Kubernetes

Helm

Argo CD

Rancher / RKE2

Docker

Prometheus

Grafana

Terraform / OpenTofu

AWS

Google Cloud

Hetzner

In short

We design, build, upgrade and support Kubernetes clusters: managed services (EKS, AKS, GKE) or self-managed, including vanilla upstream Kubernetes with kubeadm on bare metal or VMs, k3s and RKE2/Rancher. Work covers networking (Cilium, Calico, Gateway API), service mesh with Istio or Linkerd, autoscaling with HPA, VPA, KEDA and Cluster Autoscaler or Karpenter, storage (Rook-Ceph, Longhorn), RBAC and policy hardening, GitOps with Argo CD, monitoring, backups and tested version upgrades. We can hand over to your team or run the platform for you.

Services

What we do with Kubernetes

Cluster design and build

Managed or self-hosted clusters with networking, ingress, storage and separate environments, built from Terraform.

Vanilla Kubernetes on bare metal

Upstream Kubernetes with kubeadm on your own servers or VMs: HA control plane, etcd backups, Cilium or Calico, MetalLB, and Rook-Ceph or Longhorn storage. No vendor distribution required.

Autoscaling: HPA, VPA, KEDA

Horizontal Pod Autoscaler on CPU, memory or custom metrics, Vertical Pod Autoscaler for right-sized requests, KEDA for queue- and event-driven scaling, and Cluster Autoscaler or Karpenter for nodes.

Service mesh: Istio or Linkerd

Mutual TLS between services, traffic splitting for canary releases, retries and timeouts, and service-level observability. We also tell you when a mesh is overkill.

Ingress and Gateway API

NGINX, Traefik or Envoy-based gateways, Gateway API routes, cert-manager for TLS and external-dns.

Upgrades

Tested Kubernetes version upgrades, API deprecation fixes and add-on updates, with a rollback plan.

Security hardening

RBAC, network policies, Pod Security Standards, Kyverno or OPA Gatekeeper policies, image scanning, External Secrets with Vault, and audit logging.

Backups and stateful apps

Velero backups, persistent volumes, and databases on Kubernetes done safely, or kept outside when that is wiser.

Cost and performance

Right-sized requests and limits, node pools and spot or cheaper nodes, so you stop paying for idle capacity.

Managed Kubernetes

We run the platform: upgrades, patching, monitoring and on-call, with response times in writing.

Examples

Typical Kubernetes projects

Compose / VMsHelm chartsArgo CDProduction cluster

From Docker Compose to Kubernetes

Applications packaged with Helm, deployed through GitOps, with staging and production that behave the same.

Old versionDeprecation fixesStaged upgradeCurrent version

Overdue upgrade

Clusters several versions behind brought up to date one step at a time, without downtime for users.

Cluster reviewRBAC + policiesImage scanningEvidence

Security review before an audit

Hardening and documentation for ISO 27001, SOC 2 or a customer security questionnaire.

EKS / AKSTerraformk3s on HetznerLower bill

Managed cluster to self-managed

The same workloads on simpler, cheaper infrastructure, with monitoring and backups from day one.

Queue / trafficKEDA + HPAKarpenterScale back down

Traffic spikes without over-provisioning

Workers scale on queue length, web pods on requests per second, and nodes appear only while they are needed.

Plain HTTPIstio mTLSPoliciesAudit-ready

Zero-trust between services

Every service-to-service call encrypted and authorised, plus canary releases and traffic metrics per service.

How to start

How to start with Kubernetes

Cluster assessment

Fixed priceagreed after a short call
  • Architecture, security and cost review

  • Autoscaling and upgrade path

  • Prioritised fix list

  • About 1 week

Book the assessment
MOST POPULAR

Platform build or upgrade

Fixed priceper phase, scoped in writing
  • Cluster(s) built from code

  • GitOps with Argo CD

  • Monitoring and backups

  • Handover and training

Plan the project

Managed Kubernetes

Monthly plansized to your needs
  • Upgrades and patching

  • Monitoring and alerting

  • Capacity reviews

  • Response times in writing

Ask about managed

Process

Getting started with Kubernetes

1

Assess

What runs where, what hurts, and what the cluster costs.

2

Build or fix

In phases, from code, with staging first.

3

Hand over or run

Training and runbooks, or we operate it for you.

Why Kubernetes

Why companies move to Kubernetes

Kubernetes is a standard way to run containers across any infrastructure. Done well, it makes releases routine and capacity elastic. Done badly, it is expensive complexity, which is why we start with an assessment.

Self-healing

Failed containers restart, unhealthy ones are replaced and traffic only reaches healthy instances, without someone being paged.

Scale with demand

Pods scale out on CPU, memory or business metrics (HPA, KEDA), right-size themselves (VPA) and nodes are added or removed automatically.

Zero-downtime releases

Rolling, blue-green and canary deployments with instant rollback; with a service mesh you can shift 1% of traffic at a time.

Same everywhere

The same manifests run on a laptop, AWS, Azure, Hetzner or your own servers, which keeps you portable and avoids lock-in.

Better use of servers

Many services packed onto fewer machines with resource limits, so you pay for capacity you actually use.

One way to operate

Logging, monitoring, security policies and secrets handled the same way for every service, instead of per server.

When you may not need it

An honest note before you book.

  • A handful of services with steady traffic: VMs or a PaaS can be simpler and cheaper.

  • No one to own the platform: unless we run it for you, someone has to keep it upgraded.

  • A single monolith that is not containerised yet: start with containers and CI/CD first.

FAQ

Kubernetes FAQ

Straight answers. Ask us anything else on a call.

Do we even need Kubernetes?

Not always. For a few services, VMs or a PaaS can be simpler and cheaper. We tell you which in the assessment, and design for where you will be in two years.

Vanilla Kubernetes or a distribution?

Upstream Kubernetes with kubeadm gives full control and no vendor dependency, at the cost of more operational work. k3s and RKE2 are lighter to run; OpenShift and Rancher add management layers. We pick by team size, compliance needs and who will operate it.

Do we need Istio?

Only if you need mutual TLS everywhere, fine-grained traffic control or service-level telemetry across many services. For a few services, Linkerd or plain ingress plus network policies is simpler. We tell you which in the assessment.

HPA or VPA?

HPA adds or removes pods when load changes; VPA adjusts how much CPU and memory each pod requests. They should not both act on CPU and memory for the same workload. A common setup is HPA (or KEDA) for scaling and VPA in recommendation mode to keep requests right-sized.

Managed (EKS, AKS, GKE) or self-hosted?

Managed control planes save effort on the big clouds. On Hetzner or your own hardware, k3s or RKE2 are reliable and much cheaper. We compare total cost including the time to run it.

Can you work with our existing cluster?

Yes. Most of our Kubernetes work starts with an existing cluster that needs upgrading, hardening or tidying up.

Related

Related services

CI/CD and GitOps

Next step

Talk to an engineer about Kubernetes

Send a few details, and pick up to 3 times if you would like a call. We reply within one business day.

You talk to the expert who would do the work

Written scope and price after the call

No obligation

info@opensource.consulting
+1 514 577 8599

OpenSource Consulting

Open source solutions integrator: we design, build, integrate and support Odoo, n8n, Zabbix, Grafana, Kubernetes and databases.

info@opensource.consulting

+1 514 577 8599

Canada · Netherlands · UAE

Services

© 2026 OpenSource Consulting. All rights reserved. · Privacy · Cookies · Terms

Our brands: elasticsearch.expert · zd-inc.net · opsfinitive.io

Talk to a Kubernetes expert