-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Issues: vmware-tanzu/velero
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Provide S3 plugin that aims to support any S3 compatible object storage.
#8265
opened Oct 4, 2024 by
kaovilai
Velero 1.14.1 & aws plugin 1.10.1: api error SignatureDoesNotMatch
#8264
opened Oct 4, 2024 by
amrap030
Fatal: unable to open config file results in PartiallyFailed Backup
#8263
opened Oct 4, 2024 by
amrap030
Scheduled config from helm chart config fails backup with ValidationError
#8262
opened Oct 3, 2024 by
darnone
DataUpload Fails on Kubernetes 1.29 due to changed VSC SourceVolumeMode
#8259
opened Oct 3, 2024 by
msfrucht
RFE: Extend Volume Policy criteria to include label selector
1.16-candidate
#8256
opened Sep 30, 2024 by
shubham-pampattiwar
(GCP): Add an ability to change the destination AZ while restoring.
Area/Cloud/GCP
Help wanted
#8247
opened Sep 25, 2024 by
tuusberg
DataMover - distribute datadownload evenly across nodes if possible
1.16-candidate
area/datamover
backlog
#8242
opened Sep 24, 2024 by
Lyndon-Li
Velero 1.14.1 & aws plugin 1.10.1: using wrong role with IRSA
Area/Cloud/AWS
Needs investigation
#8240
opened Sep 23, 2024 by
lrstanley
Don't run maintenance on repo in the backup storage when BSL is ReadOnly
1.16-candidate
backup-repo/Maintenance
repository
#8238
opened Sep 23, 2024 by
maciej-p
velero skipping volume backups if connected to S3 backblaze
Area/CSI
Related to Container Storage Interface support
Needs info
Waiting for information
#8235
opened Sep 21, 2024 by
mehransaeed7810
Terminating namespace polling for each resource during restore
Restore
#8234
opened Sep 20, 2024 by
anshulahuja98
Micro-service datamover backup recovery issue
area/datamover
limitation
#8231
opened Sep 19, 2024 by
blackpiglet
File system restore cannot work in PSA enabled Kubernetes cluster
1.16-candidate
downstream-integration
The issue originated from downstream integration
PodVolume
#8229
opened Sep 19, 2024 by
ywk253100
Data mover --- node selection by storage class
1.16-candidate
area/datamover
backlog
kind/requirement
#8223
opened Sep 18, 2024 by
Lyndon-Li
Velero command not throwing and error when schedule hasn't been correctly defined
Area/CLI
related to the command-line interface
#8214
opened Sep 12, 2024 by
jeremyvdveen
time="2024-09-12T09:56:32Z" 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:567".
Needs info
Waiting for information
#8212
opened Sep 12, 2024 by
Srija-ravi
Allow resource status restore in a more granular way
1.16-candidate
Needs Design
#8204
opened Sep 10, 2024 by
shubham-pampattiwar
Velero not automatically detecting aws s3 region for buckets anymore after updating to v1.14.1
Area/Cloud/AWS
#8200
opened Sep 10, 2024 by
thomaspeitz
Data mover Micro Service -- support NFS/local-volume/host-path volume as target BSL
1.16-candidate
area/datamover
backlog
#8190
opened Sep 6, 2024 by
Lyndon-Li
Restore Data Movement Node Selection
1.16-candidate
area/datamover
kind/requirement
#8186
opened Sep 4, 2024 by
MuriloCouceiro
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.