363c2692a1
The Velero deployment did not have a way of exposing the namespace it was installed in to the API client. This is a problem for plugins that need to query for resources in that namespaces, such as the restic restore process that needs to find PodVolume(Backup|Restore)s. While the Velero client is consulted for a configured namespace, this cannot be set in the server pod since there is no valid home directory in which to place it. This change provides the namespace to the deployment via the downward API, and updates the API client factory to use the VELERO_NAMESPACE before looking at the config file, so that any plugins using the client will look at the appropriate namespace. Fixes #1743 Signed-off-by: Nolan Brubaker <brubakern@vmware.com> |
||
|---|---|---|
| .. | ||
| crd.go | ||
| daemonset.go | ||
| daemonset_test.go | ||
| deployment.go | ||
| deployment_test.go | ||
| doc.go | ||
| install.go | ||
| resources.go | ||
| resources_test.go | ||