Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support volume configuration, provisioning, etc. #8901

Merged
merged 1 commit into from
Aug 30, 2024

Conversation

smira
Copy link
Member

@smira smira commented Jun 12, 2024

This implements the first round of changes, replacing the volume backend
with the new implementation, while keeping most of the external
interfaces intact.

See #8367

@smira smira added this to the v1.8 milestone Jun 12, 2024
@smira smira force-pushed the feat/volume-config branch 2 times, most recently from e09fea0 to 4d3cd8c Compare July 9, 2024 17:12
@smira smira force-pushed the feat/volume-config branch 4 times, most recently from 2f1a743 to 3128bf7 Compare July 23, 2024 17:12
@smira smira force-pushed the feat/volume-config branch 3 times, most recently from d976f7f to e848274 Compare July 30, 2024 16:03
@smira smira force-pushed the feat/volume-config branch 2 times, most recently from 06023fd to 542a9b7 Compare August 15, 2024 12:47
@smira

This comment was marked as resolved.

@smira smira force-pushed the feat/volume-config branch 4 times, most recently from 7b1daf5 to 8dae199 Compare August 16, 2024 13:43
@smira smira force-pushed the feat/volume-config branch 8 times, most recently from 0bbbcf7 to 06e2be1 Compare August 20, 2024 17:41
@frezbo
Copy link
Member

frezbo commented Aug 29, 2024

will we have a use case where the old wipe option on upgrade is needed 🤔 ?

@smira
Copy link
Member Author

smira commented Aug 29, 2024

will we have a use case where the old wipe option on upgrade is needed 🤔 ?

I don't think so -- Omni runs with --preserve for more than a year now.

One could still wipe volumes via talosctl reset if needed independent of the upgrade process.

This implements the first round of changes, replacing the volume backend
with the new implementation, while keeping most of the external
interfaces intact.

See siderolabs#8367

Signed-off-by: Andrey Smirnov <[email protected]>
@smira
Copy link
Member Author

smira commented Aug 30, 2024

/m

@talos-bot talos-bot merged commit b453385 into siderolabs:main Aug 30, 2024
51 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants