---
# System prepended metadata

title: Roadmap wes/pradeep

---

# Velero Community Roadmap

Velero open source project will focus on providing generic, platform agnostic, application
agnostic, crash-consistent data protection features and be an enabler for enterprise data
protection solutions focusing on business continuity, disaster recovery, migration, data backup &
recovery use cases. Velero will provide generic capabilities and features catering to various
application types e.g. databases (relational, NoSQL), web applications, system application
(Harbor, Load balancers). Velero would not develop features for specific applications however
implement a good foundation of capabilities to backup / restore various applications categories

### Velero will not focus:
- Application specific and cover specific application


### Velero open source project roadmap for CY25 and beyond will focus below themes:
- Improve backup / restore performance supporting disaster recovery goals, e.g. RPO
(Recovery Point Objective) and RTO (Recovery Time Objective)
- Improve the security, performance and scalability
- Keep up with K8S distributions
- Efficient change block tracking (adopt K8S capability)
- Expand storage support for backups
- Multi-tier application crash-consistent backup
- Easy to troubleshoot issues
- Flexibility and Granular backup option (resources & data)

### The Velero open source project roadmap will include below features and capabilities for supporting above:



| Theme                           | Requirement              | Notes                  |
| --------------------------------|------------------------- | ---------------------- |
| **Performance and Scalability**   | | |
||||
||Reduce backup / restore time (multithreading, parallel execution)                    | Aims for lower RPO using recurring incremental backup.  <wes target parallel backup v1.18 |
||||
|| Improve time to copy data to/from BSL (Async upload, compression) | wes: local volume / nfs may help|
||||
|| Incremental Backup and Restore | wes- backup done , restore todo. break w/ cbt and b/r|
||||
|| Multiple destination for backup | Copy back up to multiple backup storage location. Probably documentation re: how to sync object. investigate |
|||| 
|| Bandwidth throttling support  |  Velero should support bandwidth throttling. Velero should work well in low bandwidth environment |
||||
|| Continuous backup for Persistent Volumes | Currently, Velero is not designed as a CDP product. There can be separate product/solution beyond Velero to address CDP|
||||
|**Security** |||
|| Cloud provider token (short term) support in place of cloud credentials | wes - mostly downstream at this point but will check|
||||
|| Integration to key stores (Hashi vault) | |
||||
|**Flexibility** |||
||Improve volume backup options (Granularity, policy to use backup method based on volume types, size)| wes: making good progress | 
||||
|| Enhance the plugin framework to better customize the workflow/behavior of velero, like filtering resources, controlling the order to backup/restore resources. | |
||||
|**Broader Coverage**| |Apps, Storage, K8S distribution|
||||
|| NFS as backup storage | Replicated seems interested in contributing on this, Wes: Tiger is looking into this one |
||||
||Backup / restore hooks library gitHub project||
||||
|| Windows Cluster support ||
||||
|**Multi-tier application backup** |||
||||
|| Volume Group Snapshots (subject to available as Beta in K8S) | wes: design 1.16, deliver in 1.17.  |
||||
|| Application consistency group ||
|**Partner enablement**  |||
||||


## Note:
Velero community roadmap represents a high level focus area for the project and not a
commitment from the Velero community to deliver these features in any specific order or in any
specified time frame. Roadmap items will be updated every six months. You are welcome to join
the Velero community meeting and bring your suggestions for adding or removing items to the
roadmap. Velero community members and maintainers may work on items beyond roadmap
items as well.


## Untriaged items to discuss for the RoadMap

* <wes> Restore a single file from a backup
    * https://kopia.io/docs/reference/command-line/common/snapshot-restore/#:~:text=Restore%20a%20directory,does%20not%20exist
    
* <wes> Add support for b/r of k8s operators