f576575ebb
The catalyst-api Deployment hardcodes OPENOVA_FLOW_SERVER_URL as http://openova-flow-server.catalyst.svc.cluster.local, but the Service is installed by bootstrap-kit slot 56 (56-bp-openova-flow-server.yaml) with spec.targetNamespace: catalyst-system. In-cluster DNS resolution of the .catalyst.svc.cluster.local hostname therefore failed on every mothership + Sovereign — /api/v1/flows/{id}/snapshot|stream|events returned 502 and the Sovereign Console Flow canvas stayed empty. Discovered on t34 T3 walk by agent a9e0547e (TBD-A56). Fix: update the env value to .catalyst-system.svc.cluster.local. The Go default constant defaultFlowServerURL already pointed to the correct namespace, and 57-bp-openova-flow-emitter.yaml's flowServerUrl also already uses .catalyst-system — so this is a single-file env correction with an aligned comment update in handler.go. Chart 1.4.198 → 1.4.199; bootstrap-kit pin in clusters/_template/bootstrap-kit/13-bp-catalyst-platform.yaml bumped to match. Validation: - helm template products/catalyst/chart renders the env value as http://openova-flow-server.catalyst-system.svc.cluster.local - git grep openova-flow-server\.catalyst\. returns only the descriptive comment in Chart.yaml that documents the previous bug. Refs #1948 Co-authored-by: hatiyildiz <hatice.yildiz@openova.io> |
||
|---|---|---|
| .. | ||
| axon | ||
| catalyst | ||
| continuum | ||
| cortex | ||
| dmz-vcluster | ||
| fabric | ||
| fingate | ||
| openova-flow | ||
| relay | ||
| sandbox | ||