A licensing microservice needs a custom in-container check that runs a shell command and uses its exit code. Which probe handler fits?
Select an answer to reveal the explanation.
Short Explanation
Sometimes health isn’t an HTTP path—it’s ‘did this script exit cleanly?’ An exec probe runs your command in the container and passes on exit code 0. Keep the command light so probes don’t become the outage.
Full Explanation
exec probes invoke a command list inside the target container; exit status 0 means success, non-zero means failure. They suit custom checks when HTTP or TCP alone is insufficient. Annotations are not probes. Random HTTP ports or probing the control-plane API do not evaluate the container’s intended health command.