You may encounter an issue where your Velero pods are crashing with messages like these:
This is due to a known issue in Velero where it is being passed an invalid or null value, which can be caused by an invalid or missing configuration of the backup location. More information is available upstream here:
https://github.com/vmware-tanzu/velero/issues/3220
To resolve this, check the configuration of the "velero" section of the "addons" block of your config.yaml for typos or any other misconfigurations.
If you're unable to identify the problem, revert any changes back to the default values, run "./konvoy deploy addons" again to try and get Velero deployed and running, then introduce new changes one at a time until you can narrow it down.
E0708 16:17:27.178350 1 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference"
This is due to a known issue in Velero where it is being passed an invalid or null value, which can be caused by an invalid or missing configuration of the backup location. More information is available upstream here:
https://github.com/vmware-tanzu/velero/issues/3220
To resolve this, check the configuration of the "velero" section of the "addons" block of your config.yaml for typos or any other misconfigurations.
If you're unable to identify the problem, revert any changes back to the default values, run "./konvoy deploy addons" again to try and get Velero deployed and running, then introduce new changes one at a time until you can narrow it down.