This is the solution video for the Saeki, a mock exam one, so for the first question, we have to
deploy a bot named engine expert using the Ingenix out by an image.
To do this, we will use the imperative come on, Cuba, we'll run.
The name of the port is in the next part.
And the image is Ingenix Alpine.
So this should create a pot by that name and image.
That's verify using capacity, get pots can see that it's in a container creating said.
Now it's now running state, so let's move on to the next question.
Deploy our messaging pod using the latest Alpine image with the labels set to cheer as a call to message.
So we'll use the same comment as before.
Let's copy the label.
And we'll use the same command, Cukier.
Run.
And let's change the name of the party to messaging.
The inmates should be released, Alpine.
And we'll use the dash el option and paste the label, which is a key value pair here as a message.
So now that part has been created.
We can validate by running Kubasik, we'll get parts that are shoe labels.
And we see that messaging has called decreased global.
Next year, to create a namespace by the name of Apex Dash X nine nine eight four five seven four,
so let's copy the name of the namespace and we'll use the command cube to create an S, which is short
for namespace and P is the name that has created the namespace.
So yeah, let's move on to the next question.
So for this, we have to get the output of all the notes of the cluster in adjacent format and redirect
to a file.
So to do this, we will run Cuba, we'll get notes.
And we'll get that enough format of Jaeson using the dash or.
Jason.
Come on.
So first, let's try and get we see that there are two notes.
So now let's use Dasch or Jason, which gives us all the details and a decent format.
And now let's redirected to the file.
That should be it.
Let's move on to the next question.
Create a service called Messaging Service to expose the messaging application within the cluster on
board six three seven nine.
So now we have to create a new service for the part that we created earlier called messaging, and it
should be exposed within the cluster on board return.
So for this, let's use the command cubicle expose.
Part.
The name of the pod, which is messaging the name of the service as messaging service and a space that
here and let's use that dashboard as equal to six three seven nine.
We also have to provide the target board, which is six three seven nine.
And that should be it.
So if you're on this command, it should automatically create the service for the great selectors.
So let's use Kube still describe as we see.
And here you can see that it is using the port 67 nine.
It has got one end point and it does using the correct selector of TerraCycle message.
And it has created a cluster type type service.
So let's move on, create a deployment named H.R. Dasch Web app using the image called cloud web app
color with two replicas.
So let's copy the name of the image from the question.
And we'll make use of the command cube to create deployment.
The name is H.R. Dasch Web app, the image name, let's be Sudheer.
And to scale it to two replicas will use still scale deployment.
The name of the deployment dashers replicas is equal due to.
To validate Lindstrand capacity, you'll get deployment's, and here you can see that it two of two
pots ready.
Next year to create a static board named Static Dash busy box on the Mustonen that uses the busy box
image and the command sleep one thousand.
So this should be a strategy box, so we'll have to create a configuration file and place it in the
pot use by Satake Pots.
So let's generate the configuration file for the part first, so we're making use of your run.
Let's name it to static.
The Xbox, the image, let's change it to the Xbox, let's move the label.
And let's at the command, which is.
Sleep one thousand.
And let's use the dry run feature here, created another in Yemen format and redirected to a file called
Static Dash Xbox.
So right now it is creating it and the root directory will.
Update the configuration file if needed, but it looks like everything is.
As it should be, so let's determine the directory where the.
Such reports are created by default for Cuba, Adam created clusters, it was created under the D.C.
Cabinet as manifest directory.
So here we have four files for the four static parts for our controlling components, so this is where
we should be adding that in part to validate let's check the Kubelik configuration.
So here, let's go to see this wall Kubelik and graph for the string static part within the conflict
document.
And here you can see that the static part part is set to discriminators manifest actory as expected.
So now we will just move the file that we created in the root directory called Starting with the Box,
and we'll move it to the appropriate directory, which is it is when it is manifest.
And now if you're on CubeSat, you'll get Pottz.
You should see that allostatic part by the name of starting the Xbox.
Masser has been created.
Now create a board in the finance namespace named Damp Bus with the image is Alpine.
So we have to create a part in a different namespace.
So first let's check of the names with exists so we don't get in.
As I can see that the finance needs to be a success.
So, again, let's make use of the same as before, which is still run.
So let's make sure that we have the correct options for the comments being used, so the name should
be tempered by bus and it should use its Alpine.
So let's seize the image name first.
And then the name of the pod.
OK, so now we are redirecting the configuration to allow you to move to.
Call Baudot YAML.
You know, we can also try to add the name space feel within the come on and let's see if that works.
So looks like that did not take, but that's OK, we can add the value within the file.
So here I am in the editor, so I'm just going to add the namespace is equal to finance under the metadata
section.
The rest of the fields look correct, so let's create this pot.
What has been created, let's verify by checking it and the finance ministry and you can see that it
is running.
We want a new application called Orange is Deployed.
There's something wrong with it, identify and fix the issue.
So first, let's check if a deployment or a part has been created by the name of Orange.
So first, let's check deployments.
So it looks like it's not created.
Let's check what's.
And you can see that there is a report by the name of Orange, and if you see the cities, you can see
that it is in a crash to back off.
And you can also see that it has gotten in a container, which is in a crash back of it.
So let's describe the part.
And scroll up and see the status.
So they should have two containers, one should be in any container and one should be regular.
So this is the regular container by the name of orange container, which is innervating, said the most
likely it's waiting for the container to complete.
So.
Let's crawl up and here is the container called a net dash my service, and that is innervating state
and the last state was terminated.
And if you see the command that it's using is incorrect, there's a typo for the come on sleep.
So, yeah, let's fix that.
And as a result, that's the reason why the parties in arrows said, so let's get the configuration
and the Yamal format for the part, then will delete the existing part, wait for the part to terminate
completely, and then we will edit the configuration file that we just generated.
So let's go down to the container section and look up the come on sleep, which is incorrect here.
Let's correct it and save the file.
Now, if we create the part, it should work.
So, again, let's check the status.
And you can see that the container is running those initializing and now it's now running straight.
So that means that the container was successful and the second regular container is now running as well.
So for the next question, expose the HRR Web app as a service, the name of the service at our Web
Dash Abda service, it should be exposed on both.
Three hundred eighty two on the nose of the Colossus on this case, we have to create a new inaudible
type service.
So we have already created that the deployment, which is at our Web dash app.
So to do this, Let's Run explores deployment, the name of the deployment.
And the name of the service.
And we'll make use of dash dash type, the call to not put.
And let's make use of the port, which is.
Eight zero eight zero and the target put as AIDS rates were as well.
So, again, we'll make use of the dash dash dry run.
There is currently no way to specify the name of the norpoth or specify the note put two three zero
zero eight two.
So we'll generate a configuration file.
And redirected to escort YAML, let's manually update the node port.
Two three zero zero eight two.
And that should be it, so we can now save this file and create the service.
To validate, let's try and describe, as we see in the name of the service and here we can see that
it has got to end points and it is using the norpoth type, which is said to translate to.
So for this next question, we have to make use of decent battery to retrieve the EU's images of all
the notes and store it and have fun.
And there is also a hint that the US images field is under the north info section under the status of
each port.
So in this case, we'll make use of these and Pat.
And we'll also make use of the documentation.
To help us get the correct come on.
So now let's go to the corner of documentation and search for Jason.
And here you'll find that there is a document called Cupidity Your Cheat Sheet, which is really handy
and has a lot of examples for all the cube still commands.
And if you scroll down, you'll see a lot of examples related to this in part as well, which can be
pretty handy to make use of during the exam.
So in this case, it's specifically looking for capsid.
You'll get notes and there is an example which is perfect for this use case.
So, yeah, let's copy it and try to list the node configuration using this in.
In this case, we have to make use of the flag, which is mezger.
So let's add that.
And in this case, we are trying to list all the items within the node configuration.
So that'll pull out a lot of information.
That's not what we need.
So we'll have to drill down even further.
And from the question we saw that it should be under the status section.
So, yeah, let's drill down even further.
So should be under status dot info.
And you can see that it has filtered the output a little bit, but again, we are looking for B with
the image.
So if you're not really sure, we can still get no or Jason.
And here I'm using a picture of less and we can see the entire Jaeson output this way and we can look
at the section that we really need to drill down.
So in this case, we know that the north info is under the status section.
So you just scroll down or you can also make use of such.
You'd at least like grep or search within the text editor itself for the feel that you're looking for
and try to create the command.
So this is optional.
But, yeah, something which can be handy if you do not know which section to pass through and which
command to use.
So in this case, against that, there is an order and protection under the status and within that we
have a map with image which provides V with image for all the notes of this cluster.
So, yeah, let's go back and update our come on.
So, yeah, let's add in with image.
And this should narrow down and print out only the EU's images for the notes, so that looks like the
correct options.
And now let's read directly to the file, which was asked and the question.
And that should be it.
So let's move on to the final question.
So we had to create a volume and the spec is provided on the right.
So for this, again, we'll make use of the equipment and his documentation.
There are no imperative commands as of now which we can use to create a persistent volume.
So we'll use an example from the documentation.
So in this case, it is making use of a hotspot.
So all we need is the template to be used.
So let's scroll down.
I'm just searching for a spot here.
And see if there is an exact example that we can use.
And in this case, we don't see example of persistent volume, which makes use of hotspot directly,
but that's OK, we can make use of our template and add the required field.
So in this case, doesn't look like there is an exact example that we can copy, but yeah, let's just
copy the template.
Of opposites in volume.
And so we'll make use of this template here.
So, Kopi.
Some of the lines.
And we'll update it and according to our question.
So I'm going to create a file called Dot Yamal.
And the name of the process and volume should be read and latex.
Let's go back to the documentation.
And copy this back section as well.
So let's update the mood.
It should be retried many.
We do not need the volume also, I'll delete that and let's update the size of the posts volume as well
in accordance to the question.
And the last thing that we want to add is the whole.
So that's not something which is in the documentation.
At least not a direct example that we can use, but in this case, it looks like they are using Neff's
material just seems like the worst part and U.S. option.
So one other comment that I find handy is Kubasik, you'll explain, and the object and make use of
the dash recursive.
So here I'm using less and within that I'll search for Hotspot just to see the different options that
has to be used with this field.
So you can see that the hotspot has an object.
And that the object name is.
So that's something that we have to add in and that should be under the spec section, so let's make
sure that it is intended correctly.
And within that, as we saw in the cubicle explain command, there should be a part feel that we have
to enter and this is the whole spot which we have copied from the question.
So that should be heard.
Let's now create the processing volume using capacity or create.
And you can see that deposition volume has been inspected by running CubeSat, you'll get Peevey, which
is short for position volume.
And here you can see that deposition volume with the correct options has been created.
The access straight right?
Many the signs is great and the current status is available.
So that should be it.
We can also run capacity of the strike to make sure that the it is using the correct spot.
So here it is using the bodies.
But the question.
So now let's end the exam and run the evaluation just to make sure that we've got everything correct.
So in case you got any of the answers wrong, you can go back to the Domhnall and fix it and run the
evaluation again.
So don't worry if you get anything wrong in the beginning, but that's the end of the solution.
We do.
Thank you for joining me and I'll see you in the next one.