Velero watch for Schedule on multiple namespaces

[julien-sugg]

Greetings,

I am facing some issues with the Schedule custom resources sitting in a namespace other than the one containing the Velero controller (namespace velero).

In my current setup, only the Schedule objects within the velero namespace are properly backed-up while the others (e.g. in namespace myapp-development) are left untouched with no status information.

Did I miss anything in the official documentation ? Is it possible to instruct the controller to watch for custom resources over multiple namespaces in order to achieve decentralized backup configuration ?

My current setup is the following:

1. Velero 1.6.0 installed using the official helm chart (v2.17.1@https://vmware-tanzu.github.io/helm-charts)
2. GCP Plugin velero-plugin-for-gcp 1.2.0
3. CSI Plugin velero-plugin-for-csi 0.1.2
4. Kubernetes version: 1.19.9 (GKE v1.19.9-gke.100)

Additional information:

working schedules info from the velero namespace, where the controller is also deployed

$ v schedule get -n velero
NAME                                  STATUS    CREATED                          SCHEDULE       BACKUP TTL   LAST BACKUP   SELECTOR
letsencrypt-certificates-bi-monthly   Enabled   2021-04-19 17:13:25 +0200 CEST   0 1 */15 * *   2922h0m0s    21h ago       <none>
pvc-hot                               Enabled   2021-04-19 17:13:25 +0200 CEST   */30 * * * *   2h0m0s       18m ago       <none>

NON-working schedules info from the development namespace

$ v schedule get -n development
NAME            STATUS   CREATED                          SCHEDULE       BACKUP TTL   LAST BACKUP   SELECTOR
test-schedule   New      2021-04-16 10:37:07 +0200 CEST   */30 * * * *   2h0m0s       n/a           <none>

Velero controller logs

$ k logs <myVeleroPod> | grep -i test-schedule
# no output when `grep`ing on this particular schedule

Please let me know if more configuration details or any other info are required.

Thanks in advance for your feedback.