Some new experimental features in Helm are gated by certain environment variables. For example, using their new facility for referencing charts from an OCI registry requires setting HELM_EXPERIMENTAL_OCI=1.
Skaffold should allow configuring the environment, with templating, that is passed into Helm. The absence of this capability prevents users of Cloud Deploy from using experimental features.
We could consider broadening this to all builders and deployers as it could be useful for the custom, jib, and ko builders.
I have the same issue. Would be great if this was tackled.
All bitnami charts are basically now requiring OCI support while other (private) helm chart pulls still only support the old way.
Some new experimental features in Helm are gated by certain environment variables. For example, using their new facility for referencing charts from an OCI registry requires setting
HELM_EXPERIMENTAL_OCI=1
.Skaffold should allow configuring the environment, with templating, that is passed into Helm. The absence of this capability prevents users of Cloud Deploy from using experimental features.
We could consider broadening this to all builders and deployers as it could be useful for the custom, jib, and ko builders.