grafana/pyroscope

Replace minio with alternatives

Open

#4,557 创建于 2025年10月23日

在 GitHub 查看
 (3 评论) (1 反应) (0 负责人)C (9,041 star) (528 fork)batch import
good first issuehelm

描述

While our helm chart uses a fairly old version of minio anyhow, we likely want to move on from minio, given they stopped providing helm charts and docker images for the OSS community.

Likely alternatives we should verify are:

贡献者指南

技术栈
godockerkubernetes
领域
infrastructurecloudbackend
议题类型
refactor
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Go programmingHelm chart usageObject storage concepts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
The issue suggests replacing minio with alternatives like garage, versitygw, or seaweedfs. The contributor should investigate each alternative's compatibility with Pyroscope's current architecture, review the existing Helm chart configuration for minio, and propose a migration plan. Key files to examine include the Helm chart templates and Go code that interfaces with object storage.
Replace minio with alternatives · grafana/pyroscope#4557 | Good First Issue