From 0fc955989af5fb72cff109c9496e04a41cafa1d9 Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 24 Aug 2026 23:17:08 +0200 Subject: [PATCH] chore(deploy): enable central MCP on main-8221216 --- deploy/railiance/apps/helm/state-hub-values.yaml | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/deploy/railiance/apps/helm/state-hub-values.yaml b/deploy/railiance/apps/helm/state-hub-values.yaml index 7c16c97..9b40ece 100644 --- a/deploy/railiance/apps/helm/state-hub-values.yaml +++ b/deploy/railiance/apps/helm/state-hub-values.yaml @@ -6,11 +6,18 @@ namespace: image: repository: forgejo.coulomb.social/coulomb/state-hub - tag: "main-697dd49" + tag: "main-8221216" ingress: enabled: false +# MCP layer on central (CUST-WP-0067-T08). Enabled together with the image tag +# above: MCP_HOST landed in main-8221216, and enabling this on an older image +# would deploy a pod that binds loopback and never becomes reachable. +# ClusterIP only — no ingress, same reason the API's is disabled. +mcp: + enabled: true + config: sbomNexusUrl: "http://sbom-nexus.sbom-nexus.svc.cluster.local:8010" # Reversible T04 read cutover; set back to `legacy` to roll back. @@ -33,6 +40,9 @@ sweep: # stale gitea-remote lineage. Re-enable only after the governed remote # reconciliation and registrar preflight are complete. enabled: false + # Present in the live release but previously missing here, so deploying from + # this file alone silently dropped it. Inert while enabled is false. + hostname: 239.62.205.92.host.secureserver.net hostname: 239.62.205.92.host.secureserver.net hostPath: /home/tegwick sshHostPath: /home/tegwick/.ssh