[No Audio]
Pods, till now, I have been avoiding using this
term while explaining the architecture as much as
possible. But trust me, Kubernetes is all about Pods.
So, what are Pods? If we keep this Docker
setup architecture in mind, where containers are
on top of Docker, this is where Kubernetes stand,
right between Docker and Containers.
But Kubernetes doesn't host containers as they are.
It encapsulates them in an environment or object
called Pod. A Pod can have one or more containers
inside it. But mostly you will find one Pod per container.
Pods fall under the category of
workload objects. Here are a few things about
Pods, which you should remember.
They are the smallest unit of orchestration in Kubernetes and
everything revolves around them. The only way to
interact with containers in Kubernetes is through Pods.
So they are quite absolute.
As we mentioned earlier, each Pod runs at least one container.
It can have more than one, but one is a must, and it is also a standard practice.
Now, this is what makes Pod special.
Kubernetes is designed with the
fact in mind that containers die.
Their failure is natural. And so the restart policy of containers
hosted by Pods is set to always by default.
Just like Swarm perform orchestration on containers,
higher level objects of Kubernetes perform
orchestration on Pods. Now, since we know a little
bit about Pods, let's get to work with them.