You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Prove temporary V2 storage and recovery before application cutover #5809
Enable the prepared temporary V2 storage targets and prove restore, persistence and reattachment before moving application data.
Motivation
The migration must establish a working V2 data path and verified recovery before replacing any existing application storage. The temporary-storage route also needs its own activation checks; the earlier filesystem-staging procedure cannot authorize it.
Proposed Solution
Resume the existing private activation and canary work under #5582 on the current reviewed foundation. Provide separately confirmed, protected operations for the prepared temporary targets and a disposable V1-to-V2 restore proof. Keep activation off until its native prerequisites pass, and retain journals and uncertain resources for explicit recovery.
Acceptance Criteria
Bind every selected temporary target to its reviewed identity, encrypted raw storage, native memory reservation, capacity budget and owned preparation proof before registration.
Enable V2 through the declarative owner only after the required independent storage targets and host prerequisites are proven.
Verify actual V2 engine, frontend and required replica health.
Restore a known disposable V1 payload onto V2, compare its content, and verify persistence after reattachment on separate qualified workers.
Prove cleanup of only the canary's owned scratch resources, including retained storage; uncertain outcomes preserve their journal and resources without replay.
Exercise both disabled and enabled admission states and interrupted recovery paths in tests.
Record actual protected production acceptance before closing; CI or a queued PR alone is insufficient.
Alternatives Considered
Changing a StorageClass does not migrate existing data. Reusing filesystem-staging authorization for raw targets would not prove the new route. Application cutover remains separate work under #5582.
Additional Context
Priority: this is on the critical path to the maintainer-requested V2 migration. It resumes already-started work; it does not add an unrelated feature.
Native prerequisites are tracked in #5791 and #5787. Baseline and interruption recovery remain governed by #5665 and the existing strict current-source policy.
#5584 - chore(storage): prepare worker capacity for Longhorn V2 [merged] #5470 - feat(backup): prove recovery from the independent snapshot store [merged] #5726 - feat(storage): add the fixed Longhorn V2 migration worker [closed]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Nov 3, 2026
🔗 Related PRs
#5584 - chore(storage): prepare worker capacity for Longhorn V2 [merged]
#5470 - feat(backup): prove recovery from the independent snapshot store [merged]
#5726 - feat(storage): add the fixed Longhorn V2 migration worker [closed]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
chore: agent-claim #5809 nonce=c4610cca26d7a64d9a20dd31a231d049
chore: agent-claim #5809 nonce=35c1135792f283c4b4ca8592c67dd80b
chore: agent-claim #5809 nonce=67a84c73af9c4a41130783f4bfc36350
chore: agent-claim #5809 nonce=34b3108dbc3d991fc42212328182e18a
chore: agent-claim #5809 nonce=86daea9f52673e2a03895acab24f5943
1 remaining item
chore: agent-claim #5809 nonce=3dfe3f29cfc25074b9613e71bb89ccc2
chore: agent-claim #5809 nonce=664a5d943882088f9ae9dbce96c6c4cc
chore: agent-claim #5809 nonce=1110d114a8a37f336d5004869bc51c93
chore: agent-claim #5809 nonce=2a9743ab85f0d55a850664bfe4aa6007
chore: agent-claim #5809 nonce=8b43d6a124ccc915f8c1844abe839e4c
chore: agent-claim #5809 nonce=2779b1e39b99d793d1e18cdb960c23f9
chore: agent-claim #5809 nonce=8fa7cbbe40d2ae449b052de73fddffe2
chore: agent-claim #5809 nonce=94a25356cdb072f181b61e1c6d2b15ae
chore: agent-claim #5809 nonce=677e1ffdb13d07fc9334d02740193e95
chore: agent-claim #5809 nonce=cd784def2596cedf4374f87e6b1deb7f
chore: agent-claim #5809 nonce=471f0aea93af4cd2c5387f24bfa6467c
chore: agent-claim #5809 nonce=01215ca8a10b6bd2f5a619f2a5aae373
chore: agent-claim #5809 nonce=3a4da6f32cff8579e388c680c3dabac8
chore: agent-claim #5809 nonce=a487082bd99634f416c90300c6bcfccf