Current status 

Until now only the operator has an helm chart. 

Operator helm chart is related to https://github.com/debezium/debezium-operator-manifests

repo.

In that repo, after the release and when the images are available, we publish the helm package as GH release artifact and then build the https://charts.debezium.io/index.yaml through GH pages. 

Now we also have to manage the helm chart for Debezium Platform.

Ideally, It will be good to have all our charts inside the same yaml file under the charts.debezium.io

Plus there is also the possibility to push them as OCI artifacts on quay.io.

Strimzi adopted both approaches. 

Proposed solution

Prerequisites:

We should have a debezium-charts repo with the gh-pages and charts.debezium.io will point to it. 

This will be the place of the index.yaml file.

Pipeline changes

Our release pipeline should:

• Package and push operator/debezium platform helm chart artifact on GH release
• This can be done using the the GH CLI create release

• Build the index.yaml
• This can be done using helm repo index command.

• Push the helm chart packages to quay.io (maybe into a separate organization like debezium-helm like strimzi-helm)
• This can be done with helm push

• The release pipeline should trigger the image builds.