migrate

Migrate Kubernetes workstation pods and PVCs to new storage classes.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill migrate-kord96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/Kord96/kordinate/tree/main/agents/charon/skills/migrate
Command: npx skills add https://github.com/Kord96/kordinate --skill migrate-kord96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable, low-downtime procedure to relocate critical resources—workstation pods, persistent volume claims, and associated data—between clusters or storage backends while preserving credentials, service connectivity, and operational continuity.

Core Features & Use Cases

  • Workstation migration: Build and import a new workstation image, create a new PVC, copy data into the new volume, deploy the updated pod, and monitor a rolling update.
  • PVC migration / storage-class upgrade: Move PVC contents to a new storage class (for example migrating from local-path/RWO to Longhorn RWX) using an init job and migration pod.
  • Verification and cleanup: Run post-migration checks inside the new pod, update secrets, remove old ingress/configmaps/secrets/PVCs, and report final state.
  • Use case: Replace an RWO workstation PVC with a Longhorn RWX volume to enable multi-pod access while importing a rebuilt workstation image into a cluster without downtime.

Quick Start

Invoke the migrate workflow by running /migrate workstation to move a workstation or /migrate pvc <name> <namespace> to upgrade a PVC storage class.

Frequently Asked Questions about migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Kubernetes PVC contents to a new storage class like Longhorn?

Migrating PVC contents to Longhorn involves using an init job and migration pod to copy data into the new volume. This upgrades storage classes from local-path RWO to Longhorn RWX, enabling multi-pod access.

What is the best way to move a workstation pod to a new cluster without downtime?

Moving a workstation pod without downtime requires building and importing a new container image, creating a new PVC, copying data, and deploying the updated pod. You then monitor a controlled rolling update to ensure operational continuity.

Do I need SSH access to the control plane to relocate resources across clusters?

Yes, SSH-authenticated access to the control plane is required to relocate resources across clusters. This access enables kubectl operations, container image imports, verification checks, and explicit cleanup of old ingress, secrets, and PVCs.

How does PVC storage class migration handle cleanup of old Kubernetes resources?

PVC storage class migration handles cleanup by removing old ingress, configmaps, secrets, and PVCs after running post-migration verification checks inside the new pod. This explicit cleanup reports the final state and removes orphaned resources.

Can I upgrade a RWO workstation PVC to RWX multi-pod access?

Yes, you can upgrade an RWO workstation PVC to RWX multi-pod access by migrating to a Longhorn storage class. This process uses an init job and migration pod to transfer data while importing a rebuilt workstation image into the cluster.

What verification checks are needed after moving Kubernetes pods and persistent volumes?

After moving Kubernetes pods and persistent volumes, verification checks must be run inside the new pod to confirm successful data transfer and service connectivity. Updated secrets and final state reporting confirm the migration completed successfully.