JenTing

Related to #269

In my perspective, it should be fixed in Velero core, ref to https://github.com/vmware-tanzu/velero/issues/1980. After that, every time when a new Schedule CR setting, Velero won't trigger a new backup immediately...

> Thank you @jenting, I see the referenced issue is nearly 2 years old. Hopefully it gets resolved soon. I saw it be scheduled to `v1.8.0`, hope it'll be fixed...

> In other words, the identified helm hook does not make sense for schedule resources. Why is that being done in the first place? The purpose we want to achieve...

Thanks for the suggestion and we did consider separate the chart before. But I can't remember the main reason on why we did not choose this solution before. Anyway, for...

Sure, we did have that before but after implementing the upgrade CRD job we remove the setting. We could add it back.

> It should be possible to workaround this issue by setting `upgradeCRDs: false` to avoid creation of the `Job` in step 2 but I am not sure what problems this...

I had the OR scenario before is that if I want to monitor lots of certificates within one cert-exporter Deployment, some certificates are find and filter by label, the others...

The kucero also have this issue.

@pavb74 Would you mind amending the last 3 commits and adding the signed-off-by? Then I think it's good to be merged.