chore(helm): replace minio with seaweedfs for object storage
Summary
Replace MinIO with SeaweedFS as the object storage backend in Pyroscope Helm chart.
Fixes #4557
Motivation
SeaweedFS offers several advantages for production deployments:
- Production-ready: Battle-tested in large-scale environments with proven reliability
- S3-compatible API: Drop-in replacement for S3, ensuring compatibility with existing tooling
- Active community: Strong community support and regular updates
- Performance: Optimized for handling large volumes of profiling data efficiently
Changes
- Removed
miniodependency from Chart.yaml - Added
seaweedfs(v4.0.393) as the storage backend - Updated Chart.lock and dependency artifacts
Testing
- [x]
make lintpasses - [x]
make go/testpasses - [x] Helm chart validates successfully
Hi @simonswine
I’ve implemented the changes for Issue #4557.
Whenever you get a chance, please take a look and let me know if anything needs improvement.
Thanks!
Thanks for the detailed feedback.
I agree with the points raised (incomplete wiring, Helm version requirement, and the MinIO random password issue). I also agree that we should keep MinIO for backward compatibility and introduce SeaweedFS as an opt-in alternative (seaweedfs.enabled), allowing users to migrate at their own pace.
I’m happy to continue with this approach and update Helm values, docs, and checks. If you prefer RustFS (#4681) instead, please let me know and assign to me.