1
00:00:00,001 --> 00:00:05,234
[Intro Music]

2
00:00:05,234 --> 00:00:07,567
Hello and welcome back to the container master class.

3
00:00:07,567 --> 00:00:09,934
We are back with a significant update this

4
00:00:09,934 --> 00:00:13,101
time, with something that has become the center of

5
00:00:13,101 --> 00:00:16,033
the conversation around the Kubernetes ecosystem.

6
00:00:16,434 --> 00:00:20,967
And that is Kubernetes going serverless.

7
00:00:21,601 --> 00:00:25,501
To put it simply, serverless means not having to worry

8
00:00:25,501 --> 00:00:28,767
about the underlying infrastructure at all.

9
00:00:29,234 --> 00:00:32,101
For example, while operating a regular Kubernetes

10
00:00:32,101 --> 00:00:35,201
cluster, we have seen that the user interacts with

11
00:00:35,201 --> 00:00:39,434
the Master and passes on the request through the Master.

12
00:00:40,334 --> 00:00:42,867
When we use hosted Kubernetes, like Google

13
00:00:42,867 --> 00:00:47,167
Kubernetes Engine, we as users talk to the hosted

14
00:00:47,167 --> 00:00:49,901
Kubernetes service providing platform instead,

15
00:00:50,267 --> 00:00:54,434
like Google Cloud, but we do have to manage the cluster.

16
00:00:54,767 --> 00:00:56,601
We are very well aware of the cluster

17
00:00:56,601 --> 00:00:59,967
configurations and we also have to keep an eye on

18
00:00:59,967 --> 00:01:03,267
the resource utilization to see if we have to

19
00:01:03,267 --> 00:01:05,634
scale the cluster for better load handling.

20
00:01:05,801 --> 00:01:10,801
In other words, hosted Kubernetes allows us to host

21
00:01:10,801 --> 00:01:14,401
and manage the cluster on their resources.

22
00:01:14,601 --> 00:01:18,201
But think about this case, all you need is a working

23
00:01:18,201 --> 00:01:21,434
desktop browser, you have to do a few clicks here

24
00:01:21,434 --> 00:01:25,367
and there, and boom, your containerized

25
00:01:25,367 --> 00:01:27,634
application is live.

26
00:01:28,567 --> 00:01:31,167
That is Serverless Kubernetes.

27
00:01:31,167 --> 00:01:33,167
[No Audio]

28
00:01:33,167 --> 00:01:35,601
Behind the scenes or in the backend,

29
00:01:35,601 --> 00:01:38,567
the serverless Kubernetes service provider also

30
00:01:38,567 --> 00:01:41,234
has lots of Kubernetes clusters deployed.

31
00:01:41,934 --> 00:01:48,001
But, you don't have to worry about it. This has a few implications.

32
00:01:48,834 --> 00:01:51,567
First, you do not know the full

33
00:01:51,567 --> 00:01:54,234
details of the cluster that you are operating on.

34
00:01:54,934 --> 00:01:58,101
There are exceptions, but we will get into them later.

35
00:01:58,567 --> 00:02:02,601
Second, the smallest unit of acquisition is

36
00:02:02,601 --> 00:02:05,434
not a bunch of virtual machines anymore.

37
00:02:05,867 --> 00:02:09,567
You're merely given a separate namespace and it is highly

38
00:02:09,567 --> 00:02:12,701
likely that other users are also operating on the

39
00:02:12,701 --> 00:02:14,867
cluster your containers are on.

40
00:02:15,901 --> 00:02:18,967
But you will never clash because of the namespace isolation

41
00:02:18,967 --> 00:02:21,301
and RBAC access policies.

42
00:02:22,367 --> 00:02:23,834
This makes deploying your

43
00:02:23,834 --> 00:02:28,001
applications even faster, economical, and easier.

44
00:02:28,767 --> 00:02:31,867
Google Cloud's Cloud Run is a great example of

45
00:02:31,867 --> 00:02:33,867
Serverless Kubernetes offerings.

46
00:02:34,367 --> 00:02:38,101
In the next lecture, we will get hands on with Cloud Run.

47
00:02:38,101 --> 00:02:42,134
Till then happy learning and I hope you have a great day.