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

document upgrade/downgrade #85

Open
worldsoup opened this issue May 18, 2023 · 3 comments
Open

document upgrade/downgrade #85

worldsoup opened this issue May 18, 2023 · 3 comments
Assignees

Comments

@worldsoup
Copy link
Contributor

inspired by: https://discord.com/channels/981533931486724126/1108708939744424048/1108711816684650497

CC @Pothulapati

@romange
Copy link
Contributor

romange commented Oct 9, 2023

@Pothulapati do we need to document this?

@Pothulapati
Copy link
Contributor

TBH, Even if the underlying image is docker, The actual abstraction matters more. In k8s, The upgrade/downgrade procedure is an update on the resource and we use the underlying snapshot or replication feature to make sure there is no data loss. (Documentation for snapshotting is incoming)

We can have a page on how to update your isntances but it essentially mentions that as same as other k8s resources, and to make sure there is no data loss to have snapshotting or replication set before. wdyt?

@romange
Copy link
Contributor

romange commented Oct 9, 2023

I think we should document processes that are unique to dragonfly. I do not think we need a dedicated page for upgrade procedure for k8s, maybe have a paragraph in the documentation about snapshotting to show how dragonfly version can be changed using the usual k8s command.

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

No branches or pull requests

3 participants