Cells: Plan production rollout for SSH routing for Git pull and push

Why

Epic &13532 delivers Topology Service-based SSH routing for Git pull and push across Cells. After validating the behavior on staging in #864 (closed), we need an explicit production rollout plan that minimizes risk, defines observability and rollback criteria, and clarifies ownership.

What

Create and align on a production rollout plan for Topology Service-based SSH routing for Git pull and push.

The plan should cover:

  • prerequisites and production readiness checks
  • rollout phases, sequencing, and target scope
  • feature flag or configuration changes used to control rollout
  • dashboards, metrics, logs, and alerts monitored during each phase
  • success criteria and observation windows
  • rollback triggers and a tested rollback procedure
  • handling of degraded or unavailable Topology Service and target-cell endpoints
  • validation of clone, fetch, pull, push, Git LFS, user-scoped, and repository-scoped SSH operations
  • communication, ownership, and escalation paths
  • post-rollout verification and follow-up cleanup

Definition of done

  • Stakeholders review and approve the rollout plan.
  • Preconditions and dependencies are documented and complete.
  • Rollout phases, owners, and timing are documented.
  • Monitoring and alerting are identified and verified.
  • Success and rollback criteria are explicit.
  • The rollback procedure is documented and validated.
  • Production verification steps are documented.
  • Follow-up issues are created for any gaps found during planning.

Related