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
Preserve original volumes during Longhorn V2 cutover #6005
Keep each original Longhorn V1 volume recoverable while its application moves to V2.
Motivation
Most existing application claims still have a reclaim policy that deletes their storage with the claim. A reviewed cutover needs to keep the original backend so the application can recover if its replacement fails.
Proposed Solution
Provide a separately confirmed operation for one bound V1 application claim. Bind approval to the original claim, persistent volume and Longhorn backend. Change only the reclaim policy, then read all three original identities back.
Acceptance Criteria
The operation requires the first protected run from current main and confirms the exact original storage identities.
Changed or unbound objects, backup scratch resources and other engines are rejected.
An interrupted response is observed without repeating the write.
The protected cutover verifies the original backend survives claim replacement until its recovery and retirement checks pass.
Additional Context
This is a safeguard for the V2 migration. The platform-wide reclaim policy and scheduled audit remain tracked in #4441.
The 18 application-source retention operations completed successfully on their first attempts from reviewed main ead8141b0c4cc72b29b83e59dbac7f52a474bb97. A subsequent native, read-only check accounts for all 22 original Longhorn backends: the 18 application sources now have Retain, one released original remains retained, and three Email-owned sources remain held with their recovery owner. All 17 provider sources remain retained as previously verified.
The original PVC/PV/backend identity join is unchanged from the pre-operation receipt, apart from the expected PV resource-version changes. The native observer and 18 mismatched-identity refusal controls pass; the proof itself performs zero writes.
This completes the non-Email application source-protection phase. It does not establish V2 migration, restoration, historical coverage, source retirement or iSCSI-removal readiness; those acceptance gates remain open.
Activity
chore: agent-claim #6005 nonce=6c1a115770bfe6154451c77229e9c19e
chore: agent-claim #6005 nonce=eecfc08c01895fb0035cfe5271522412
devantler commentedon Nov 12, 2026
The 18 application-source retention operations completed successfully on their first attempts from reviewed main
ead8141b0c4cc72b29b83e59dbac7f52a474bb97. A subsequent native, read-only check accounts for all 22 original Longhorn backends: the 18 application sources now haveRetain, one released original remains retained, and three Email-owned sources remain held with their recovery owner. All 17 provider sources remain retained as previously verified.The original PVC/PV/backend identity join is unchanged from the pre-operation receipt, apart from the expected PV resource-version changes. The native observer and 18 mismatched-identity refusal controls pass; the proof itself performs zero writes.
This completes the non-Email application source-protection phase. It does not establish V2 migration, restoration, historical coverage, source retirement or iSCSI-removal readiness; those acceptance gates remain open.