feat(mcp): run two replicas behind a PodDisruptionBudget #2022
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/mcp-replicas"
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?
Second step of the two-step introduction from PR 2021: v0.1.625 pinned the first image that knows --mode=mcp, so the Deployment leaves its 0-replica seed state. Two replicas, hostname anti-affinity, maxUnavailable 0, PDB minAvailable 1 — the same availability shape as the dashboard and release API. The go-htmx structural guard now covers pipelines-mcp.