search

skybitsnl / backsnap

Kubernetes backup operator - off-site point-in-time backups with history
MIT License
28 stars 2 forks source link

Multiple chart deployments #6

Open KundaPanda opened 1 month ago

KundaPanda commented 1 month ago

Hello,

I am trying to deploy backsnap using the Helm chart twice, with each deployment having a different s3 endpoint and schedule. The issue is, that the chart includes CRDs with no way of disabling them, creating conflicts during apply/install.

Is there another preferred way of doing this (backing up to multiple s3 servers and with different schedules)?

If not, could you please either allow disabling the CRDs in values.yaml or rename the crd directory to crds (according to https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#method-1-let-helm-do-it-for-you)?

sgielen commented 1 month ago

Hi @KundaPanda!

Different schedules is already supported (you can set a schedule on a namespace or on a PVC), but indeed, different S3 endpoints is not. I would indeed advise to deploy two operators for that, i.e. deploy the Helm chart twice as you are doing.

I hadn't realized that the CRD would be causing issues with that. I'll read into the CRD best practices and fix up the chart accordingly as soon as I have time. Or, if you want, you're welcome to create a PR for it?