OCI Chart Storage Stabilization in Helm 3.11 Introduces Unresolved CRD Version Conflict Handling

When using Helm 3.11’s stabilized OCI chart storage to distribute charts, teams aim to safely manage CustomResourceDefinition (CRD) versions across multiple releases.

However, Helm does not currently detect or prevent situations where two releases attempt to install different versions of the same CRD, leaving the cluster in an indeterminate state that requires manual inspection to determine which version is active.

This gap raises the question of how Helm should handle CRD version conflicts moving forward.

Should Helm emit a warning when a release would introduce a conflicting CRD version? Should Helm block the installation unless the user explicitly overrides the conflict? Should Helm provide a flag to enforce namespace‑scoped CRDs or delegate CRD management to external tools?