Kubernetes & GitOps Platform Consultant

What you get

• Cluster architecture and tenancy model — single-tenant, multi-tenant or hybrid. We pick the right isolation boundary for your workloads before a line of YAML is written.
• ArgoCD with app-of-apps and ApplicationSets — one control plane that manages 1,000+ applications the same way it manages ten. Every change is reviewable in a pull request and rolled back with one revert.
• Secrets management that survives an audit — External Secrets Operator, workload identity and OIDC federation. No long-lived credentials, no shared service principals, no .env files in repos.
• CI/CD pipelines and deploy automation — GitHub Actions or GitLab CI, reusable workflows, promote-via-PR release flow.
• SLI/SLO and error budget definition — the reliability contract between platform and product teams, written so both sides know what 'working' means.
• Fault injection before release — pod kill, node loss, network partition. Find what breaks before your users do.
• Runbooks, ADRs and team handoff — the platform ships with documentation your team can operate without me.

Proven at scale

I built and operated a multi-tenant Kubernetes PaaS running 1,000+ applications behind a single ArgoCD control plane across 10 clusters — serving 2M+ daily requests with 99.9% uptime. Read the case study for the architecture decisions, the multi-tenancy model and the lessons learned.

Read the GitOps platform case study →

How it works

A fixed-scope project — typically 2–3 weeks per cluster. We agree on the deliverable before I start, and you get a production-ready platform with documentation, not a proof-of-concept that someone has to finish later.

Multi-cluster or multi-environment builds are scoped separately: same architecture, more of it.