Ergomake | Environments-as-a-Service
When I first encountered Kubernetes, its networking model seemed sufficiently advanced to look like magic. The problem is: I hate magic, and I hope you do too.
In this blog post, I hope to ruin your esoteric expectations about Kubernetes Networking so that it appears more manageable than Egyptian scrolls. For that, I'll show you processes running on nodes, containers, and plain text files.
This brief guide to Kubernetes networking contains what I wish I had known when I started writing Ergomake, which creates remote ephemeral environments so that folks can develop, preview, and test changes without talking to an SRE or running a thousand containers.
We'll start this post by explaining what an Ergomake environment is and what happens within our Kubernetes cluster when you run ergomake up.
Then, I'll go through each of those steps manually and explain everything that Kubernetes itself does when you create pods and services.
