[CNCF LFX Proposal] OpenEverest - Develop the Object Storage provider
- Dominant language
- JavaScript
- Stars
- 3.1k
- Forks
- 816
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 8
Description
### CNCF Project
OpenEverest
### Term
2026 Term 3 (Sep-Nov)
### Program Name
Develop the Object Storage provider
### Program Description
## Description
OpenEverest already manages databases on Kubernetes through its provider framework. This project extends that framework to object storage.
The gap is straightforward: users run OpenEverest on-premise or at the edge and need S3-compatible storage alongside their databases. Today they deploy MinIO or SeaweedFS manually, outside of OpenEverest, with no integration. This project fixes that by making object storage a first-class resource.
The mentee will implement an object storage provider within OpenEverest's existing v2 provider architecture. Starting with MinIO or SeaweedFS (or you name it), the provider will handle cluster lifecycle - deploy, scale, upgrade, configure replication and access policies—through the same UI, CLI, and API that users already use for databases. Buckets and users will be manageable from the OpenEverest dashboard, and object storage clusters will be usable as backup targets for managed databases.
The framework is already in place. The work is building the provider.
## Expected Outcomes:
• MinIO or SeaweedFS providers for OpenEverest v2
• Lifecycle management: deploy, configure, scale, upgrade
• Bucket and user management through OpenEverest UI/CLI/API
• Backup target integration with database clusters
• Tests and documentation
### Technologies
Go, Kubernetes, Helm, S3 API, MinIO, SeaweedFS
### Skills same as Technologies?
- [ ] Yes, the required skills are the same as the technologies listed above.
### Required/Desirable Skills
Go, Kubernetes, object storage, S3-compatible systems
### Mentors
Sergey Pronin | @spron-in | sp@solanica.io | sproninsolanica
Diogo Recharte | @recharte | diogo.recharte@solanica.io | drecharte
### Upstream Issue URL
https://github.com/openeverest/openeverest/issues/2255
### Application Prerequisites
- [x] Resume
- [x] Cover Letter
- [ ] School Enrollment Verification
- [ ] Participation Permission from school or employer
- [ ] Coding Challenge
- [ ] Custom Prerequisite (fill in details below)
### Coding Challenge URL
_No response_
### Custom Prerequisite Name
_No response_
### Custom Prerequisite Description
_No response_
### Custom Prerequisite — File Upload
- [ ] Yes — completion of this task requires the mentee to submit a file.
---
**LFX program:** [CNCF - OpenEverest: Develop the Object Storage provider (2026 Term 3)](https://mentorship.lfx.linuxfoundation.org/project/f1ac447c-0f12-42d4-bc90-83c9a3bd2648)
Contributor guide
Research direction
Read the existing OpenEverest v2 provider framework and upstream issue #2255 first; no files or tests are named in this proposal. Compare the existing database-provider lifecycle with the requested MinIO or SeaweedFS scope, then define completion around deployment, scaling, upgrades, bucket and user management, backup-target integration, tests, and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- api, backend, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100