# 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.py`** fills them for a deploy profile (`deploy/crucible-kab-dev.yaml`) into `build/`, ready for `kubectl diff -k` and `kubectl apply -k`. - **`secretnames.yaml` is left out of the build,** so a deploy can't wipe a Secret created by hand. - **`namespace.yaml` is left out too.** `agents` and `mcp-servers` are shared with other agents, so the build must neither relabel them nor let `kubectl delete -k` remove 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.