ApiHealth
Readiness: the pod can serve proxied traffic.
GET
Every proxied request needs Redis (cluster registry, sessions, throttling),
so the pod is only ready when Redis answers a PING within 2 seconds, and
once the boot-time OIDC discovery has succeeded (it retries with backoff
instead of crashing the pod while the IdP is down).
Ready to serve traffic.
application/json- response
Body of the readiness probe.
controller*stringfailing while the controller's ProxyKubeApi watch has kept failing
for 5 minutes, ok otherwise. Informational: it never makes the pod
unready, the proxy keeps serving from Redis.
oidc*stringok once the service-wide OIDC provider has been discovered, pending
while the boot-time discovery is still retrying.
redis*stringok when Redis answered a PING, unavailable otherwise.
curl -X GET 'https://example.com/management/ready'Example Response
{ "controller": "string", "oidc": "string", "redis": "string"}