help request: How do you do health-check to ApiSix deployment (liveness/readiness probes) #11971
Description
Description
Hello ApiSix people,
I'm trying to figure out how to do a health check on the ApiSix deployment itself.
Looking at the K8s/Helm implementation, the stateful set/pods do not have liveness/readiness probes set at all.
Is there a special port or endpoint on the GW(9080), AdminAPI (9180), or somewhere else for a simple /healthz check as others do?
I'm trying to deploy to GKE K8s through the new K8s Gateway implementation, but the health check always fails.
I've made a proxy on the GW(9080) /healthz to hosts like 127.0.0.1 and *.10 (since the GoogleHC sets the host to http://10.1.1.10 for example)... but no luck, ApiSix always says 404 route not found.
GW(9080) /healthz - just proxies the requests to Istio health check /healthz/ready port 15021
Any ideas are welcome!
p.s is there another way to get access to the Slack channel? sent an email already a while back, but no luck... or it is meant only for @apache.org users?
Environment
- APISIX version (run
apisix version): v3.11 - Operating system (run
uname -a): GKE K8s (Linux gke-***-node-p-5f54990d-0vbu 6.1.100+ change: added doc of how to load plugin. #1 SMP PREEMPT_DYNAMIC Sat Aug 24 16:19:44 UTC 2024 x86_64 AMD EPYC 7B13 AuthenticAMD GNU/Linux) - OpenResty / Nginx version (run
openresty -Vornginx -V): / - etcd version, if relevant (run
curl http://127.0.0.1:9090/v1/server_info): (buildt in etcd on apisix 3.11 - APISIX Dashboard version, if relevant: /
- Plugin runner version, for issues related to plugin runners: /
- LuaRocks version, for installation issues (run
luarocks --version): /