Configure health checks
Configure supported HTTP or command checks and verify the resulting health status.
Open Healthcheck on a container to see the settings supported by its deployment type. Some deployments use a health check defined by the image; the Console displays these as image-managed rather than editable.
Configure health checks before deploying
Without a health check, requests can be dropped during a rollout, and deployment can proceed without being aborted even if the container image has problems.
Configure an HTTP check
- Enable Enable health check and select HTTP as the Check type.
- Set the method, protocol, host, port, and path for an endpoint available inside the container.
- Set the interval, timeout, retry count, and start period for your application's startup behavior.
- Select Save health check, then Restart the container.
The image must contain curl or wget. This check runs inside the container; use the application's internal address and port rather than treating the public domain as the default check target.
Configure a command check
Select Container command when that option is available. Enter an executable command present in the image. The process exit code determines the check result: zero indicates success.
Health check commands run directly. Shell operators such as ;, |, &, $, >, and < are not supported. Save and restart to apply the change.
Verify the check
After the restart, inspect the health status in Overview and application output in Runtime Log. Allow for the configured start period before investigating a startup failure.
When checks are image-managed, update the image's health check configuration through the deployment workflow available for that resource. A healthy internal check does not by itself verify public DNS or firewall access.