This is the solution video for the static parts lab.
For the first question, we have to find the number of static pots in the cluster and all living spaces.
So let's go to the Domhnall.
And will on Kuby still get parts all named Spaceless?
Now, one of the tricks to identify a static pod is look for the suffix, so most of the time the static
parts would have the name of the node and the suffix or in this case, look for master or node 01 and
you would find that there are four parts which have these effects of the master.
And these are the Cremaster Cube API server, Dash Master Cube Controller Manager, Ness Monster and
Cube scheduler master.
So you can check by grabbing dockmaster and running a word count.
Well, let us keep that and there you go.
We've got four pods and total.
So the correct answer is for.
For the next question, we have to find the components which is not deployed as a static port.
So we already know the four parts which are static ports, and the one which is not in this question
is the core DNS.
So select the gaudiness option.
The next question is quite similar, which of the components is not deployed as a static port?
And here again you'll see that Q proxy was not on that list, your proxy as deployed as a demon said.
So use that option.
On what north are these static pots created?
So let's go and check that.
Is the same gunman as before, use the dash or wide to lose the notes and you'll see that all of them
are running on M..
And this is the reason why all the parts have the suffix of dockmaster.
For the next question, we have to find out the part of the directory holding the static pod definition
files.
To do this, we will check the process for Cubitt and find out the location of the configuration file
that it uses.
So, Ron Pasdar, if and great for cumulate.
And search for dash dash config.
And you'll see in this case that it does slash water slash lab, Kubelik slash config, not YAML.
So let's copy that.
And we have to prep for the static pod parameter in this file, so just grab for static and that file
and it should show you the part where the static pod configuration is stored.
So in this case, it is execution.
It is manifest directly on the master.
So let's go into that location.
And Leslie files were just underneath, so you can see all the four files here, so that's the correct
option, execution of this manifests.
How many poor definition files are present in the manifest folder, so we already know that there are
four static parts, so there should be four files in that directory.
What is the Docker image used to deploy decubitus over as a static port?
So let's inspect the file for Cuba server grep for image in the Cuba episode or YAML file.
And the answer is Cuba server version one, not 16, not zero.
Next, we have to create a static part by the name of static busy box that uses the Xbox image and it
should run the command sleep one thousand.
So to do this, we will create the.
Pod definition file within the same directory, which is when it is manifest and will use inoperative
command to create the file, copy the name of the pod.
So it should be static dash Zyvox.
And the image should be Zyvox.
We'll use the dash dash command to specify the command that the port is supposed to run, which is leap
one thousand.
And finally, we will use the dash dash dry, run dash oyamel.
Don't forget to use the dash actually to never so that it creates the file for the pot and let's redirect
that to a file by the same name with a static dash, busy box dot yaml.
Now, as soon as you create that file, since it's a static pot, it should automatically create the
pot.
Wait for a couple of seconds.
In this case, I made a mistake.
I did not use the actual YAML.
So I'm going to remove this file.
And recreated.
But this time I will specify the natural yaml.
Now, if you check it, you'll get pots.
You should find the static pot running.
But you do not have to specify accuracy to create or still apply against the file that we created as
long as it has been created in the correct directory, which is specified in the Kubelik configuration
file.
It should automatically create the pod.
It's also important to note that static polls do not make use of the scheduler.
Let's check the answer.
Now, let's edit the image on this report to the Xbox One twenty four, so to do this, we can directly
update the file that we created earlier, change the image to the Xbox One to eight.
Not for.
And save an exit, and that should automatically make the changes.
The goods and our earnings shape now, so does Re-created the port.
Let's move on to the final question.
So for the final question, there has been a new static poll that has been created by the name of static
dash green box, where to find it and delete it.
So let's go to the terminal and check out this new pod.
So there is a new report by the name of Static Dash, Green Box National TSRA one which has been created,
and you can see that the suffix of the static part is not the one, which is a good indication that
it is created on the wheel.
Cannabinoids are one.
So we'll have to assess and to know that we want to look the.
Configuration file for the static pod.
To do that, let's first try to get the IP address of the Nozawa.
We will use the additional white option.
If I try a succession of 01, it is not able to assess because it's not added to the DNS or the Horsfall,
so we'll have to use the IP address or copy the internal IP address.
And then it's a search using that IP address, so you can see that the password list is already set
up.
So from the Marsano, you can just search and provide the IP address and it should take you directly
to node 01 non-specified any user.
We don't know which user.
We are making use of road user by default and that's what has been used for setting up the password
less SSL.
So now that we are on that one, let's inspect the Kubelik process just like before.
We will find the.
Kubelik configuration file so great for Ashutosh Config.
And you can see that it's using the same location as the master, which is slash water slash lab cumulate
slash conflict dot Yamal.
So let's look for static in that file to look at the location of the static pot pot and hear the static
pot is different from the master.
It was created under Slash Slash, a directory called Just to Mess With You.
So let's go to that pot and check out the contents.
So there should be a file here which is responsible for the static pot, which we have to delete.
So here is the definition file called Green Box Yamal, so just go ahead and remove it.
Now, exit out of North one.
Well, we are back at the master note, and on Cuba, you'll get pots and hopefully that pot should
have been gone by now.
So there you go, the part has been deleted.
We had just left with the one static pod that we created earlier, so go ahead and check the solution.
Thank you for joining me this lap.
I'll see you the next one.