Collecting Requirements/Ideas/Features for v1.11.0

[OrlinVasilev]

Hello Community!

Velero v1.10 is coming within the next weeks, and before we start working on v1.11, we’d love to brainstorm with you on ideas and requirements for the feature list of this next release!

We will be super grateful if you submit your ideas and feature request along side with your willingness to work on them, which will help tremendously the project and community!

Please review what we have already laid out in the v1.11 roadmap and share your thoughts/ideas/requirements/feedback here so we can all work together on building out the next version of Velero.

Orlix
Velero Community Manager

[weshayutin]

@OrlinVasilev Thank you so much for starting this thread. It's very helpful to be able to plan for an upcoming release of velero.

Designs:

1. Item action progress monitoring design
2. BackupItemAction v2 design
3. RestoreItemAction v2 design
4. VolumeSnapshotter v2 API design

GH Issues related to Plugin v2 API changes:

• Implement new plugin v2 APIs for VolumeSnapshotter
• Implement new plugin v2 APIs for BackupItemAction
• Implement new plugin v2 APIs for RestoreItemAction

GH Issues related to the implementation of BR monitoring:

• Implement backup monitoring for backupItemAction
• Implement restore monitoring for restoreItemAction

GH Issues related to B/R phases:

• New Backup phases:
• New Restore phases
• Defer uploading backup.json
• Implement -itemoperations.json.gz file
• Implement -itemoperations.json.gz file restart logic
• Change recon logic to ignore B/R that are not completed

GH Issue (to be created ) describing holistic changes for timeouts:

• Discover timeouts through out the velero codebase
  • Understand the existing related parameters
  • Identify hard coded timeouts
  • Propose a logical mapping for remaining hardcoded timeouts