envoyproxy / envoyproxy/envoy

Figure out a minimal healthcheck pattern

Open
#31,619 10 comments 4 reactions 0 assignees View on GitHub
area/docker area/health_checking enhancement no stalebot
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
437

Description

Some of our examples use a healthcheck which relies on the admin endpoint, and uses `curl` to check readiness

Ideally we want a really minimal healthcheck that requires little/no container/system tools to check, that we could include in the published images - adding curl/nc in the distroless container is not trivial/desirable

One way of doing this would be if there were a filesystem file that could be checked for. This would definitely be the ideal

Another possibility - which would still require admin and a util - would be to expose admin only on a unix socket and connect to that with `socat`

I have a current need for something like this - but there is also a recent ticket related to this - #31614

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.