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

Possibility to edit timestamp format on scheduled backup #566

Closed
WRKT opened this issue Apr 11, 2024 · 4 comments
Closed

Possibility to edit timestamp format on scheduled backup #566

WRKT opened this issue Apr 11, 2024 · 4 comments
Labels
enhancement New feature or request velero

Comments

@WRKT
Copy link

WRKT commented Apr 11, 2024

Describe the problem/challenge you have
I am trying to implement a scheduled backup using Velero daily, so in the default <TIMESTAMP> format YYYYMMDDHHMMSS, I would like to be able to remove the HHMMSS.

Describe the solution you'd like
As example, the final format I want is backup-20240411 but not backup-20240411125400, so I would like to have the possibility to edit the timestamp format for my scheduled velero backup.

Environment:

  • helm version: v3.14.3
  • helm chart version: v6.0.0
  • velero version: v1.13.0
  • Kubernetes version: v1.29
  • Kubernetes installer & version: kind cluster
  • OS: Debian bookworm
@qiuming-best
Copy link
Collaborator

Sorry, I do not support it

@WRKT
Copy link
Author

WRKT commented Apr 22, 2024

Should I submit my ask to the velero repository directly ?

@jenting
Copy link
Collaborator

jenting commented May 11, 2024

Yes, please file a feature request issue to the velero repo, thanks.

@jenting jenting added enhancement New feature or request velero labels May 13, 2024
@WRKT
Copy link
Author

WRKT commented May 17, 2024

OK i will do it. Closing the issue.

@WRKT WRKT closed this as completed May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request velero
Projects
None yet
Development

No branches or pull requests

3 participants