Kubernetes consulting for GKE and bare metal

I design, build, migrate and upgrade Kubernetes clusters on Google Cloud and on your own hardware. The goal is always the same: a cluster that is secure by default, predictable to operate and boring in the best sense of the word.

Book an intro callAll services

When to call me

Sounds familiar?

These are the situations where teams usually bring me in.

  • You are planning a move to Kubernetes and want to get the foundation right the first time.
  • Your cluster was set up in a hurry, and now nobody wants to touch it.
  • Upgrades keep getting postponed because every one of them feels risky.
  • Costs grow faster than traffic, and nobody can say why.
  • You run on bare metal and need Kubernetes without a cloud provider behind it.

What I deliver

What you get

Cluster architecture

Node pools, networking, ingress, storage and multi-tenancy designed for your workloads — on GKE or bare metal.

Migrations

Moving services from VMs, Docker Compose or another cluster with a clear cut-over plan and a rollback path.

Upgrades & maintenance

Planned, rehearsed version upgrades instead of emergency ones.

Security hardening

RBAC, network policies, secrets management and workload isolation set up from the start.

Helm & GitOps

Every change to the cluster goes through Git and review — no manual kubectl in production.

Right-sizing

Requests, limits and autoscaling tuned to real usage, so you pay for what you actually use.

How it works

From first call to handover

  1. 01

    Assess

    Review the current setup or the requirements: workloads, traffic, data, team and constraints.

  2. 02

    Design

    Propose an architecture with the trade-offs spelled out — GKE vs. bare metal, one cluster vs. several.

  3. 03

    Build & migrate

    Infrastructure as code, service by service, with monitoring in place before traffic moves.

  4. 04

    Operate & hand over

    Runbooks, upgrade procedures and walkthroughs for your team.

Tools

  • Kubernetes
  • GKE
  • Helm
  • GitOps
  • Terraform
  • Ansible
  • Docker
  • Linux
  • Bare metal
  • Networking
  • Prometheus
  • Grafana

FAQ

Common questions

GKE or bare metal — which should we choose?
It depends on your workloads, team and budget. Managed GKE takes a lot of operational work off your plate; bare metal can be cheaper for steady, predictable workloads. I’ll walk you through the trade-offs for your specific case.
Can you take over a cluster someone else built?
Yes. I start with a review of the existing cluster, fix the riskiest parts first, and then bring it under version control and regular upgrades.
Do Kubernetes upgrades require downtime?
With the right setup — multiple replicas, pod disruption budgets and rolling node upgrades — most upgrades don’t. Where downtime is unavoidable, it is planned and communicated in advance.

Related services

Platform Engineering

An internal developer platform with golden paths: self-service environments, standard pipelines and sane defaults, so every team ships the same way.

Cloud & Infrastructure as Code

Google Cloud and bare-metal infrastructure described in Terraform and Ansible: reviewed, versioned and reproducible. No more snowflake servers.

Observability & Reliability

Metrics, logs and alerts with Prometheus and Grafana: alerting that wakes people up only when it matters, and a plan for when things break.

Contact

Let’s talk about your infrastructure

Tell me what you’re building and where it hurts — I’ll get back to you with next steps.