This document provides a link to the Velero Project boards that serves as the up to date description of items that are in the release pipeline. The release boards have separate swim lanes based on prioritization. Most items are gathered from the community or include a feedback loop with the community. This should serve as a reference point for Velero users and contributors to understand where the project is heading, and help determine if a contribution could be conflicting with a longer term plan.
Discussion on the roadmap can take place in threads under Issues or in community meetings. Please open and comment on an issue if you want to provide suggestions, use cases, and feedback to an item in the roadmap. Please review the roadmap to avoid potential duplicated effort.
One of the most important aspects in any open source community is the concept of proposals. Large changes to the codebase and / or new features should be preceded by a proposal in our repo. For smaller enhancements, you can open an issue to track that initiative or feature request. We work with and rely on community feedback to focus our efforts to improve Velero and maintain a healthy roadmap.
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 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.
Last Updated: July 2021
The release roadmap is split into Core items that are required for the release and desired items that may slip the release.
The top priority of 1.7 is to increase the technical health of Velero and be more efficient with Velero developer time by streamlining the release process and automating and expanding the E2E test suite.
| Issue | Description |
|---|---|
| Streamline release process | |
| Automate the running of the E2E tests | |
| Convert pre-release manual tests to automated E2E tests | |
| 3493 | Carvel based installation (in addition to the existing velero install CLI). |
| 675 | Velero command to generate debugging information. Will integrate with Crashd - Crash Diagnostics |
| 3285 | Design doc for Velero plugin versioning |
| 1975 | IPV6 support |
| 3533 | Upload Progress Monitoring |
| 3500 | Use distroless containers as a base |
| Issue | Description |
|---|---|
| 3536 | Manifest for backup/restore |
| 2066 | CSI Snapshots GA |
| 3535 | Design doc for multiple cluster support |
| 2922 | Plugin timeouts |
| 3531 | Test plan for Velero |