Cloud on Chris Wagner

How I Actually Make Trade-off Calls — Not Just What I Build

cw@wagner.org.za (Chrisando Wagner) — Mon, 03 Aug 2026 00:00:00 +0000

If you’ve already read the build logs — the k3s cluster, the storage classes, the failover drill — you know what I build. This post is about the part that doesn’t show up in a terraform apply output: how I actually decide something, in the moment a plan stops matching reality, and what I do about it afterward.

That’s a different question than “what technology did you pick,” and it’s the one I think actually separates senior from principal-level work. Anyone competent can execute a plan that goes to schedule. What I’m going to walk through is a plan that didn’t, twenty minutes into a homelab rebuild, and the small, unglamorous decision that followed it — because that decision is a better sample of how I’ll behave on your platform than any tool list is.

What I Build — A Technical Services Profile

cw@wagner.org.za (Chrisando Wagner) — Mon, 03 Aug 2026 00:00:00 +0000

If you’ve landed here from LinkedIn or a referral, this is the longer answer to “what do you actually do?”

The short version: I design and build infrastructure, and increasingly I’m the one deciding what infrastructure gets built. I have done so for 25 years — across datacentres, managed service environments, banking platforms, and my own homelab — using everything from Windows Server and VMware to OpenStack, Red Hat, and modern cloud-native stacks on Kubernetes. My current role is setting cloud and containerisation strategy for a regulated banking platform: the reference architectures other engineering teams build against, the guardrails that keep a POPIA and PCI-DSS environment audit-ready, and the FinOps governance that keeps cloud spend accountable at group level.

I Run Kubernetes for a Bank and at Home. Here's When You Shouldn't.

cw@wagner.org.za (Chrisando Wagner) — Mon, 27 Jul 2026 00:00:00 +0000

Every eighteen months or so, the same argument does a lap of the internet. Someone writes “we moved off Kubernetes and cut our infra bill by 60%.” A few months later, someone else writes “we moved back to Kubernetes and here’s why.” Both posts get the same engagement, both are right about their own environment, and both get quoted afterwards as if they’d settled something universal. Neither side did.

I’m writing this because I sit on both ends of that argument at the same time, every day, and I don’t think either tribe is being honest with the other.