This is in direct conflict with the default setup of standalone Docker. In order for Kubernetes to work, every pod needs to have its own IP address like a VM I’m going to sum it up a bit differently. There’s a lot of words on the earlier networking page. If any of this is wrong, please send a pull request Basics
The next post will be specifically about my chosen pod network provider, Calico and how it interacts with your OS and containers.ĭisclaimer: I’m not an expert on networking by any stretch of the imagination. Most of the information here is in the earlier linked networking doc, but I’m going to put it in my own words.
First, I’m going to explain in sysadmin (ie I try to avoid network gear at all costs) terms how kubernetes approaches networking. I’m going to detail all this in two parts. I certainly didn’t, so for the past week or so, I’ve been learning how all this works. If things go wrong, are you going to have any idea what’s going on here? Do you feel comfortable running this in production? However, take a look at the full networking documentation page. You can initialize your network super easily, and if you’re playing around with minikube or some other small setup, this really takes the pain out of getting started.
You can install a pod network add-on with the following command: kubectl apply -f Let’s take a look at the kubeadm page, for example. The other issue is that too many of the “Getting Started” tutorials gloss over the parts that you actually need to know. However, because of its code complexity, and the vast number of features, plugins, addons and options, the documentation isn’t getting the job done. It’s a fantastic tool that is revolutionizing the way we do things at $work.