Introduction
Now, there is some interesting information that we see displayed here in the cube system namespace as well as in the kubectl get node output.
Here we see that we have one master node with a version that we chose to install, and you see that its status is not ready.
So we have one node, a master node in the cluster which runs some of the pods. How, however, it is in the not ready status.
In addition to that, we also see that in the cube system namespace we have two pods that are in a pending state. These are the core DNS pods. Now, there is actually the same reason behind those two being in a pending state and masternode being in a not ready status.
And the reason for both of these issues is that we need to install what’s called a pod network in Kubernetes.
So we’ve come to a very interesting topic which is what is a pod network?
And how does networking actually work in Kubernetes?
So we’re going to learn everything about networking in Kubernetes and once we understand that, we’re going to install a networking application or a networking layer in Kubernetes, that will fix both of these issues. I hope you’re excited about it. So let’s dive in.
The core concept in networking of Kubernetes is the networking of pods and containers.
Some of the questions we will answer is how are pods created? How does pod networking actually look like? How do pods communicate with each other on the same node? And how the talk to each other across different nodes in the cluster? First, let’s see how networking works within the pods and then we will see how networking works between the pods.