2026-08-01
From Podman to K8S
My experience migrating to k8s
I started on docker like most people, and simply moved to rootless podman. It was fairly easy considering I'd been working with podman at work for years. I started off with podman-compose, but after having some RedHat engineers come to my place of work and show off quadlets--I immediately switched to them.
I found the whole interactions with systemd very pleasant, but when that VM would give me problems (for whatever reason) it drove me further away from single node deployments.
I felt/feel as if I would have better overall job prospects utilizing and learning OpenShift over vanilla kubernetes. I spun up a single-node openshift (sno), which was very resource intensive. I had capable hardware for some 4/16s perhaps but not the resources required for multiple OpenShift nodes. So I experimented with it for a bit, then moved on.
I already had ansible playbooks to spin up a 3 node cluster via debian, which I swiftly moved away towards RHEL servers. I then began migrating everything from podman to straight kubernetes. The first roadblock for my GO based applicaitons was env variables, which I began placing into a refreshly spun up vault server. This currently lives on a static node, unsure how I feel about that.
I then migrated everything one at a time including the data, then I utilized Calico's gateway api instead of the near-deprecated nginx ingress server.
Its been a smooth transition so far, I really enjoy argoCD and how it controls everything, minus the calico, taint, vault, and root-app manual applys.