By deploying our pod replicas using a deployment object, we can reap many, many benefits, one of
them being automated deployment.
So by simply declaring a desired number of pod replicas, Kubernetes will always make sure that we're
at that desired state.
Okay, so if one of the pods ends up failing or terminating for whatever reason, Kubernetes will simply
create a new pod to make sure that we always have the desired number of healthy and running pod replicas.
Okay, so, um, that's automated deployment.
You simply specify your desired state in a YAML configuration file, and Kubernetes will continuously
monitor your actual state and always try to bring you to that desired state.
So in our case, um, it's always going to make sure that two great submission API pods are running
at all times, both of them ready to serve requests.
All right.
So let's go ahead and take a look at it now.
What I'm going to do is start by first demonstrating the benefit of automated deployment.
So remember that we've declared a desired state of two great submission API pod replicas.
Now, if one of these pods were to fail or terminate, for whatever reason, Kubernetes is going to
continuously monitor our current state and try to bring us back to that desired state of two pod replicas
automating their deployment.
So I'm going to simulate pod termination by simply deleting it, deleting it kubectl delete pod the
following that's inside of the grade submission namespace.
All right.
Kubernetes is going to notice that we're missing a pod.
And it's going to automatically create a new one to ensure that we're always at that desired state.
That's what these controllers do.
They always monitor our current state and bring us to a desired state.
Um, this is taking a while.
All right.
We're good.
Now, if I say kubectl get pods dash n great submission.
It automatically created a new one.
Okay, so that's the benefit of automated deployment.