Using client-go

I help CTOs and platform teams design, build, and hand over Kubernetes-based platforms that can be understood, operated, and evolved by the teams that own them.

My work sits at the intersection of Go, Kubernetes API machinery, control-plane design, platform engineering, infrastructure automation, and distributed systems.

I am most useful when a team is not only deploying workloads to Kubernetes, but building a product, platform, or control plane on top of it. That is where API shape, controller behaviour, ownership boundaries, and automation design become long-term architecture.

I work through focused architecture discovery, hands-on implementation, design review, documentation, and structured handover.

The objective is to leave behind clearer technical decisions, production-oriented software, explicit ownership boundaries, useful documentation, and a team able to continue without me.

Typical problems I help with:

• Kubernetes APIs, CRDs, and resource lifecycle design
• controllers, reconciliation behaviour, and failure handling
• custom API servers and control-plane components
• Go infrastructure software and automation tooling
• platform architecture that must remain connected to code
• review and simplification of existing platform codebases
• documentation and handover for internal teams.

I also write practical technical material on Kubernetes controllers, client-go, Go services on Kubernetes, SRE workflows, AI platform engineering, and operational context for humans, tools, and AI agents.

Available for selected consulting, fractional, contract, and staff-level engagements.

The best first conversation starts from the engineering problem: what you are building, why it is difficult now, what decisions are hard to reverse, and what the internal team needs to own after the work is done.