Files
cp1-agents/docs/platform-issues/mcp-gateway-default-tenant/README.md
Jonathan Boniface 416c66ced4
All checks were successful
check agents / check (push) Successful in 10s
Add CP1 Discovery agents in both patterns
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight
individual declarative agents (individual-agents/), with their KAB workflow
exports. Shared check, render and import scripts, the alz-discovery-sample
MCP server, the crucible-kab-dev deploy profile, deployment docs, platform
issue reports and the source material. Agent steps time out at 20 minutes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 18:25:57 +00:00

1013 B

MCP gateway: registering a server fails with a 500

Open since 2026-10-29, on crucible-kab-dev-aks. The full analysis is in report-2026-10-29.md.

File What it is Applied?
report-2026-10-29.md Root cause, code path, evidence and options —
kyn-agent-builder-mcp-gateway.deployment.yaml The gateway Deployment, cleaned up (DEFAULT_TENANT_ID=default, no TENANT_ID); no different from the live one No change needed
secrets.yaml Secret kab-tenant-id. It holds KAB's default tenant id, which is an identifier and not a credential. No
mcp-gateway-link-default-tenant.job.yaml A one-off Job that maps KAB's default tenant to the gateway tenant default No. It changes core-components, so it needs approval.

The Job fixes registration only while the default tenant is selected. In the gateway's single tenancy mode, tenants that KAB provisions later still fail. See option C in the report.