feat(platform): let the observability proxy attach to the tenant Gateway

With the Gateway API enabled, the publishing Gateway admits routes only
from the publishing tenant and the namespaces in
gateway.attachedNamespaces. The observability proxy publishes its
HTTPRoute from its own namespace, so without an entry the route renders
and is never served.

Clusters that override gateway.attachedNamespaces replace the whole
list and have to add the namespace themselves.

Assisted-by: LLM
Signed-off-by: Maxim Belyy <maximbel2003@gmail.com>
This commit is contained in:
Maxim Belyy authored and ZverGuy committed 2026-11-10 18:27:09 +07:00
1 parent 47d9ca01f3
commit 77acd23bdd
2 files changed
+11

No files matched your search

@@ -5,6 +5,7 @@ suite: observability-proxy package wiring
templates:
- templates/sources.yaml
- templates/bundles/system.yaml
- templates/apps.yaml
release:
name: cozystack
namespace: cozy-system
@@ -67,3 +68,12 @@ tests:
kind: Package
name: cozystack.observability-proxy
any: true
# The proxy's HTTPRoute lives in its own namespace, and the tenant Gateway
# admits routes only from the namespaces listed here.
- it: lets the proxy namespace attach a route to the publishing Gateway
template: templates/apps.yaml
asserts:
- matchRegex:
path: stringData["values.yaml"]
pattern: 'gateway-attached-namespaces: "([^"]*,)?cozy-observability-proxy(,[^"]*)?"'
+1
View File
@@ -668,6 +668,7 @@ gateway:
- cozy-kubevirt-cdi
- cozy-monitoring
- cozy-linstor-gui
- cozy-observability-proxy
- default
# Platform monitoring configuration.
monitoring: