Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BackupStorageLocation.velero.io "default" is invalid #631

Open
lsacco-nutreense opened this issue Nov 24, 2024 · 0 comments
Open

BackupStorageLocation.velero.io "default" is invalid #631

lsacco-nutreense opened this issue Nov 24, 2024 · 0 comments

Comments

@lsacco-nutreense
Copy link

What steps did you take and what happened:
A simply ran helm with my values file and get this output:

helm install velero vmware-tanzu/velero \
  --namespace velero \
  --create-namespace \
  --values velero-values-nonprod.yaml

Error: INSTALLATION FAILED: 2 errors occurred:
	* BackupStorageLocation.velero.io "default" is invalid: [spec.objectStorage.bucket: Required value, spec.provider: Required value]
	* VolumeSnapshotLocation.velero.io "default" is invalid: spec.provider: Required value

Here's what my values file looks like:

initContainers:
  - name: velero-plugin-for-aws
    image: velero/velero-plugin-for-aws:v1.11.0
    volumeMounts:
      - mountPath: /target
        name: plugins

configuration:
  backupStorageLocations:
    - name: default
      spec:
        provider: aws
        objectStorage:
          bucket: prod-eks-backup
        config:
          region: us-west-2
          profile: "default" # I've tried with and w/o this
  volumeSnapshotLocations:
    - name: default
      spec:
        provider: aws
        config:
          region: us-west-2
          profile: "default" # I've tried with and w/o this

serviceAccount:
  annotations:
    eks.amazonaws.com/role-arn: [arn-to-my-iam-role]
  create: true
  name: velero-server
credentials:
  useSecret: false

What did you expect to happen:

I wasn't expecting to see this error. I've tried multiple variations of my values.yaml and to no avail.

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.)

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • helm version (use helm version): version.BuildInfo{Version:"v3.15.3", GitCommit:"3bb50bbbdd9c946ba9989fbe4fb4104766302a64", GitTreeState:"clean", GoVersion:"go1.22.5"}
  • helm chart version and app version (use helm list -n <YOUR NAMESPACE>):
helm list -n velero
NAME  	NAMESPACE	REVISION	UPDATED                             	STATUS	CHART       	APP VERSION
velero	velero   	1       	2024-11-24 14:51:21.144488 -0800 PST	failed	velero-8.0.0	1.15.0
  • Kubernetes version (use kubectl version):v1.30.3
  • Kubernetes installer & version: brew
  • Cloud provider or hardware configuration: AWS EKS v1.230
  • OS (e.g. from /etc/os-release): AWS Linux 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant