Enable zero-downtime, fault tolerant deployments with health checks
Option | Example | Description |
---|---|---|
Path | /health_check | the HTTP path that should be queried to check if your service is healthy |
Port | 8080 | the port that your service is running on |
Option | Default | Description |
---|---|---|
Initial Delay | 5 | How long Ignite should wait before sending the first health check |
Interval | 60 | How long Ignite should wait (in seconds) between sending health checks |
Timeout | 10000 | The maximum time, in milliseconds, that should be tolerated for receiving a response to the health check. If exceeded, the container will be determined as unhealthy |
Maximum Failures | 3 | How many times the health check needs to fail for a container to be determined unhealthy |
HTTP 2xx
response code, such
as 200
or 204
.
Using the Console
Using the CLI