This is the solution video for the pod slap, which is our very first lab, so the first question is
for us to find out the number of parts that are existing in the system to do this will go back to the
DOMHNALL and run the command.
Kubek will get pods.
And you can see that currently there are no ports running in the system.
So the answer is zero and the next question, we had to create a new board with the engine image.
Let's run the command cube CTA run in Ingenix Dash Dash image is equal to Ingenix.
From government is one dot, one eight onwards, this command will create a pod and set off a deployment,
which was true for previous versions.
So here we have a pod called Ingenix created to validate let's run CubeSat will get pods again.
And you can see that it is in that container creating state.
So let's go and validate the answer.
And again, we have to check how many parts have been created in the system, so let's run the same
command again.
And now you'll notice that including our next part, a few more ports have been created.
So in total, there are four which are running on this cluster now.
And all of them are in the running states, so the answer is for.
What is the image used to create the new pots and for this, we'll have to look into the description
of the pot?
So let's copy one of these parts and we will clear the screen and on the command cube cubicle, describe
pod and the name of the pod.
And let's grab for the image.
Here we can see that the image used this busy box.
So let's say select Zyvox.
Which notes are these parts, please, John?
So, again, let's go back to the terminal.
And will run the command, Kubek will get parts with the dash, all white option, and this will show
us the north and west deposal place.
So here we can see that all the pods are running on node 01.
So let's select that as the answer.
Now we have to find out the containers that are part of one new port called Webapp.
So first, let's run Gibbsville get web app and can see that under the ready column, we can see one
out of two, which is an indicator that there are two containers running and that port.
We along, we had to find out what images are used for the new Web board.
So let's run the command cubicle, describe pod webapp.
And if you scroll up, we should be able to see these containers which have been created, so there
is one called Agent X and there is another one called Engine X.
So there are two containers which are part of this pod.
What is the state of the container agent X and the port webapp?
Again, we can make use of the same comment as before, which is the described come on.
And you can see that the state is waiting.
So let's select error or wait.
Why do you think the container agent X and the port webapp is in error?
So again, we should be able to find that out from the evil section.
So here we can see that the agent X image could not be pulled out from our dock, Rob, because such
an image does not exist.
What is the red column in the output of Kubek will get parts come indicate.
So we have already seen that the previous question, so let's run.
It will get past webapp again.
And here you can see that the column is ready.
So this shows the number of containers running containers.
In the pod, two running containers in the port, which as compared to the total containers in the pod.
So let's not delete the pod called webapp and to do this will run capacity or delete pod web app.
The port has been deleted.
Now let's create a new pod with the name Redus, and the image right is one, two, three.
So this image does not exist, but the respective puppet and create this pod.
So let's use the same commanders before.
We use Kubek Children, Reader's Digest, our image is equal to readers, one, two, three.
But first, we'll make use of dry run is equal to client.
This will allow us to.
Create a dry run of the pot.
It will not create the pot, but we can use Oyamel to redirect the YAML definition into a file called
pot.
So let's open up this file using the editor.
And you can see that in this case, we have a pod called Red is the name of the container is also released,
but it's using a wrong image called Redus.
One, two, three.
So let's save this file.
And created using Kubek to apply the F and name of the poor definition for just Baudot yaml, it's now
the part has been created.
So let's go back and check.
Now, finally, we have to fix the image on the iPod Redus.
And to do this, we will use Kubek edit Pod Redus.
That should open up the running configuration and we, Ed, and let's scroll all the way to the bottom
and find the feel called image and will change it from readers want to try to read reduce.
Was the Susanville safe before?
And that should be it, the response should be updated now with the correct image, which is also called
Redus.
So give it a minute.
So now it's in our state and that should be the end.
That's our last question.
So thank you for joining me in this video.
I'll see you in the next one.