docs(dashboard): note the observability proxy client in the console guide

The next session needs to know why one module bypasses the typed
Kubernetes client and where the charting dependency is loaded.

Assisted-by: LLM
Signed-off-by: ZverGuy <maximbel2003@gmail.com>
This commit is contained in:
ZverGuy committed 2026-11-04 05:47:28 +07:00
1 parent 290490769e
commit b05323f6be
1 file changed
+2
@@ -32,6 +32,8 @@ Implications:
- **RJSF** (`@rjsf/core` + `validator-ajv8`) for application config forms.
- **Vitest + jsdom + @testing-library/react** for tests.
- **Monaco** for YAML view, **noVNC** for the VM console tab.
- **uPlot** for the Metrics tab charts, lazy-loaded with that tab.
- Metrics and logs come from the observability proxy, not kube-apiserver: `lib/observability/proxy.ts` reads its native Prometheus JSON and VictoriaLogs NDJSON through `K8sClient.raw`, under the paths nginx routes to it ahead of `/apis`.
## Dev loop