Roadmap
All future items in this document are forward-looking statements, and subject to change. Please don't hesitate in providing us with feedback, may it be on these items or additional features, so we can consider and prioritize them accordingly.
2024
Quarter 1
- Better Documentation
- End-to-End Checksums
- User Quota
Quarter 2
- Longhorn 1.7 General Availability
- Temporary access credentials (Secure Token Service)
- More Interesting Metrics
- Automation/Scripting of Object Store/Bucket/User (Experimental Availability)
Quarter 3
Quarter 4
- Longhorn 1.8 (?)
- Multi-Site Active/Passive
- Automation/Scripting of Object Store/Bucket/User (General Availability)
2023
Quarter 1
- Expiration Lifecycle Management (unversioned)
- Object locks
- Object listing with prefixes/filters
- Telemetry
- UI: Object deletion/undeletion
Quarter 2
- Expiration Lifecycle Management (versioned)
- Access & Identity Management
- Metrics from backend
- UI: Object versioning
- Crash Consistency
Quarter 3
Quarter 4
- Longhorn 1.6 Experimental Availability
- Longhorn Controller
- Longhorn UI Integration
- Stable On-Disk format
- Metrics on UI
2022
Quarter 1
- Brainstorm process
Quarter 2
- Initial project setup
- First tests with RGW
- UI mockups
Quarter 3
- File-based backend
- Basic S3 operations support
- User management
- Helm charts
- Testing
- UI implementation
- Documentation
- Basic object management & versioning
- Bucket management
- Automation implementation
Quarter 4
- Object deletion/undeletion
- Multipart uploads
- Multipart copy
- ACL support
- UI: Basic object explorer
- Rancher Partner chart
Plan of direction
Features the team wants to develop but are currently not a top priority.
- Implement Storage classes
- Lambda Functions on S3
In scope
Features that aren't currently planned but the project would accept external contributions.
Out of scope
Features that aren't being considered unless core assumptions change.
- None at the moment
Info
Please note that this roadmap is an evergreen document and will most certainly evolve as we continue to learn from our users.