2

I have a gke cluster with two node pools.

By mistake I deleted an image from Artifact Registry and did a rollout that end with some pods in ImagePullBackOff (403 Forbidden). After creating back the image (via a Cloud Build build from git tag) I created a third node pool and deleted one of the pool that I had. Now the situation is that the pods in the old pool are able to download the image and the pods into the newly created pool are in ImagePullBackOff again (403 Forbidden again).

I have tried to create a forth pool but the situation is the same. I have a second gke cluster and the issue described is absent.

Have you got any idea why newly created pools into the first gke cluster are unable to download the image?

0

Resolved by waiting (a lot...) and creating back a new pool.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.