kayx23 commented on issue #2630:
URL:
https://github.com/apache/apisix-ingress-controller/issues/2630#issuecomment-5425564997
Rechecked this against current releases (Ingress Controller 2.2.0 is latest;
APISIX 3.16.0 and 3.18.0).
The original RC5 report is stale. Health-check **config** is synced in
standalone (ADC + ApisixUpstream `healthCheck` → `upstream.checks`). On
API-driven standalone (`traditional` + `config_provider: yaml`), Control API
**does** return node status after:
1. the route actually matches (first request right after `PUT
/apisix/admin/configs` can 404 because apply is async), and
2. waiting ~2–4s for `healthcheck_manager` to create the checker (first hit
only enqueues it).
Before that, `/v1/healthcheck` shows the empty HTML table / `"nodes": {}`
from the screenshots. After the wait, JSON/HTML listed the upstream node as
healthy/unhealthy.
Updated the title and description accordingly. If anyone still sees a
permanently empty table after a 200 on the route + a few seconds on 2.2.x +
APISIX 3.16+, please comment with versions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
