You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
I am running a helm install with a configuration that has worked on the past but the backupstoragelocation and volumesnapshotlocation resources are not deployed. If I perform a helm template with my values files, the generate manifest are incorrect:
I expected the backupstoragelocation and volumesnapshotlocation resources to be created
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)
log shows:
time="2025-02-25T22:11:11Z" level=warning msg="Velero node agent not found; pod volume backups/restores will not work until it's created" logSource="pkg/cmd/server/server.go:650"
time="2025-02-25T22:11:11Z" level=warning msg="Failed to set default backup storage location at server start" backupStorageLocation=default error="backupstoragelocations.velero.io "default" not found" logSource="pkg/cmd/server/server.go:492"
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
I am deploying this with argocd cd but get the same result with helm even though I have a running install of velero in another cluster with helmfile Environment:
helm version (use helm version): v3.17.1
helm chart version and app version (use helm list -n <YOUR NAMESPACE>): chart:8.4.0, app: 1.15.2
Kubernetes version (use kubectl version): 1.30.9
Kubernetes installer & version: asdf 0.16.4
Cloud provider or hardware configuration: AWS EKS
OS (e.g. from /etc/os-release): Client Mac, AWS EKS node AWS optimized Linus 2
The text was updated successfully, but these errors were encountered:
What steps did you take and what happened:
I am running a helm install with a configuration that has worked on the past but the backupstoragelocation and volumesnapshotlocation resources are not deployed. If I perform a helm template with my values files, the generate manifest are incorrect:
generated manifest:
I you notice, the name is still default and the provider is empty.
values:
What did you expect to happen:
I expected the backupstoragelocation and volumesnapshotlocation resources to be created
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)
log shows:
time="2025-02-25T22:11:11Z" level=warning msg="Velero node agent not found; pod volume backups/restores will not work until it's created" logSource="pkg/cmd/server/server.go:650"
time="2025-02-25T22:11:11Z" level=warning msg="Failed to set default backup storage location at server start" backupStorageLocation=default error="backupstoragelocations.velero.io "default" not found" logSource="pkg/cmd/server/server.go:492"
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
I am deploying this with argocd cd but get the same result with helm even though I have a running install of velero in another cluster with helmfile
Environment:
helm version
): v3.17.1helm list -n <YOUR NAMESPACE>
): chart:8.4.0, app: 1.15.2kubectl version
): 1.30.9/etc/os-release
): Client Mac, AWS EKS node AWS optimized Linus 2The text was updated successfully, but these errors were encountered: