Kubernetes consulting, including the part where we tell you not to
Centricone designs, migrates to, and operates Kubernetes — and starts by checking whether your workload actually justifies the operational cost, because for many teams it does not.
What we build
What we build with Kubernetes
Clusters designed for how you will operate them
Node pools, networking, ingress, and upgrade strategy chosen against your team's capacity to run them, not against a reference architecture.
GitOps delivery
Cluster state in version control with Argo CD reconciling it, so what is running is always what was reviewed and merged.
Resource tuning that stops the bleeding
Requests, limits, and autoscaling set from observed usage — the single biggest source of both cluster instability and wasted spend.
When Kubernetes is the right call — and when it is not
We would rather talk you out of a stack than deliver the wrong one well.
Reach for it when
- Many services with genuinely different scaling profiles
- Teams with, or committed to hiring, platform engineering capability
- Workloads needing portability across clouds or into a customer's own environment
Pick something else when
- A handful of services — managed containers or serverless are cheaper and far simpler
- Teams without on-call platform capacity; a cluster is a system that needs owners
- Organizations adopting it for the résumé rather than for a workload requirement
What we normally run alongside it
No stack is one tool. These are the pieces that usually show up with Kubernetes on our projects.
- Docker
- Helm
- Argo CD
- Terraform
- Prometheus
- Istio
Kubernetes questions we get asked
Weighing it against something else? Tell us the constraints and we’ll give you a straight recommendation.