grafana/pyroscope

Replace minio with alternatives

Open

#4,557 opened on Oct 23, 2025

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

Repository metrics

Stars
 (9,041 stars)
PR merge metrics
 (Avg merge 5d 7h) (62 merged PRs in 30d)

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

Research direction
Evaluate the listed storage alternatives (garage, versitygw, seaweedfs) for compatibility with Pyroscope's S3 API usage. Update the Helm chart to replace minio with one of the alternatives, ensuring backward compatibility and testing.
Tech stack
godockerkubernetes
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoDockerKubernetesHelm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30