 In this video, we are going to create the aliveness probe. So that's slightly different than a readiness probe. The readiness probe basically tells Kubernetes when the application has started up and is ready to start accepting traffic. Aliveness probe is a health check saying that, hey, I'm alive and I can continue to accept traffic. So slight difference, but very important nonetheless. So I'm going to go in and edit the deployment. And when I come down here, we do have to set one more environment property. I'm going to come in here and say, and again, this is to enable, go ahead and enable that aliveness probe. So we're going to come in and say name, again, as management health. And this time it is aliveness state. And we'll give this a value. And just as before, we can come in here. And let me try to get this up off the bottom a little bit. This time we have a liveness. Again, we'll be using an HD2 get. Yeah, it's actuator health. And creatively, this is going to be liveness. So this is going to be our health check. I'm just going to double check the spelling there. That all looks correct. So let's go ahead and save this. And again, we can go ahead and apply this. I'm going to go ahead and fix this real quick. I'm going to pause the video while I do so. So came in, so I have a typo there. I have a quote instead of a colon. So very, very easy mistake to make. So I suspect this will work much better now. And we can see that that has been applied. And we can see that we have one instance terminating the other one starting. Go ahead and get this one that's starting up. Take a quick look at the logs. And we can see that we are up and running. And now we are up on 30.159. That is the port that this came back up on. Let's toggle over to Postman. Go ahead and send that. We can see that we are up on the readiness. Let's check the liveness endpoint. And we can see that is up as well. Come back over to the command line. And we can see that our application is up and running. Again, Kubernetes has now been configured periodically. Check that endpoint to make sure that the service is up. So we configured two things. One is a readiness. That is basically saying to Kubernetes that the service has started up and is ready to start accepting a request. The other one is a health check, the liveness. That tells us that the application is still alive and able to accept traffic. So if we look at our deployment, you can see here, this is the complete configuration for it. So we've had to set up three different environment variables. So starting up with to enable the health probes, to enable the readiness, and then also to enable the liveness state. And then we have the liveness probe. That is, they are both doing HDP gets against port 8080. And for the liveness, we are going to actuate our health liveness. And creatively enough for the readiness, we are actuating our health readiness, the two different paths that Kubernetes are going to be using to monitor our spring boot application.