kedacore / keda-olm-operator

Operator for deploying KEDA Controller on OperatorHub.io/OLM
Apache License 2.0
31 stars 23 forks source link

Images not being pushed to docker registry #184

Closed joelsmith closed 1 year ago

joelsmith commented 1 year ago

According to https://github.com/kedacore/keda-olm-operator/blob/main/RELEASE-PROCESS.md#8-create-keda-release-on-github Git should automatically build images based upon the release and push them to DockerHub. It appears that this is not working as DockerHub doesn't show any releases after 2.5.0:

https://hub.docker.com/r/kedacore/keda-olm-operator/tags

Expected Behavior

New releases should appear on DockerHub

Actual Behavior

New releases do not appear on DockerHub

Steps to Reproduce the Problem

  1. Look at current releases: https://github.com/kedacore/keda-olm-operator/releases
  2. Look at DockerHub tags: https://hub.docker.com/r/kedacore/keda-olm-operator/tags
  3. Notice that newer releases do not have a corresponding tag on DockerHub.

Specifications

joelsmith commented 1 year ago

Once this issue is resolved, the 2.10.1 release needs to be completed via these two PRs: https://github.com/k8s-operatorhub/community-operators/pull/2731 https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/2640

joelsmith commented 1 year ago

Silly me... of course there is no way it's been broken since 2.5.0, so clearly the images were being published somewhere else. This bug can be closed via a doc update to point to the new GHCR repo instead.