mirror of
https://github.com/vmware-tanzu/velero.git
synced 2025-12-23 06:15:21 +00:00
Proposed 1.7.0 roadmap (#3537)
Signed-off-by: Dave Smith-Uchida <dsmithuchida@vmware.com>
This commit is contained in:
committed by
GitHub
parent
a76cacd2ca
commit
afe47aeec8
66
ROADMAP.md
66
ROADMAP.md
@@ -15,23 +15,55 @@ We work with and rely on community feedback to focus our efforts to improve Vele
|
|||||||
The following table includes the current roadmap for Velero. If you have any questions or would like to contribute to Velero, please attend a [community meeting](https://velero.io/community/) to discuss with our team. If you don't know where to start, we are always looking for contributors that will help us reduce technical, automation, and documentation debt.
|
The following table includes the current roadmap for Velero. If you have any questions or would like to contribute to Velero, please attend a [community meeting](https://velero.io/community/) to discuss with our team. If you don't know where to start, we are always looking for contributors that will help us reduce technical, automation, and documentation debt.
|
||||||
Please take the timelines & dates as proposals and goals. Priorities and requirements change based on community feedback, roadblocks encountered, community contributions, etc. If you depend on a specific item, we encourage you to attend community meetings to get updated status information, or help us deliver that feature by contributing to Velero.
|
Please take the timelines & dates as proposals and goals. Priorities and requirements change based on community feedback, roadblocks encountered, community contributions, etc. If you depend on a specific item, we encourage you to attend community meetings to get updated status information, or help us deliver that feature by contributing to Velero.
|
||||||
|
|
||||||
`Last Updated: May 2020`
|
`Last Updated: March 2021`
|
||||||
|
|
||||||
|
#### 1.7.0 Roadmap
|
||||||
|
The release roadmap is split into Core items that are required for the release, desired items that may be removed from the
|
||||||
|
release and opportunistic items that will be added to the release if possible.
|
||||||
|
|
||||||
|
##### Core items
|
||||||
|
|
||||||
|
|Issue|Description|
|
||||||
|
|---|---|
|
||||||
|
|[3493](https://github.com/vmware-tanzu/velero/issues/3493)|[Carvel](https://github.com/vmware-tanzu/velero/issues/3493) based installation (in addition to the existing *velero install* CLI).|
|
||||||
|
|[3531](https://github.com/vmware-tanzu/velero/issues/3531)|Test plan for Velero|
|
||||||
|
|[675](https://github.com/vmware-tanzu/velero/issues/675)|Velero command to generate debugging information. Will integrate with [Crashd - Crash Diagnostics](https://github.com/vmware-tanzu/velero/issues/675)|
|
||||||
|
|[2066](https://github.com/vmware-tanzu/velero/issues/2066)|CSI Snapshots GA|
|
||||||
|
|[3285](https://github.com/vmware-tanzu/velero/issues/3285)|Support Velero plugin versioning|
|
||||||
|
|[1975](https://github.com/vmware-tanzu/velero/issues/1975)|IPV6 support|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
##### Desired items
|
||||||
|
|Issue|Description|
|
||||||
|
|---|---|
|
||||||
|
|[3533](https://github.com/vmware-tanzu/velero/issues/3533)|Upload Progress Monitoring|
|
||||||
|
|[2922](https://github.com/vmware-tanzu/velero/issues/2922)|Plugin timeouts|
|
||||||
|
|[3500](https://github.com/vmware-tanzu/velero/issues/3500)|Use distroless containers as a base|
|
||||||
|
|[3535](https://github.com/vmware-tanzu/velero/issues/3535)|Design doc for multiple cluster support|
|
||||||
|
|[3536](https://github.com/vmware-tanzu/velero/issues/3536)|Manifest for backup/restore|
|
||||||
|
|
||||||
|
##### Opportunistic items
|
||||||
|
|Issue|Description|
|
||||||
|
|---|---|
|
||||||
|
|Issues TBD|Controller migrations|
|
||||||
|
|
||||||
|
#### Long term roadmap items
|
||||||
|Theme|Description|Timeline|
|
|Theme|Description|Timeline|
|
||||||
|--|--|--|
|
|---|---|---|
|
||||||
|Restic Improvements|Introduce improvements in annotating resources for Restic backup|August 2020|
|
|Restic Improvements|Introduce improvements in annotating resources for Restic backup|TBD|
|
||||||
|Extensibility|Add restore hooks for enhanced recovery scenarios|August 2020|
|
|Extensibility|Add restore hooks for enhanced recovery scenarios|TBD|
|
||||||
|CSI|Continue improving the CSI snapshot capabilities and participate in the upstream K8s CSI community|Long running (dependent on CSI working group)|
|
|CSI|Continue improving the CSI snapshot capabilities and participate in the upstream K8s CSI community|1.7.0 + Long running (dependent on CSI working group)|
|
||||||
|Backup/Restore|Improvements to long-running copy operations from a performance and reliability standpoint|August 2020|
|
|Backup/Restore|Improvements to long-running copy operations from a performance and reliability standpoint|1.7.0|
|
||||||
|Quality/Reliability| Enable automated end-to-end testing |Dec 2020|
|
|Quality/Reliability| Enable automated end-to-end testing |1.6.0|
|
||||||
|UX|Improvements to install and configuration user experience|Dec 2020|
|
|UX|Improvements to install and configuration user experience|Dec 2020|
|
||||||
|Restic Improvements|Improve the use of Restic in Velero and offer stable support|Dec 2020|
|
|Restic Improvements|Improve the use of Restic in Velero and offer stable support|TBD|
|
||||||
|Perf & Scale|Introduce a scalable model by using a worker pod for each backup/restore operation and improve operations|Dec 2020|
|
|Perf & Scale|Introduce a scalable model by using a worker pod for each backup/restore operation and improve operations|1.8.0|
|
||||||
|Backup/Restore|Better backup and restore semantics for certain Kubernetes resources like stateful sets, operators|Dec 2020|
|
|Backup/Restore|Better backup and restore semantics for certain Kubernetes resources like stateful sets, operators|2.0|
|
||||||
|Security|Enable the use of custom credential providers|Dec 2020|
|
|Security|Enable the use of custom credential providers|1.6.0|
|
||||||
|Self-Service & Multitenancy|Reduce friction by enabling developers to backup their namespaces via self-service. Introduce a Velero multi-tenancy model, enabling owners of namespaces to backup and restore within their access scope|Mar 2021|
|
|Self-Service & Multitenancy|Reduce friction by enabling developers to backup their namespaces via self-service. Introduce a Velero multi-tenancy model, enabling owners of namespaces to backup and restore within their access scope|TBD|
|
||||||
|Backup/Restore|Cross availability zone or region backup and restore|Mar 2021|
|
|Backup/Restore|Cross availability zone or region backup and restore|TBD|
|
||||||
|Application Consistency|Offer blueprints for backing up and restoring popular applications|May 2021|
|
|Application Consistency|Offer blueprints for backing up and restoring popular applications|TBD|
|
||||||
|Backup/Restore|Data only backup and restore|May 2021|
|
|Backup/Restore|Data only backup and restore|TBD|
|
||||||
|Backup/Restore|Introduce the ability to overwrite existing objects during a restore|May 2021|
|
|Backup/Restore|Introduce the ability to overwrite existing objects during a restore|TBD|
|
||||||
|Backup/Restore|What-if dry run for backup and restore|May 2021|
|
|Backup/Restore|What-if dry run for backup and restore|1.7.0|
|
||||||
|
|||||||
Reference in New Issue
Block a user