kubernetes & orchestration
- rke1 / rke2
- rancher
- helm
- argocd
Production Kubernetes across ten-plus physical venues, managed through a central Rancher control plane in AWS.
Nearly twenty years across software and infrastructure. Currently running ten-plus RKE2 clusters across physical venues for Drive Shack / Puttery, and cleaning up etcd fires when they happen. My mental model of "production" includes the guests, not just the pods.
Platforms are products. On-call humans are users too.
Twenty years across infrastructure, platforms, and the interfaces on top of them. All of them shape how I think about production.
Production Kubernetes across ten-plus physical venues, managed through a central Rancher control plane in AWS.
Venue provisioning built as a repeatable pipeline.
2026-02 — venue provisioning pattern (infra → config → services)
Monitoring built for action, not dashboard cosplay.
2026-01 — full observability stack on helm's deep
AWS-primary platform work with enough multi-cloud literacy to know when not to commit.
2024 — ~64% aws cost reduction (rightsizing + infra cleanup)
Release paths should make the safe thing easy and the dangerous thing obvious.
2025-12 — internal helm repo + enforced release path
Secrets and access run like the rest of production: managed, audited, in code.
2025 — least-privilege rbac rollout across venue estate
Long software background now aimed at platform tooling and automation.
2026-03 — rancher mcp server (fastmcp, httpx, pydantic v2)
Decade of frontend work before the DevOps pivot, still active for internal tools and the occasional side project.
2020 — topgolf gameplay ui (internationalized, multi-region)
Hardware and home automation as the physical counterpart to the platform work.
2026 — nfc fossil dig station (jurassic park party build)
Twenty years across nine roles. The first three are expanded by default. The rest open on click.
$ git log --all --oneline --since="2007-01-01"
Outside work I still build infrastructure, just smaller and weirder. Home automation, 3D printing, woodworking, electronics, homelab systems, and the occasional wildly overengineered party prop.
Led communications, member engagement, event coordination, and public messaging for a volunteer sports club. Less glamorous than production infrastructure, but the same core skill shows up fast: make the system understandable, keep people informed, and reduce chaos before it turns into work for everyone else.
woodworking · 3d printing · esp32 / arduino · home automation · curling · scuba · homelab infrastructure · built environments.
You didn't ask. This is Linus, orange American shorthair, b. 2014, official CTO. He's been the constant through twelve years of career changes, so he gets to be on every important thing I make. Why the lambda? Because Half-Life 2 is one of the greatest games of all time. And it looks kickass.
Addison, TX · open to senior platform role · remote or dallas · selective contract work
start where you are.