container-cache: podDisruptionBudget values are documented but not read by the PDB template

[balajinvda]

Problem

deploy/helm/container-cache/deploy/values.yaml (chart 0.30.x) documents:

podDisruptionBudget:
  enabled: false
  # minAvailable and maxUnavailable are mutually exclusive; set exactly one.
  minAvailable: ""
  maxUnavailable: ""

but templates/poddisruptionbudget.yaml does not reference any of those keys. It renders a PodDisruptionBudget with minAvailable: 50% whenever replicaCount > 1, regardless of enabled, minAvailable or maxUnavailable. Verified with helm template on 0.30.4: podDisruptionBudget.enabled=true, minAvailable=2 still renders minAvailable: 50%, and enabled=false still renders the PDB.

Expected

The template honours the values: no PDB when enabled is false, and exactly one of minAvailable / maxUnavailable emitted when set, falling back to the current 50% default.

Why it matters

Downstream templates (sbom-templates) cannot expose these knobs from cluster-spec while they are ignored, and operators reading values.yaml assume they work.