1
00:00:00,001 --> 00:00:00,934
[No Audio]

2
00:00:00,934 --> 00:00:05,001
Just like containers, Pods have their lifecycles as well.

3
00:00:05,967 --> 00:00:09,267
First of all, Pod is in the pending state.

4
00:00:09,434 --> 00:00:13,267
It means its configurations are approved by kube-controllermanager

5
00:00:13,267 --> 00:00:17,467
and apiserver, but it is yet to be sheduled on a node.

6
00:00:18,134 --> 00:00:20,934
Once it gets green signal from kubelet,

7
00:00:20,934 --> 00:00:23,167
and it is sheduled, it is in

8
00:00:23,167 --> 00:00:26,701
the Running state. It means at least one of the

9
00:00:26,701 --> 00:00:29,334
Pod's container is definitely running.

10
00:00:30,367 --> 00:00:33,901
Sometimes, the containers are programmed to exit after

11
00:00:33,901 --> 00:00:37,901
performing a certain task. In such case, the Pod

12
00:00:37,901 --> 00:00:41,134
goes to Succeeded state, where all of its

13
00:00:41,134 --> 00:00:45,234
containers have exited successfully. Or you can say gracefully.

14
00:00:46,534 --> 00:00:48,967
If one or more containers fail in

15
00:00:48,967 --> 00:00:52,134
between, or a container dies due to being out of

16
00:00:52,134 --> 00:00:56,301
memory, Pod goes to Failed state from Running state.

17
00:00:56,667 --> 00:00:59,301
It can be rescheduled after troubleshooting.

18
00:00:59,301 --> 00:01:02,967
In that case, it goes back to Pending and then

19
00:01:02,967 --> 00:01:07,567
Running state. Lastly, we have Unknown state, where

20
00:01:07,567 --> 00:01:09,934
the Pod is not running, but the reason

21
00:01:09,934 --> 00:01:12,067
for it is not determined yet.

22
00:01:12,201 --> 00:01:14,967
And this was the lifecycle of the Pod.