chore(deploy): enable central MCP on main-8221216
This commit is contained in:
parent
82212165f9
commit
0fc955989a
1 changed files with 11 additions and 1 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue