Problem

Helmfile shells out to helm binary currently v3.7.1. Helm before v3.8.0 allowed users to opt into incomplete OCI functionality – which was still EXPERIMENTAL – and because of this would not enable that feaure unless users explicitly set HELM_EXPERIMENTAL_OCI=1.

Helmfile is using the experimental flag before the full feature in Helm was complete, by setting the HELM_EXPERIMENTAL_OCI environment variable for users. However, this information is not conveyed to Helmfile users, which means those users are depending on a feature from a version of Helm where it was not yet complete and considered "experimental" (use at own risk).

Interim solutions

I’m a bit concerned about this problem, and think it's important that Helmfile document this non-explicit experimental opt-on when users set oci: true as the OCI Registries section of Helmfile's README instructs.

Longer-term solutions

• I see there is a HELMFILE_EXPERIMENTAL env var, but this is only used for Helmfile’s concept of “explicit mode” and not for OCI, which was the only experimental feature of this version of Helm. I would suggest moving Helmfile's experimental OCI functionality behind this flag as well
• Or if it's close to equal effort, focusing on Update Helmfile project to use Helm OCI full feature #2111 instead would be more valuable to end users