-
Notifications
You must be signed in to change notification settings - Fork 10
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
Migrating our containers to GitHub Container Registry #16
Comments
Thoughts @kedacore/keda-maintainers? |
Happy to pick this up. |
Sounds good! |
Thoughts on this @jeffhollan @anirudhgarg @ahmelsayed? |
Yesterday we've agreed that this is the way forward, but we'll publish them in both Docker Hub & GitHub Container Registry until GHCR is out of preview. We will:
|
I'd propose to write a small blog post with this as well, next to the GitHub Discussion, what do you think? |
Blog post is published on https://keda.sh/blog/migrating-to-github-container-registry/ and discussion is open on kedacore/keda#1700 |
GHCR is GA, it's time to remove Docker Hub support and close this deprecation. Agreed @kedacore/keda-maintainers? Happy to pick this up. |
I agree |
+1 |
No longer push to Docker Hub on release as per kedacore/governance#16 Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
No longer push to Docker Hub on release as per kedacore/governance#16 Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
No longer push to Docker Hub on release as per kedacore/governance#16 Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
No longer push to Docker Hub on release as per kedacore/governance#16 Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
KEDA v2.6 will only be available on GitHub Container Registry. |
We've discussed it in the past (see kedacore/keda#995) but I think it's time to migrate our Docker images to GitHub Container Registry which brings our artifacts closer to our GitHub repos and gives us more insights on the adoption (# of pulls per tag, instead of vague total pull count).
We are dry-running this for our HTTP add-on and it's fairly straightforward.
Here is how people can discover them:
Per Docker image, you can then see the pull count per tag:
I've used this on other projects as well and it gives you a lot more insights than Docker Hub, and would never move back.
The text was updated successfully, but these errors were encountered: