Create a repeatable application migration and rollback runbook #11

New issue

Closed

opened 2026-08-29 00:22:50 -05:00 by portegumi · 1 comment

portegumi commented

2026-08-29 00:22:50 -05:00

Collaborator

Description

Establish a reusable migration pattern before creating a separate implementation issue for every existing Docker service. The runbook should support incremental, reversible cutovers and acknowledge that some services may remain outside Kubernetes.

Scope

Inventory an application's containers, dependencies, routes, credentials, and persistent paths.
Select or create PV/PVC mappings while preserving container paths where sensible.
Define backup and restore checks before cutover.
Define the sequence to stop the old workload, start the Kubernetes workload, validate it, switch routing, monitor it, and roll back.
Include ownership for decommissioning the old deployment only after an observation period.

Acceptance criteria

The runbook covers discovery, storage, secrets, deployment, validation, routing, observation, and rollback.
Existing Docker services remain running until their individual approved cutovers.
Data integrity and backup verification gates are included.
The runbook supports applications that remain outside Kubernetes.
The process is exercised and refined during the proof-of-concept migration.

Dependencies / blockers

Requires initial storage and networking conventions. It does not require UDS Core to be deployed.

## Description Establish a reusable migration pattern before creating a separate implementation issue for every existing Docker service. The runbook should support incremental, reversible cutovers and acknowledge that some services may remain outside Kubernetes. ## Scope - Inventory an application's containers, dependencies, routes, credentials, and persistent paths. - Select or create PV/PVC mappings while preserving container paths where sensible. - Define backup and restore checks before cutover. - Define the sequence to stop the old workload, start the Kubernetes workload, validate it, switch routing, monitor it, and roll back. - Include ownership for decommissioning the old deployment only after an observation period. ## Acceptance criteria - [ ] The runbook covers discovery, storage, secrets, deployment, validation, routing, observation, and rollback. - [ ] Existing Docker services remain running until their individual approved cutovers. - [ ] Data integrity and backup verification gates are included. - [ ] The runbook supports applications that remain outside Kubernetes. - [ ] The process is exercised and refined during the proof-of-concept migration. ## Dependencies / blockers Requires initial storage and networking conventions. It does not require UDS Core to be deployed.

portegumi added the

app-migration

documentation

labels

2026-08-29 00:22:50 -05:00