pyroscope pod goes in crashloopbackoff if deployed via argocd in case minio is enabled

[Rishabh Tayal]

Describe the bug

Pyroscope pod goes in crashloopbackoff if deployed via argocd only if minio is enabled
attaching restart pyroscope logs :

podlogs-pyroscope-0-1741232738278.log

To Reproduce

Steps to reproduce the behavior:

1. Deploy pyroscope with minio enabled using argocd

Expected behavior

You have hardcoded helm hooks in helm chart which is incompatible argocd

Environment

• pyroscope chart version : 1.12.0
• Infrastructure: Kubernetes
• Deployment tool: argocd (https://github.com/argoproj/argo-helm/tree/main/charts/argo-cd)
• argocd chart version : 7.7.15
• argocd image : quay.io/argoproj/argocd:v2.13.3

Additional Context

The issue could be due to helm hooks used in annotations for creating minio bucket job and minio user job

[Anton Kolesnikov]

Thanks for filing the issue @tayalrishabh96!

Could you please clarify if the issue persists if you disable minio via values.yaml?

I'd suggest deploying pyroscope and minio independently