2:14:39
2025-06-26 09:07:32
1:12:32
2025-06-26 09:11:34
6:42
2025-06-26 11:08:41
35:51
2025-06-26 11:24:37
38:41
2025-06-26 13:21:35
20:37
2025-06-26 15:06:35
51:46
2025-06-27 09:06:19
58:45
2025-06-27 09:06:25
36:01
2025-06-27 11:26:09
1:12:38
2025-06-27 13:45:09
Visit the Kubernetes Comprehensive 2-Day course recordings page
WEBVTT
-->
All right, I'm recording, but I don't do you.
-->
So you might have to refresh you or...
-->
Oh, there we go.
-->
Okay, all right, so what I was trying to say
-->
before I lost internet is you had an extra L in there,
-->
which is...
-->
Let's describe the pod and take a look at the pod.
-->
Or describe...
-->
Correct.
-->
And what did we label the node?
-->
Yep, so we're just going to re-vene on that file and just change the very bottom to test from fail.
-->
So we need to delete it first.
-->
So do you use that, but just change apply to delete.
-->
Oh, whoops.
-->
And you're going to use that same command, but that you had Coup control, apply them on itself.
-->
Just change the word apply to it.
-->
All right, friend your same test again.
-->
And we have node type equals test, right?
-->
So we put that in there correct.
-->
So now let's go look at the node.
-->
Let's just get the labels from the node.
-->
Q control, get nodes, and then hyphen, hyphen, show, hyphenly.
-->
All right, see if you can find that in there.
-->
Okay, what's in front of node type?
-->
Yep.
-->
Okay, so let's pseudo them again.
-->
There you go.
-->
And you will see teams use shortcuts.
-->
on node labels, but the proper convention is to use whatever the API is in front of it.
-->
In this case, it just happens to be Kubernetes.io, but there are others as well.
-->
And so if you get in a habit of using the Kubernetes convention in front of it,
-->
then you'll start to notice other teams that just use shortcut for label names.
-->
So if the label name needs to match, exactly.
-->
Okay, and test it again.
-->
All right.
-->
Yeah. Go ahead and check those events out.
-->
Take a look at the logs.
-->
There we go. We're up and running.
-->
All right. So how do we check the node resource utilization?
-->
So let's describe the node. All right, so you can see we have
-->
resource utilization. We've got requests for CPU of 5%,
-->
limits are zero, memory is 1%, limits are
-->
220 so that would be over here and then you can see our node nodal selector is zero CPU
-->
request zero memory zero limits so it has nothing that it is requesting okay delete the pod
-->
using a different method so we're going to do cube control delete on node nodule selector
-->
and we're going to also delete remove the label all right and it you can see it's very
-->
descriptive it told me that node nodal selector was deleted the pod and minicube was unlabeled right so we
-->
could go ahead and check those just to verify it it's pretty descriptive okay now we're going to check
-->
the kuk config expiration and signature algorithm locate the kube config file in the mini kube cluster and
-->
obtain the client search all right so ls there we go and we can see that um config is actually a file
-->
It's not very descriptive.
-->
It just says config.
-->
So I would name it a YAML file on my production clusters with a descriptive name.
-->
It's MiniCube.
-->
So you can cat the config and see what's in it.
-->
And where is the client cert located?
-->
So it's in the home minicube.
-->
Dot MiniCube Profiles minicube directory, right?
-->
So we're going to CD into that directory.
-->
Oh, yes, here's a student.
-->
student yeah they overwrite oh yeah and then remove the client dot cert so you can cd into that
-->
but then just remove client dot cert oh yeah it's remove client dot cert okay and cap the client
-->
dot cert okay what is the not after date show up to the top okay 20 25 so minicube gives you a three-year
-->
search. Now, production clusters typically have a one-year cert. MicroK8s gives you a 10-year,
-->
I believe. Then what type of signature algorithm is used? And you can change that, by the way,
-->
when you build your own clusters. You can use different types of signature algorithms.
-->
And then what X-519B3 extensions are present? And the CA is false. Did you notice that? So this cannot
-->
be used to generate server search within the cluster. This is just for connecting to the Kubernetes
-->
API. So this is your entrance into the cluster that you've protected all costs. All right. So in lesson
-->
one we learned how Kubernetes nodes and pods work together, how Kubernetes components work. We
-->
learned how Kubernetes versioning works and what needs to be done at the end of life, how to label nodes,
-->
how to pin nodes to a specific node using labels
-->
and node selectors.
-->
And what is the estimated life cycle
-->
of the Kubernetes cluster?
-->
And why?
-->
Well, the estimated life cycle is no more than 13 months, right?
-->
So when we look at the life, the end of life for each version,
-->
then the in a production cluster your TLS cert is good for 12 months typically so your life
-->
cycle of the Kubernetes cluster is about 12 months from the time it's created and you can
-->
extend your your cert out and you can definitely run a cluster past end of life without
-->
upgrading but it's designed to be upgraded it no more than a 12-month