Ensure that a deployment using the Helm Chart or generic statefulsets can be migrated to the K8s Operator

[johnrk-zz]

For self-hosted customers that are interested in using the Operator, they may be using our Helm Chart or deploying with a statefulset in the interim. We need to make migrating to the Operator seamless with no downtime.

Docs Issue: cockroachdb/docs#8031

This is not for the K8s Operator MVP.

[Wouter0100]

Honestly, this is something we'd love to use. Currently there seems to be no real way to migrate - especially as Helm seem not to be the preferred way of deployment anymore.

[adamzr]

Why is this closed? Is there a way to migrate now? Or will there never be a way to migrate?

[pseudomuto]

I was trying to clean up stale issues (anything < 2021). This one should definitely remain open. Thanks for pinging!

[rwrz]

Any update on this?
I'm on this right situation right now... the only way I can imagine to do is to turn my systems off, backup all the data, deploy new operator, then restore everything.
But, would be much better if we could just deploy the OPERATOR version as a second "region" cluster, wait the migration, then uninstall the helm version.
Any ideas?

[lucacri]

Same as for @rwrz , any update on this?

[banjoh]

Honestly, this is something we'd love to use. Currently there seems to be no real way to migrate - especially as Helm seem not to be the preferred way of deployment anymore.

@pseudomuto This is an interesting comment. Are you able to shed some light here? Is it a deficiency in Helm?

Disclaimer: I'm a triage maintainer of the helm project. We are working on Helm v4, so improvement suggestions are definitely welcome.