Heschi Kreinick 826bc42c71 internal/https: add health checking support and use it ... CL 454935 broke the Kubernetes ingress by requiring IAP on health checks. Move /healthz handling into internal/https, where it automatically bypasses authentication and removes some duplicate trivial implementations. Unfortunately, GKE is not capable of inferring health check parameters from a multi-container pod like relui, so we have to change our BackendConfig. That sets off a yak shave -- I made the questionable decision to use the same backend for all our IAP services, and the coordinator doesn't currently support /healthz. Split all them up and delete the devapp configuration I was using for testing way back in the day. Change-Id: I45e866d30508a07e9a805de70af731dd64c22d7f Reviewed-on: https://go-review.googlesource.com/c/build/+/455215 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>		2022-12-05 19:20:45 +00:00
..
build-ingress.yaml	internal/https: add health checking support and use it	2022-12-05 19:20:45 +00:00