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

Multiple chart deployments #6

Open
KundaPanda opened this issue Oct 16, 2024 · 1 comment
Open

Multiple chart deployments #6

KundaPanda opened this issue Oct 16, 2024 · 1 comment

Comments

@KundaPanda
Copy link

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
Copy link
Contributor

sgielen commented Oct 16, 2024

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?

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

No branches or pull requests

2 participants