Files
cozystack/packages/system
Maxim Belyy 47d9ca01f3 feat(observability-proxy): publish the proxy on its own host
Clients outside the cluster, such as kubectl, scripts and third-party
tools, need to call the proxy with their Kubernetes bearer token. The
kube-apiserver service proxy cannot carry it: kube-apiserver drops the
Authorization header once it has authenticated the request. The console
route sits behind the dashboard gatekeeper, which with OIDC enabled
answers an API client that has no session cookie with 401, and exists
only where the dashboard itself is published. A route straight to the proxy
Service is the path that keeps the token.

It stays off until "observability-proxy" is listed in
publishing.exposedServices, and follows the dashboard for TLS and for
the Ingress versus Gateway API switch.

The edge must not end a request the proxy still serves. The tenant
ingress-nginx reads upstream with a 10s timeout, while a log tail may
stay silent for the proxy's 5m idle limit, so the Ingress waits longer
than that. Cilium leaves Envoy's 15s route timeout in place on an
HTTPRoute that sets none, which would cut every tail, so the route
disables it: the proxy bounds each request on its own.

Assisted-by: LLM
Signed-off-by: Maxim Belyy <maximbel2003@gmail.com>
2026-11-10 18:27:09 +07:00
..
…
…
…