Which command sets a readiness probe on a deploymentconfig with a specified URL and timings?

Which command sets a readiness probe on a deploymentconfig with a specified URL and timings?

• A. oc set probe dc/<name> --readiness --initial-delay-seconds=5 --timeout-seconds=2 --get-url=<endpoint>
• B. oc set probe dc/<name> --liveness --initial-delay-seconds=5 --timeout-seconds=2 --get-url=<endpoint>
• C. oc set probe dc/<name> --readiness --initial-delay-seconds=5
• D. oc set probe dc/<name> --readiness --get-url=<endpoint> --initial-delay-seconds=5 --timeout-seconds=2

Answer: (A)

Configuring readiness probes checks when a pod is ready to serve traffic, using a specific HTTP endpoint and timing parameters. The best command uses the readiness probe on the deployment config, points to the URL with --get-url, and includes both timing controls: the initial delay before the first probe and the timeout for each probe attempt. This combination ensures you’re checking a defined endpoint and enforcing how quickly the probe should respond after startup. The other approaches would either switch to a liveness probe, omit the URL endpoint, or omit required timing settings, which means they wouldn’t configure a readiness probe with a specified URL and the desired timings.

Configuring readiness probes checks when a pod is ready to serve traffic, using a specific HTTP endpoint and timing parameters. The best command uses the readiness probe on the deployment config, points to the URL with --get-url, and includes both timing controls: the initial delay before the first probe and the timeout for each probe attempt. This combination ensures you’re checking a defined endpoint and enforcing how quickly the probe should respond after startup.

The other approaches would either switch to a liveness probe, omit the URL endpoint, or omit required timing settings, which means they wouldn’t configure a readiness probe with a specified URL and the desired timings.