Possible rate limits for pulling images from ghcr.io? #49671
Replies: 3 comments 1 reply
-
Similar mentioned at #45253 |
Beta Was this translation helpful? Give feedback.
-
The overall docs appear to be here: There appears to be no usage rate limit for public registries (although it is unclear if there are intentions for this to change). Otherwise, usage appears to be billed both by storage time and data transfer: |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
We host our packages in the form of docker container images on ghcr.io. These docker images are used to deploy various kinds of applications to multiple kubernetes clusters.
Each repository holds one docker image, and applications from that repository are deployed into a kubernetes namespace with the same name as that of the repository. All applications within that namespace use the same docker container image.
All the applications in that given namespace (whether it is a deployment, or a statefulset, or a cronjob) rely have
.spec.imagePullSecrets
configured to point to a secret that contains a github username and a PAT associated with that username. We know those credentials work because executingdocker login
using those credentials and then executing adocker pull ghcr.io/<org>/repo:<tag>
works successfully.However, on using the same credentials within a kubernetes cluster, pods get stuck in the
ImagePullBackoff
state, withkubectl describe pod ...
indicating an HTTP 4xx status code for docker pulls.This begs the question - does ghcr.io impose rate limits for pulling images from ghcr.io for a given username:PAT combination?
Beta Was this translation helpful? Give feedback.
All reactions