feat(mcp): run two replicas behind a PodDisruptionBudget #2022

Merged
sean merged 1 commit from feat/mcp-replicas into trunk 2026-08-10 11:12:09 +00:00
Owner

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.

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.
feat(mcp): run two replicas behind a PodDisruptionBudget
All checks were successful
pipeline/ci CI green @ b85e3604d95e
b85e3604d9
The pinned image now knows --mode=mcp, so the 0-replica introduction
step is over. Stateless streamable MCP needs no session affinity, so
two replicas with hostname anti-affinity and maxUnavailable 0 complete
the same availability shape the dashboard and release API have. The
structural guard now covers pipelines-mcp too.
sean merged commit b85e3604d9 into trunk 2026-08-10 11:12:09 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/pipelines!2022
No description provided.