-
Notifications
You must be signed in to change notification settings - Fork 47
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
Sunsetting usage of dockerhub in Keptn #250
Comments
thanks for bringing this up @mowies. What do you think? |
Thank you, @mowies for tagging me. https://github.com/keptn-sandbox/keptn-eks-blueprints-addon is not building any container images and would not be affected by the Docker Change. |
@mowies https://github.com/keptn-contrib/artifacthub only consists of GitHub Actions to fetch new releases from the other repositories so that they can be displayed on ArtifactHub. No Docker container exists for this repository, and therefore it doesn't need to be considered for the migration. |
Thanks for the heads up Moritz. https://github.com/keptn-sandbox/datadog-service and https://github.com/keptn-sandbox/sumologic-service don't use dockerhub so we are good. |
Hi @mowies Regarding my organizations: |
Thanks @mowies for bringing this up. The repository I'm tagged in, https://github.com/keptn-sandbox/new-keptn-docs-engine, is not affected by the Docker change since it's not building any container images. |
hey @mowies, keptn-sandbox/k6-service is also not affected... thanks! |
https://github.com/keptn-sandbox/ansibletower-service |
https://github.com/keptn-sandbox/slackbot-service
This can be archived.
Regards,
Zohaib
…________________________________
From: Gabriel Prioli ***@***.***>
Sent: Wednesday, March 22, 2023 6:46 PM
To: keptn/community ***@***.***>
Cc: Zohaib UL-Hassan ***@***.***>; Mention ***@***.***>
Subject: Re: [keptn/community] Sunsetting usage of dockerhub in Keptn (Issue #250)
https://github.com/keptn-sandbox/ansibletower-service
is something I'm personally not working on anymore, so please go ahead and archive it
@mowies<https://github.com/mowies>
—
Reply to this email directly, view it on GitHub<#250 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADE6373FBLM6QJVP7QNRHLTW5L7D7ANCNFSM6AAAAAAV45H76E>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
https://github.com/keptn-sandbox/jira-service > Can be archived |
I created #257 so that we can do the project archiving in bulk after waiting a bit longer for people to answer to this issue. |
Hi @mowies, |
Sunsetting the usage of docker in the Keptn Organization
Docker is sunsetting the "free teams" plan that the keptn organization used until now for several dockerhub orgs including
keptn
,keptndev
,keptn-sandbox
andkeptn-contrib
. This means that we have another 30 days until images in the mentioned repositories will potentially not be accessible anymore.We did start the application process for an open source license for dockerhub, but that process might take a while and the general plan will still be to migrate all container images to GHCR and leave dockerhub behind.
Many images are already on GHCR and don't actually need to be moved, but there are a few repos that make use of keptn images from dockerhub.
All versions of Keptn >=1.0.0 will be migrated from dockerhub to GHCR and Helm charts will be adapted accordingly. We will provide more info about that in a separate announcement on Slack when the change is done.
The Plan
The following plan was discussed in the community meeting that was held on March 15, 2023:
Especially Keptn V1 will be migrated from v1.0.0, and Helm charts will be adapted
I am writing this ticket to get the ball rolling and starting migrating things. Since all the repos are under keptn/-contrib/-sandbox orgs, it's hard to find the right people to contact about this. We are going with contacting the users with the most contributions for each repo so that we have someone to contact at least.
References
Link to FAQ about this by Docker: https://web.docker.com/rs/790-SSB-375/images/privatereposfaq.pdf
The text was updated successfully, but these errors were encountered: