Configure object storage backend

[MJawad-AbouAleiwi]

Hello,

If I'm using Pyroscope in K8s, and I want to use MinIO as a storage backend, is the following configuration is valid?

  containers:
    - name: pyroscope
      image: grafana/pyroscope:latest
      args:
        - "--storage.backend=s3"
        - "--storage.s3.endpoint=minio:9090"
        - "--storage.s3.region=eu-west-2"
        - "--storage.s3.bucket-name=pyroscope-data"
        - "--storage.s3.secret-access-key=minioadmin"
        - "--storage.s3.access-key-id=minioadmin"
        - "--storage.s3.insecure=true"

When I access http://localhost:4040/api/v1/status/config, I see the following:

storage:
    backend: s3
    s3:
        endpoint: minio.default.svc.cluster.local:9000
        region: eu-west-2
        bucket_name: pyroscope-data
        secret_access_key: '********'
        access_key_id: minioadmin
        insecure: true
        signature_version: v4
        force_path_style: false
        bucket_lookup_type: auto
        sse:
            type: ""
            kms_key_id: ""
            kms_encryption_context: ""
        http:
            idle_conn_timeout: 1m30s
            response_header_timeout: 2m0s
            insecure_skip_verify: false
            tls_handshake_timeout: 10s
            expect_continue_timeout: 1s
            max_idle_connections: 0
            max_idle_connections_per_host: 100
            max_connections_per_host: 0

but the pyroscope logs:

ts=2025-07-04T09:07:04.192238171Z caller=pool.go:250 level=warn component=distributor msg="removing ingester failing healthcheck" addr=10.244.0.191:4040 reason="failing healthcheck status: NOT_SERVING"