Release Operator as Helm Chart

[sbose78]

Should we have a process to do release helm charts into a public community hub apart from having a kubernetes community operator/OLM release too ?

[qu1queee]

@sbose78 im glad you ask this. Yes, what about https://hub.helm.sh/ ? Also, I have been thinking on putting them in an s3 bucket(for every time we merge on master). Any other hubs in mind?

[qu1queee]

I can layout the process next week, let me know. If yes, please assign the issue to me.

[qu1queee]

@routerhan will work on this

[cmoulliard]

Helm chart can be release using a github action flow - https://github.com/marketplace/actions/helm-chart-releaser

[adambkaplan]

Revisited this issue in 2026-01-12 community meeting:

1. operatorhub.io appears to be dying on the vine. Many notable projects (Flux, cert-manager) have marked their operators as deprecated, and the CI infrastructure uses an outdated version of k8s. See kiwi Test Uses Obsolete Version of k8s k8s-operatorhub/community-operators#7263
2. Helm charts can now be published as OCI artifacts and pushed to GitHub's container registry. No chart repository needed.

From the community discussion, packaging the operator as a Helm chart makes sense as it provides a consistent user experience for future components (ex: triggers).