1
00:00:00,001 --> 00:00:01,000
[No Audio]

2
00:00:01,000 --> 00:00:05,067
Pods, till now, I have been avoiding using this

3
00:00:05,067 --> 00:00:07,767
term while explaining the architecture as much as

4
00:00:07,767 --> 00:00:13,001
possible. But trust me, Kubernetes is all about Pods.

5
00:00:13,001 --> 00:00:17,834
So, what are Pods? If we keep this Docker

6
00:00:17,834 --> 00:00:20,634
setup architecture in mind, where containers are

7
00:00:20,634 --> 00:00:24,667
on top of Docker, this is where Kubernetes stand,

8
00:00:24,892 --> 00:00:27,501
right between Docker and Containers.

9
00:00:27,501 --> 00:00:31,234
But Kubernetes doesn't host containers as they are.

10
00:00:31,234 --> 00:00:35,134
It encapsulates them in an environment or object

11
00:00:35,134 --> 00:00:39,467
called Pod. A Pod can have one or more containers

12
00:00:39,467 --> 00:00:44,201
inside it. But mostly you will find one Pod per container.

13
00:00:44,401 --> 00:00:46,534
Pods fall under the category of

14
00:00:46,534 --> 00:00:50,301
workload objects. Here are a few things about

15
00:00:50,301 --> 00:00:52,501
Pods, which you should remember.

16
00:00:53,267 --> 00:00:57,101
They are the smallest unit of orchestration in Kubernetes and

17
00:00:57,101 --> 00:01:01,034
everything revolves around them. The only way to

18
00:01:01,034 --> 00:01:04,534
interact with containers in Kubernetes is through Pods.

19
00:01:04,534 --> 00:01:06,700
So they are quite absolute.

20
00:01:07,901 --> 00:01:13,001
As we mentioned earlier, each Pod runs at least one container.

21
00:01:13,001 --> 00:01:18,667
It can have more than one, but one is a must, and it is also a standard practice.

22
00:01:20,001 --> 00:01:22,501
Now, this is what makes Pod special.

23
00:01:22,634 --> 00:01:24,734
Kubernetes is designed with the

24
00:01:24,734 --> 00:01:27,667
fact in mind that containers die.

25
00:01:28,534 --> 00:01:32,967
Their failure is natural. And so the restart policy of containers

26
00:01:32,967 --> 00:01:38,167
hosted by Pods is set to always by default.

27
00:01:38,167 --> 00:01:41,567
Just like Swarm perform orchestration on containers,

28
00:01:41,567 --> 00:01:44,367
higher level objects of Kubernetes perform

29
00:01:44,367 --> 00:01:48,601
orchestration on Pods. Now, since we know a little

30
00:01:48,601 --> 00:01:51,501
bit about Pods, let's get to work with them.