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

Painful k3s/EKS upgrade path-- documentation request #17

Open
Hareet opened this issue Apr 10, 2024 · 1 comment
Open

Painful k3s/EKS upgrade path-- documentation request #17

Hareet opened this issue Apr 10, 2024 · 1 comment
Assignees

Comments

@Hareet
Copy link
Member

Hareet commented Apr 10, 2024

We need to publish documents on how to upgrade data in k3s / eks.

Let's start with the process that we keep re-inventing separately, moving the data to a docker server, following this repo's readme, editing compose templates to reflect k3s names. And for pvc use, we'll have to move the couchdb data files to the root directory of the disk, with no other files present.

We'll want docs for both single-node and clustered.

@Hareet
Copy link
Member Author

Hareet commented Apr 10, 2024

subPath, ftw!
If we set subPath to storage/medic-core/couchdb/data instead of its default data value, we don't have to move data up directories and potentially cause indexing to occur or other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant