-
Notifications
You must be signed in to change notification settings - Fork 363
Issues: vmware-tanzu/helm-charts
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
Add PDB on helm chart
good first issue
Good for newcomers
velero
#626
opened Nov 8, 2024 by
DanielCastronovo
Tolerations for DataUpload pods
good first issue
Good for newcomers
velero
#620
opened Sep 27, 2024 by
ehemmerlin
Failed to set default backup storage location at server start
velero
#619
opened Sep 17, 2024 by
maxwassiljew
Velero Service Monitor is not discovered by Prometheus Operator (kube-prometheus -stack)
velero
#609
opened Jul 24, 2024 by
darnone
Velero backup is failing partially with pod volumes have no associated PVCs errors
velero
#607
opened Jul 23, 2024 by
rkunalan
Separation of service accounts for Velero deployment and node-agent
velero
#606
opened Jul 22, 2024 by
ugur99
Add an environment variable for a custom token with an uppercase name
#600
opened Jul 16, 2024 by
srodenhuis
Setting configuration.logLevel prevents default backup storage to be found
#597
opened Jun 28, 2024 by
SCHrodrigo
failed to provision volume with StorageClass claim Selector is not supported
#588
opened Jun 17, 2024 by
StellaV
After update velero-plugin-for-aws - backup status finalizing never completed
velero
#580
opened May 21, 2024 by
M-A-X-I-M
Can I use this chart to create all my schedule backups?
question
Further information is requested
velero
#567
opened Apr 16, 2024 by
red8888
Add support to Tolerations & nodeSelect to the restore phase with velero/velero-restore-helper
velero
#563
opened Apr 5, 2024 by
didier-segura
Previous Next
ProTip!
Follow long discussions with comments:>50.