fix(delivery): give the runtime image set a new Target identity for MCP #2023
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/mcp-runtime-target-v2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Target specs are CEL-immutable (self == oldSelf). PR 2021 tried to add pipelines-mcp to the existing runtime Target in place; the apiserver rejected every sync and ArgoCD SSA dry-run swallowed the rejection as Synced (the false-green failure mode) — v0.1.625 honestly patched only the three registered deployments.
This restores pipelines-runtime-development to its true three-deployment identity (kept forever: old Deployments reference it), and adds pipelines-runtime-development-v2 with all four deployments plus the selecting policy. The old policy is removed so the release item keeps exactly one selecting delivery policy. Guards repointed to -v2.
After merge, one release deploys the v2 set: the image adapter pins pipelines-mcp and the source sync raises it to 2 replicas.