option 1:
run a GL pipeline at intervals to pick up the latest rhdh-hub image and copy it over to https://github.com/rhdh-bot/openshift-helm-charts (reuse what I have already)

• https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/build/ci/publish-helmchart.yml
• https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/build/ci/publish-helmchart.sh
• https://gitlab.cee.redhat.com/rhidp/rhdh/-/tree/rhdh-1-rhel-9/build/helm

option 2:
implement a custom tekton pipeline + task to do the above, but inside the Konflux pipeline for building the rhdh-hub image so we git it immediately, rather than at some polling interval – this would be the most machine-efficient way but would also require learning how to write a tekton pipeline and call it from my Konflux config. could it be generalized to be useful for multiple products that want helm charts for their CI builds? :thinking:

Sample code:

• https://github.com/konflux-ci/build-definitions/blob/main/pipelines/template-build/template-build.yaml
  • https://github.com/konflux-ci/build-definitions/blob/main/pipelines/fbc-builder/kustomization.yaml#L4
  • https://github.com/konflux-ci/build-definitions/blob/main/pipelines/fbc-builder/patch.yaml

• https://github.com/konflux-ci/build-definitions/blob/main/task/fbc-related-image-check/0.1/fbc-related-image-check.yaml
• https://github.com/konflux-ci/build-definitions/blob/main/task/buildah-oci-ta/0.2/buildah-oci-ta.yaml