Hi,
This means that no kubeconfig file can be found for the Velero client to use. Velero looks for a kubeconfig in the following locations:
- The path specified by the --kubeconfig flag, if any. ( --kubeconfig=/path/to/kubeconfig )
- The path specified by the $KUBECONFIG environment variable, if any (export KUBECONFIG=/path/to/kubeconfig)
- The default path ~/.kube/config
Hope this helps, and please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.