Add readiness probe to execution pods #3720
Assignees
Comments
godber
added a commit
that referenced
this issue
Aug 22, 2024
This PR makes the following changes: - Adds readiness probe to `execution controller` job (_**Only applies to k8s V2 backend**_) - Worker deployments will now wait for the ex readiness probe to come back as `ready` before creation. - Adds `/ready` endpoint to execution controller server - Will return with status code `200` when initializing is complete - Will return with status code `503` when initializing either fails or hasn't yet completed - Bumps **@terascope/teraslice-messaging** from `v1.2.0` to `v1.3.0` Ref to issue #3720 --------- Co-authored-by: Austin Godber <godber@terascope.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating a new execution controller job resource in kubernetes, we check to see if the execution controller pod is operational by looking at the pod status. If the pod status is in a
runningstate, we proceed to create theworkerdeployment.The issue is that checking to see if the pod is in a
runningstate is not a good indication that the execution service is ready to have workers connect and start distributing slices.Adding a
readiness probeto the container and checking to see if the readiness probe currently is returningtruewould solve this.I'm looking to see if there is already a built in health check on the
execution controllerto see what we can use to verify it'sready.The text was updated successfully, but these errors were encountered: