Homelab Wave Migration (Compose → k3s)

Migrate Docker Compose services to k3s by executing a phased wave migration that includes preflight checks, automated Helm chart deployment, Traefik network policy configuration, and stateful data migration.

Move Docker volumes to k3s Persistent Volume Claims using a dedicated stateful data migration workflow, ensuring data integrity for stateful applications like Vaultwarden during the transition.

Yes, you need Terraform and SOPS to deploy homelab services on k3s, as validated preflight checks require these tools to ensure environment readiness and secure secret management before migration.

The best way to execute a wave migration for stateful homelab services is grouping them into risk-based waves (A, B, C, D), running health checks, and utilizing the provided cutover and rollback procedures.

Configure Traefik ingress network policies when moving to k3s through automated network policy management, which sets up essential routing rules as part of the Helm chart deployment process.

Yes, you can rollback a homelab service after switching from Docker Compose to k3s, because the migration process includes specific cutover and rollback procedures to ensure minimal downtime.