WEBVTT
00:00:06.440 --> 00:00:10.680
Yes, please go ahead.
00:00:27.960 --> 00:00:36.980
It is more than that. It is more than that because every group is trying to address a different set of problems, right?
00:00:36.980 --> 00:00:45.020
So by grouping, let's say you have rolling update feature, right?
00:00:46.120 --> 00:00:49.180
So making the features available for different groups.
00:00:49.540 --> 00:00:55.780
I mean, that categorization is purely done to manage those resources effectively.
00:00:56.500 --> 00:01:03.420
So there are commonalities amongst different resources and they wanted to put it in a single group.
00:01:03.420 --> 00:01:10.620
So it's not about access permissions or whatsoever.
00:01:10.720 --> 00:01:21.800
It's more on how Kubernetes is managing those resources, how functionalities are shared, how the functionalities are reused from those perspectives.
00:01:24.240 --> 00:01:33.860
For the RBAC, you can, I mean, API groups is not related to the RBAC that you are going to defend.
00:01:33.920 --> 00:01:42.060
This is totally unrelated because if you define a role, it doesn't matter which API group it is part of.
00:01:42.280 --> 00:01:49.180
You can define a role referring a resource that is part of any API group.
00:01:49.180 --> 00:01:53.240
Okay. All it matters is you are referring that resource. That's it.
00:01:53.260 --> 00:01:55.720
The verbs that can that are allowed in that resource.
00:01:56.740 --> 00:02:00.780
Okay. If you want something at a cluster level, then you need to create cluster role.
00:02:00.940 --> 00:02:06.800
So at the RBAC level, we have two resources, right? Role and cluster role, role binding and cluster role binding.
00:02:07.740 --> 00:02:16.200
So that API group does that doesn't determine whether it is at the namespace level or at the cluster level.
00:02:16.200 --> 00:02:21.260
It's only the role primitives like role and cluster role determines that.
00:02:21.260 --> 00:02:30.000
Is it clear? Okay. Correct. Correct. Correct. Correct. Welcome.
00:03:03.160 --> 00:03:04.560
Okay.
00:03:25.220 --> 00:03:25.260
Okay.
00:03:57.520 --> 00:03:58.920
Okay.
00:03:58.920 --> 00:03:58.940
Okay.
00:04:00.260 --> 00:04:01.080
Okay.
00:04:01.080 --> 00:04:02.220
Okay.
00:04:14.740 --> 00:04:16.140
Okay.
00:04:16.800 --> 00:04:17.520
Okay.
00:04:19.920 --> 00:04:21.320
Okay.
00:04:21.320 --> 00:04:22.660
Okay.
00:04:22.660 --> 00:04:23.500
Okay.
00:04:24.180 --> 00:04:25.580
Okay.
00:04:25.580 --> 00:04:25.620
Okay.
00:04:25.620 --> 00:04:25.640
Okay.
00:04:53.780 --> 00:04:55.180
Last
00:04:55.180 --> 00:04:57.700
three minutes to complete this activity.
