In Part 3 of the “Migrating a Django app to Kubernetes” I’ve written a Helm chart to run a Django application and a few corollary services on Kubernetes, but aside from port-forwarding, it’s still stuck “inside” the box. Time to let it out. Kubernetes keeps applications inside of itself by default, there are a few…

All code (minus passwords) will be published in the associated Github Repo As mentioned in part 1, my application has not one, but three backends! Neither of these applications is “stateless”, so we can’t treat them like cattle and scale them up or down as needed Stateful Sets Kubernetes introduces the idea of Stateful Set…