You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you are maybe already aware docker/hub-feedback#2314 GitHub will sunset free Teams. This change will lead to frozen public images if the owner doesn't apply to the OpenSource Program or buys the Team. (That's at least my interpretation, but as it's currently a manner of hours until this changes it's also not put into stones).
Is there any plan how Calico will handle this? Alternatives could be for example github, google, quay or ecr.
Thank you in advance,
Best regards,
Björn
The text was updated successfully, but these errors were encountered:
Hey @DaspawnW , thanks for bringing this up! I believe that we pay for our docker hub account (I'm not 100% sure so I'll have to check) so I think we might not be affected by this, but I'll definitely check with the rest of our team to make sure that we don't suffer any downtime. We also mirror a lot of our images on quay (and we're thinking about changing the default images used in our manifests/operator to quay since we don't hit pull limits there) so we should be covered in case something catastrophic happens.
As you are maybe already aware docker/hub-feedback#2314 GitHub will sunset free Teams. This change will lead to frozen public images if the owner doesn't apply to the OpenSource Program or buys the Team. (That's at least my interpretation, but as it's currently a manner of hours until this changes it's also not put into stones).
Is there any plan how Calico will handle this? Alternatives could be for example github, google, quay or ecr.
Thank you in advance,
Best regards,
Björn
The text was updated successfully, but these errors were encountered: