 Okay, in this video we are going to talk about setting a readiness probe. So readiness probe basically tells Kubernetes that the container is ready to start accepting traffic. And if you're running Spring Boot 2.3 or higher, this will be available in the Spring Boot actuator. So very important that you're on a more modern version of Spring Boot to have this functionality. Otherwise, what I'm showing you in this video will not work. So again, it's Spring Boot 2.3 or higher. And we need to do two things here to enable the readiness probe. One is to set the environment properties for Spring Boot actuator to enable this. And then the second is to tell Kubernetes to utilize it. And we'll do both of those in the deployment YAML, the descriptor for our Spring Boot application. So here you can see for the environment property, we'll go ahead and work on this. So again, this is going to be a name value pair and YAML, this is going to be a list. So we'll do name. And in this case, it is management underscore endpoint underscore health. Again, this is for the Spring Boot actuator. So management endpoint health probes enabled. Just double checking to make sure I don't have a typo there. And in this case, we want to give it a value of true. And we also need to go ahead and add in a second property, and this is going to be management. And we'll do readiness, and again, the value would be true. And then also we need to set up a new property for this. And this is for the Kubernetes configure. So these two environment properties that we set are going to basically tell Spring Boot to expose the probe. And now we need to configure the probe for Kubernetes to use it. So the way we do this is set up readiness probe. So that's going to be an HTTP Git, port 8080. That's the port that Tomcat's coming up on, the default port. And then path health readiness. So that configures Kubernetes, telling Kubernetes to go do an HTTP Git against port 8080 at that path of actuator health readiness. So let's go ahead and write this file. And then kubectl, ply minus f, deployment, and made a mistake there. Let me pause this and resolve this. So I took a closer look at the problem there, and Kubernetes is expecting these values to be explicitly strings. And it did not like the unexcaped boolean values, but going ahead, setting those values to strings using the quotes. I think with YAML, you can also use single quotes that did clear up the problem. So I reloaded it, it did load up properly. And let's go ahead and quit out of the YAML. And you can see the kubectl Git all, and let me clear this and get a better view for you. You can see that we are up and running properly. So the readiness probe is working. And let me toggle over to Postman. You can see here I'm going to actuator health readiness. I can go ahead and send that. And we can see that endpoint is being exposed, and we are getting a status back of up. So that is the desired response for Spring Boot actuator. So I'll go back over to the terminal. And just to recap what we changed here, we added in the environment properties for management and endpoint health probes enabled, and then specifically management health readiness state enabled. And then we do have for the boolean properties, we do have to escape those as proper strings. And then to tell Kubernetes to use the readiness probe, we are doing readiness probe, specifying an HTTP Git on port 8080, and that goes to the Spring Boot actuator health readiness URL. And you can see from the Postman example that path is exposed and returning back an up status for us.