Wait until the system pod is ready again. Make two POST requests to http://[hostname]:31000/system/unhealthy . If you see the same pod name twice, make the request again until you see that the second pod has been made unhealthy. You may see the same pod twice because there’s a delay between a pod becoming unhealthy and the readiness probe noticing it. Therefore, traffic may still be routed to the unhealthy service for approximately 5 seconds. Continue to observe the output of kubectl get pods . You will see both pods are no longer ready. During this process, the readiness probe for the inventory microservice will also fail. Observe it’s no longer in the ready state either.