Set a small default `readinessProbe.initialDelaySeconds` for chronograf
brsolomon-deloitte opened this issue · 1 comments
brsolomon-deloitte commented
Chronograf seems to take a few seconds to start up which consistently results in one or two failed readiness probes.
Readiness probe failed: Get "http://xx.xx.xx.xx:8888/ping": dial tcp xx.xx.xx.xx:8888: connect: connection refused
values.yaml could set and expose a reasonable readinessProbe.initialDelaySeconds for chronograf, which other charts often set in the 5-30 second range.
brsolomon-deloitte commented
(Or, a startup probe could also be used for this.)
The kubelet uses startup probes to know when a container application has started. If such a probe is configured, it disables liveness and readiness checks until it succeeds, making sure those probes don't interfere with the application startup.