Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Images not being pushed to docker registry #184

Closed
joelsmith opened this issue May 10, 2023 · 2 comments · Fixed by #185
Closed

Images not being pushed to docker registry #184

joelsmith opened this issue May 10, 2023 · 2 comments · Fixed by #185
Labels
bug Something isn't working

Comments

@joelsmith
Copy link
Contributor

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

  • KEDA OLM Operator Version: 2.10.1
  • KEDA Version: Please elaborate: 2.10.1
  • Platform & Version: Please elaborate: linux/amd64
  • Kubernetes Version: Please elaborate: Any
  • OLM Version: Please elaborate: Any
@joelsmith
Copy link
Contributor Author

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

@joelsmith
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant