[Enhancement]: keeping support for helm in non OCI repositories

[venkatamutyala]

Related problem

Per the last release 0.36.0:

Please use the Helm Chart OCI artifacts from our [Helm Chart OCI repository instead](https://quay.io/organization/strimzi-helm).

This represents a huge issue for cluster admins/operators. Helm OCI support isn't fully embraced by all helm tools (ex. ArgoCD). It would be great if we could continue support for at least another 12 months or longer so that everyone can safely cut over to OCI. Until the main helm project deprecates the legacy registry I don't think this project should either.

Not sure what the timeline was for a full removal but just wanted to advocate for this earlier than later.

Suggested solution

Keep publishing to both helm repositories until all major helm tools support OCI fully or until the helm project deprecates support for non-OCI itself

Alternatives

No response

Additional context

No response

[scholzj]

As said in the 0.36 release notes. The old Helm chart repository will remain to exist for some time. But it is manually maintained whcih often leads to issues and errors and it is there fore not reliable. So you should migrate your tooling to the OCI Helm Charts or to use the Helm Chart binary directly from the GitHUb release page which are fully automated.

[rouke-broersma]

@venkatamutyala which tools do not support helm OCI? You mention ArgoCD, but ArgoCD supports helm OCI.

[venkatamutyala]

I tried converting some apps to OCI earlier in the year with ArgoCD. I ran into weird issues where the standard (non-OCI) helm repository was generally better supported.

A few examples I was able to dig up from current/open GitHub issues:
argoproj/argo-cd#13574
argoproj/argo-cd#15344
yyzxw/argo-cd@ae3caea
argoproj/argo-cd#12436
argoproj/argo-cd#11709
argoproj/argo-cd#10823