-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add backups with Kubernetes CronJobs #1
Comments
Cockroachdb 20.2 was released, which ships their previously only in the enterprise version backup and restore functionality that is directly built into it. It probably makes sense to use that well-hardened feature rather than something somewhat home-brewed. |
I finally looked at these docs. |
Awesome! |
Actually I read https://www.cockroachlabs.com/docs/v20.2/take-full-and-incremental-backups#automated-full-backups differently |
Ah, seems like I missed that detail. Honestly, I'm not sure I want to have that part of the CRD in the end. 🤔 In the end, the question is how much overlap there should be between scheduling and scaling and actual database operation. |
Yeah I agree, especially with this feature built into CDB like this I don't think it makes sense for this to be part of the CRD. I don't see what kube-cockroachdb would even do here. |
On one of my projects I've created a Kubernetes CronJob to automatically backup databases to S3-compatible object storage (with minio).
Going forward this should become a part of kube-cockroachdb.
We need to parameterize a few things, like schedule and secrets, to make it really work for most people.
Please add a reaction to indicate you want this feature and leave a comment for other requirements around this feature.
The text was updated successfully, but these errors were encountered: