> In theory it should, because they do health checking to track status of the upstreams.
I think the PR that pushes this kamal-proxy project explicitly removes supports for healthchecks? So it's unclear.
In theory, a reverse proxy like Traefik supports this feature.
In practice it does too.
So I don't know. It seems there's some rationale that's definitely missing from the whole story. I doubt people haphazardly decide to roll out a custom reverse proxy developed in-house. The reasons laid out in the doc definitely don't seem to be it.
I'm looking here https://github.com/basecamp/kamal-proxy/tree/main/internal/s... which is the code for their v2 proxy. Notice there's a health_check.go which makes requests in a goroutine and sets the health to true/false based on the HTTP status, via a consumer interface.
As I said elsewhere in this topic, this is all too basic IMO, (disclaimer: I'm a Caddy maintainer) Caddy does this all in a more robust way.
I think the PR that pushes this kamal-proxy project explicitly removes supports for healthchecks? So it's unclear.
In theory, a reverse proxy like Traefik supports this feature.
In practice it does too.
So I don't know. It seems there's some rationale that's definitely missing from the whole story. I doubt people haphazardly decide to roll out a custom reverse proxy developed in-house. The reasons laid out in the doc definitely don't seem to be it.