In this demo, we're going to create a deployment.
So let us create a new folder called Deployments within our project directory and within the deployments
directory.
I'm going to create a new file called ADD called Deployment That YAML.
And we're going to make use of the definition file that we created earlier for the replica assets because
it's quite similar to that after deployment.
And to make this easier, we're just going to open the replica set definition file.
On the right.
So I'm going to use the split ed function here.
So on the left, we have the deployment of the ammo file that we're going to create now.
And on the right, we have the replica, said Don YAML file that we created earlier.
So, as before, we will start off with the API version.
And it is and it is also going to be apps slash me one and the same as Republicans said.
And I'm going to use the kind as deployment.
So let me select that from here and then the metadata.
I'm going to enter it here as well.
And that will have the name and labels.
And we're going to use the name as my app Dash.
Deployment.
And I will add a couple of labels as well.
The labels will be front end to your front end and maybe another one called Engine X.
OK.
Now the specked section is very similar to that of the replica set.
So I'm just going to copy this entire section here for the specs, for the spec section, and I'm just
going to paste it here.
So that should be good enough for us to start the deployment.
And I'm going to change just I'm just going to reduce a number of replicas to three.
Okay.
So let's go back to our terminal.
And if we check the route of our project directory, we see the new directory that we created called
DEPLOYMENT'S.
And I'm going to create this deployment using the Cuttle Create Command along with the Dash F deployment
and YAML file.
And as you can see, the deployment has been created.
So let's run the Cuttle Get Deployment's command.
And I can see that we have one deployment which is created and it has three out of three ready parts
and available hard three as well.
So if you want to check the pod, we can run the you've to get parts command.
And I can see that we have three pods which are in the running state, which were created a few moments
ago.
Now, let us run a cube, Carol, describe deployment.
Command and the name of the deployment is my ab dash deployment.
And here we can see a lot of similar information.
So the name of the pod, the label of the deployment itself.
And the the front end label that we set.
And we see the selector that we use the same as that of the replica set, which is equal to my app.
And it has three desired and three available parts which are in the running state.
And here's the pod section.
And the label of the part is my app.
And here's the container details with the image said to Engine X.
If you scroll to the bottom, you'll see that it also has an event section and it just shows the deployment
controller and message, which is that the replica set for this deployment has been scaled to three.
And now before we move on, let's run the cube to get all command, which shows all the objects we just
created in the cluster.
So you can see that we have one deployment, which is the deployment that we created.
And there is a replica set which is created for that specific deployment.
Called my app Dash Replica Set.
And then we have the three pods which have been created using the pad replicas.
OK, well, that's it for now.
Head over to the labs and try this out for yourselves.