Skip to content

Added volume migration - #177

Merged
noctarius merged 1 commit into
mainfrom
volume-migration
Jul 30, 2026
Merged

Added volume migration#177
noctarius merged 1 commit into
mainfrom
volume-migration

Conversation

@noctarius

Copy link
Copy Markdown
Collaborator

Added initial documentation for volume migration.

@noctarius noctarius self-assigned this Jul 30, 2026
Copilot AI review requested due to automatic review settings July 30, 2026 08:39

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new maintenance-operations documentation page describing how the Simplyblock Operator performs live volume migration and how users can trigger/observe it.

Changes:

  • Documented volume migration concepts and configuration (volumeMigrationSettings and volumeAutoPlacement).
  • Added step-by-step procedures for manual migrations, aborting, and PVC pinning-based migrations.
  • Documented drain/removal-related migrations, pinned-volume behavior, post-migration data realignment, and relevant events.
Comments suppressed due to low confidence (2)

docs/maintenance-operations/volume-migration.md:271

  • Grammar: “can also be trigger immediately” should be “can also be triggered immediately”.
successful realignment. However, a realignment can also be trigger immediately by annotating the

docs/maintenance-operations/volume-migration.md:290

  • Spelling consistency: this page uses both “canceled” and “cancelled” when describing aborting migrations. Consider using one spelling throughout (e.g., “canceled” to match the earlier section).
| `MigrationAborted`          | The migration was cancelled via `spec.abort`.                          |

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


There are also automated processes that create a `VolumeMigration` resource, for example, setting the
`simplyblock.io/selected-storage-node` annotation on an already-bound PVC. This will effectively migrate the pinned
volume to a new storage node UUID. The operator create a `VolumeMigration` on the user's behalf, as part of moving the
Comment on lines +253 to +254
Volumes whose backing logical volume has no corresponding PV (for example, a volume created outside
Kubernetes) also block removal, with an `UnmanagedVolumeBlocking` event, until they are resolved.
@github-actions

Copy link
Copy Markdown
Contributor

🤖: Deployment available as https://docstest.simplyblock.io/volume-migration

@noctarius
noctarius merged commit b6fb8f8 into main Jul 30, 2026
4 checks passed
@noctarius
noctarius deleted the volume-migration branch July 30, 2026 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants