Helm Chart Extra Args Config not being deployed

[pafrench]

Describe the bug

The setting for pyroscopedb.max-block-duration is not being applied to the deployment.

To Reproduce

The following setting was added to the Helm chart:

pyroscope:
  # config removed for brevity

  resources:
    extraArgs:
       pyroscopedb.max-block-duration: 30m
    limits:
      cpu: 3
      memory: 6Gi
    requests:
      cpu: 1
      memory: 2Gi

  # config continues

A manifest was then generated as follows:
helm template pyroscope grafana/pyroscope --namespace namespace-goes-here --values ./thirdparty/pyroscope/helm-values.yaml > ./thirdparty/pyroscope/kubernetes/base/generated-manifest.yaml

And deployed to the cluster.

Expected behavior

The pyroscopedb.max-block-duration value should be seen in the deployed pyroscope pod's pyroscope container args, but is not:

Controlled By:  StatefulSet/pyroscope
Containers:
  pyroscope:
    Container ID:  containerd://07a62d7d0a936894999038b884c31bcdb1de8aed5d6b2d85e5d99fb91ddbe58c
    Ports:         4040/TCP (http2), 7946/TCP (memberlist)
    Host Ports:    0/TCP (http2), 0/TCP (memberlist)
    Args:
      -target=all
      -self-profiling.disable-push=true
      -server.http-listen-port=4040
      -memberlist.cluster-label=namespace-goes-here-pyroscope
      -memberlist.join=dns+pyroscope-memberlist.namespace-goes-here.svc.cluster.local.:7946
      -config.file=/etc/pyroscope/config.yaml
      -runtime-config.file=/etc/pyroscope/overrides/overrides.yaml
      -log.level=debug
    State:          Running
      Started:      Tue, 24 Feb 2026 12:27:42 +0800
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     3
      memory:  6Gi
    Requests:
      cpu:      1
      memory:   2Gi

Am I looking in the wrong spot? I can't see anything in the config maps either. At the moment I'm assuming the setting isn't taking effect.

Environment

• Infrastructure: Kubernetes
• Deployment tool: Helm

[tylerauerbeck]

I think your problem is that you have extraArgs under resources, when it should just be under pyroscope at least according to your example above.