I wanna ensure
that you fully understand how everything works here.
We just executed this kubectl create deployment command.
This creates a deployment object as I mentioned
and it's then automatically sends it
to our Kubernetes cluster
to the Master Node there,
so to our Control Plane.
And you already learned earlier
in the last course module
that it's this Master Node,
which is responsible for then
creating all the things we need in our cluster
and for, for example
distributing the Pods across worker Nodes.
So indeed, on the Master Mode,
this Scheduler, which I mentioned earlier,
analyzes the currently running Pods
and it finds the best Node for the newly created Pod.
So for the Pods that has to be created
based on this deployment.
And then,
this newly created Pod
will be moved to one of our Worker Nodes.
For example, let's say the bottom one,
because maybe that is the Node
which currently is doing the least amount of work.
This is all done automatically by Kubernetes now,
so that's not something we have to do here.
Now on that Worker Node,
we got this kubelet service,
which I also mentioned in the last course section,
which now manages the Pod here,
starts the Container in the Pod
and basically also monitors this Pod
and checks its health.
Now this part, of course contains the container,
based on the image,
which we specified
when we created this deployment object.
Maybe that was all obvious,
but it is super important that we're all on the same page
and that you fully understand what's happening here
when we run this create deployment command.
So this is what's happening
and that is why we now have a Pod and a Container
running on our Mini Cube development cluster.
With that,
let's now ensure that we can also visit this application
and that we can reach it from outside the cluster.