All checks were successful
check agents / check (push) Successful in 10s
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>
1.2 KiB
1.2 KiB
0011. Deploy with kustomize from filled-in placeholders; keys stay in Secrets
| Status | Accepted |
| Date | 2026-10-29 |
| Decided by | Product owner (CP1) |
| Requirements changed | None in the stories; the deploy path differs from cp4-agents, which leaves deployment to Kyndryl's agent CI |
Decision
- Placeholders stay: each
kubernetes/folder keeps Kyndryl CI's placeholders, as cp4-agents does. scripts/render_k8s.pyfills them for a deploy profile (deploy/crucible-kab-dev.yaml) intobuild/, ready forkubectl diff -kandkubectl apply -k.secretnames.yamlis left out of the build, so a deploy can't wipe a Secret created by hand.namespace.yamlis left out too.agentsandmcp-serversare shared with other agents, so the build must neither relabel them nor letkubectl delete -kremove them.- The MCP server's inline registration-key placeholder is removed, so that key is read from its Secret.
Consequences
Keys are created with kubectl create secret and never appear in a file in the repository. The cluster has no agent-platform-connections ConfigMap, so the profile names the LiteLLM and MCP gateways in the agent's ConfigMap.