This is the solution video for the Deployment's lab.
So the first question, again, we have to determine the number of ports running in the system.
So let's go to the Domhnall and Ron Kuby still get pots.
So there are no polls running right now.
How many replica sets exist?
So, again, let's try to get replica sets.
The answer is zero.
Now, how many deployments run on the system, so let's run Kubasik, you'll get deployments and the
answer is still zero.
How many deployments exist on the system now?
It appears a few deployments have been created, so let's run the same command again and check.
So right now, we can see that a new deployment by the name of front and dash deployment has been created.
So the answer should be one.
How many replica sets exist, so let's find.
You'll get replica sets and we see that replica set has been created by the deployment.
So there should be one.
How many pots exist on the system now?
Let's try and get pots.
I can see that there are four parts which are in the cluster.
So the answer is four out of all the existing ports, how many already?
So you can see that all of them have the status of irremediable zero or a one.
Already, so the answer should be zero.
What is the image used to create reports for the new deployment, so let's run the command to.
Describe deployments, front and deployment and group for the image.
You can see that the image was just busy, box eight eight eight.
What do you think, the deployment is not ready?
So to find this, let's try and get parts and we'll try and still describe I against one of the parts
listed here.
And if you look at the even section, we can see the reason why it failed, so it says here clearly
that.
The repository does not exist in Docker Hub for the Xbox 888.
And as a result, it was not able to pull it.
So the answer is the image of the Xbox 83 does not exist.
Now let's create a new deployment using the deployment definition file provided a route and it appears
as an issue of this will try to fix it.
So let's first try to created using Kube still apply the F deployment definition, dash one document.
And here we can see an error that says that deployment cannot be fun and we shouldn't be one.
Or perhaps we won, and if you notice.
The word deployment is spelled with lowercase D, which is incorrect.
Will change that and change to change it to uppercase D. So save the file and let's try to run the command
again.
And this time it has been successful.
Now create a new deployment with the blue attributes using your own deployment definition for the name
should be SCDP different and should have three replicas.
And he made a SCPD two point four nine.
So let's copy.
And will you still create deployment?
I'm just going to copy it.
That's the name of the deployment, which is front end.
And the image will make as of dash dash image is equal to a city PD.
Two point four macalpine replica should be three.
So let's add that flack so far of first, let's just create the deployment it will create but just one
part and we can scale it using the capacity of scale deployment dash replicas and the name of the deployment.
So now we should have the deployment ready with three replicas that can verify that using you'll still
get deployments as the front end and here we can see that it is up and running with three pods.
So that's it.
Thank you for joining me and the solution we do.
I'll see you in the next one.