-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Feature]: Add support for Velero Schedules #350
Labels
enhancement
New feature or request
Comments
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 5, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Oct 17, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
kosmoz
added a commit
that referenced
this issue
Nov 8, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
pmig
pushed a commit
that referenced
this issue
Nov 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each CRD spec should have an optional
backups
property that contains data necessary to create aBackupStorageLocation
andSchedule
as defined by Velero. The schedule and ttl should be customizable with a sensible default value (backup once per day, ttl 7 days).For the time being, only S3 compatible storage will be supported.
The text was updated successfully, but these errors were encountered: