grafana/pyroscope

Replace minio with alternatives

Open

#4557 opened on Oct 23, 2025

View on GitHub
 (3 comments) (1 reaction) (0 assignees)C (9,041 stars) (528 forks)batch import
good first issuehelm

Description

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:

Contributor guide

Tech stack
godockerkubernetes
Domain
infrastructurecloudbackend
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go programmingHelm chart usageObject storage concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
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.