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

Docs: Warn that switching storage strategies is not supported #23003

Open
AObuchow opened this issue Jun 7, 2024 · 2 comments
Open

Docs: Warn that switching storage strategies is not supported #23003

AObuchow opened this issue Jun 7, 2024 · 2 comments
Assignees
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed.

Comments

@AObuchow
Copy link

AObuchow commented Jun 7, 2024

Is your task related to a problem? Please describe

Switching between persistent storage strategies (per-user -> per-workspace, or vice versa) is not supported by Che and can lead to orphaned data. The only storage strategy switching that's supported is ephemeral (non-persistent) -> per-user OR per-workspace.

Describe the solution you'd like

We should mention this limitation in the configuring storage strategy page so that users don't accidentally orphan their data.

Describe alternatives you've considered

No response

Additional context

This is related to #23002, as users might encounter a pvc multi-attach error when using the per-user storage strategy and then decide to switch to the per-user storage strategy, resulting in data loss.

@AObuchow AObuchow added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Jun 7, 2024
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jun 7, 2024
@AObuchow AObuchow added area/doc Issues related to documentation and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jun 7, 2024
@AObuchow
Copy link
Author

AObuchow commented Jun 7, 2024

@deerskindoll I'll gladly help you make this docs update :)

@deerskindoll deerskindoll self-assigned this Jun 12, 2024
@che-bot
Copy link
Contributor

che-bot commented Dec 9, 2024

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 9, 2024
@che-bot che-bot closed this as completed Dec 16, 2024
@deerskindoll deerskindoll reopened this Dec 16, 2024
@che-bot che-bot closed this as completed Dec 23, 2024
@deerskindoll deerskindoll reopened this Jan 2, 2025
@deerskindoll deerskindoll removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

No branches or pull requests

3 participants