- Challenge
- Several clusters built by different teams, all behind on versions, with upgrades nobody wanted to own.
- Approach
- We consolidated onto managed clusters, moved every deployment to GitOps with Argo CD, and ran the first two upgrades alongside the client’s engineers.
- Stack
- EKS · Helm · Argo CD · Terraform
- Result
- Upgrades are now a scheduled, routine task the client’s platform team does without us.
Kubernetes: Kubernetes that stays up to date and makes sense to your team.
We set up and look after Kubernetes on EKS, AKS and GKE, or on your own servers, running full K8s or lightweight K3s, whichever fits. Upgrades happen on schedule, access is locked down, and your team knows how it all fits together.
Talk to an engineerWhat we do
Kubernetes consultancy
Cluster and architecture review, with a prioritised upgrade plan.
Kubernetes delivery
Production clusters on EKS, AKS or GKE, with GitOps from day one.
Kubernetes support
Version upgrades, patching and incident response for your clusters.
Kubernetes training
Bootcamps and pairing so your engineers run it without us.
What a cluster we hand over looks like
Tools we work with
Distributions
- EKS
- AKS
- GKE
- kubeadm
- k3s
- RKE2
- Talos
- OpenShift
Packaging & GitOps
- Helm
- Kustomize
- Argo CD
- Flux
- Argo Rollouts
Networking & ingress
- Cilium
- Calico
- ingress-nginx
- Gateway API
- cert-manager
- ExternalDNS
- Istio
- Linkerd
Security & policy
- Kyverno
- OPA Gatekeeper
- External Secrets
- Sealed Secrets
- Vault
- Trivy
- Falco
Scaling & storage
- Karpenter
- Cluster Autoscaler
- KEDA
- Velero
- Longhorn
- Rook-Ceph
- CSI drivers
Observability
- Prometheus
- Grafana
- Loki
- Tempo
- OpenTelemetry
- New Relic
Infrastructure as code
- Terraform
- Terragrunt
- OpenTofu
- Crossplane
How an engagement runs
- 1 A call. 30 minutes with an engineer to understand the problem.
- 2 A look. Read-only access or a walkthrough, so we scope from facts.
- 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
- 4 The work. In your accounts and repositories, alongside your team.
- 5 A handover. Documentation and a session with your team, so you’re not dependent on us.
Proof
A recent Kubernetes engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.
See our workQuestions
Do you work in our accounts or yours?
Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.
Can you work alongside our own team?
Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.
Do you work with K3s as well as full K8s?
Yes. We run full K8s and K3s, in the cloud or on your own servers. K3s suits places where a lighter footprint helps, like edge sites, small clusters and development environments. K8s suits larger production platforms.
How is this priced?
Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.