- Traffic is only directed to containers that pass the check, and
- New builds smoothly roll out without downtime
Options
Protocol-Specific Options
Advanced Options
Creating Health Checks
Currently, Ignite only supports HTTP(s)-based health checks. When setting up a health check, you can choose the HTTP path to be queried to make sure the container is alive. To respond successfully to a health check, you must respond on the path specified when creating the health check with aHTTP 2xx response code, such
as 200 or 204.
Using the Console
Using the Console
- Navigate to an Ignite deployment
- Select Health Check from the sidebar
- Click Create Check in the top right

Using the CLI
Using the CLI