CONTAINER STORAGE MIGRATION READINESS — Yenra, September 5, 2026
https://yenra.com/red-hat-container-native-storage/

INVENTORY
Application and service owners:
Source/target OpenShift, storage, operator, driver, and application versions:
Supported source/target combination and transfer method confirmed by:
Storage classes, provisioners, PVCs, access modes, capacities, usage:
Reclaim policies, binding mode, expansion, snapshots, encryption/key handling:
Block/file/object semantics, locking, permissions, ownership, metadata:
Dependencies: databases, registry, logging, credentials, other cluster services:
Current backups and tested recovery evidence:

TARGET REQUIREMENTS
Performance, capacity/growth/recovery headroom, topology and failure domains:
Operating responsibilities, support boundaries, monitoring and access:
Required data-loss interval and application recovery time:

REHEARSAL
Representative data and application-consistent copy method:
Files/objects/database records expected and verified:
Checksums where appropriate, ownership/permissions, reference consistency:
Restore into clean environment and application acceptance:
Measured complete recovery/cutover duration and unresolved gaps:

CUTOVER
Approved window and communications:
Write freeze / final synchronization / reconciliation method:
Validation and decision owner:
Point at which target becomes authoritative:
Rollback trigger and treatment of writes made after cutover:
Source retention under controlled access:

RETIREMENT
Acceptance evidence, retention obligations, and backup verification:
Source deletion approval; actual reclaim-policy effects checked:
Credential/access revocation and documentation update:

This worksheet is not a vendor-supported migration recipe. Confirm the exact
configuration and procedure before changing a live cluster. Do not assume that
editing a PVC or copying Kubernetes objects transfers existing application data.