34Walk me through everything that happens between docker pull and the image being ready to run.▼hardAmazon & AWSGoogleNetflix◆ premiumA registry stores repositories, which hold manifests, which point at content-addressed blobs. Being able to draw that hierarchy and the auth exchange around it accounts for essentially every pull failure, because each one is a specific step in it returning something other than 200.Open full answer →
38This morning's deploy wave left dozens of pods in ImagePullBackOff, and the registry says rate limit. Why us, and what now?▼easySwiggyFlipkartAtlassian◆ premiumA public registry throttles by source IP and your whole fleet shares one. Why fifty nodes count as a single anonymous user, and authentication and caching changes that reduce upstream demand.Open full answer →
68New pods cannot pull images but every running pod is fine, and nothing was deployed. What changed?▼mediumRed HatMicrosoftAccenture◆ premiumRunning pods already have their images, so a credential expiry is invisible until something needs to start. That gap is why this always surfaces during an unrelated incident, at the worst moment.Open full answer →