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 how to migrate from existing self-hosted K8s deployment to using the Operator with no downtime #8031

Open
johnrk-zz opened this issue Aug 20, 2020 · 3 comments

Comments

@johnrk-zz
Copy link

johnrk-zz commented Aug 20, 2020

Exalate commented:

Towards this issue of enabling seamless migrations from self-hosted K8s deployments using the Helm Chart or Statefulsets using the Operator, we should document that process. More details on how users will do that is to be determined.

This is not part of the K8s Operator MVP.

Jira Issue: DOC-646

@github-actions
Copy link

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB docs!

@adamzr
Copy link

adamzr commented Jul 26, 2023

This is still an issue. We would like to migrate to the operator, but no upgrade path is documented.

@lucacri
Copy link

lucacri commented Oct 20, 2023

Same here, any updates?

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

No branches or pull requests

6 participants