topic Re: Image Pull back on new node in Kuberenetes in Prisma Cloud Discussions

Image Pull back on new node in Kuberenetes

twistlock — Wed, 01 Jun 2022 15:45:36 GMT

All of sudden i have getting below issue on new nodes which are part of daemonset installation

Normal BackOff 74s (x554 over 126m) kubelet Back-off pulling image "registry-auth.twistlock.com/tw_u5ko4ug7ddtzhneqzja4fcyf1eekkuxc/twistlock/defender:defender_21_08_529"

Re: Image Pull back on new node in Kuberenetes

JensWegar — Wed, 04 May 2022 08:25:21 GMT

Based on the error message, I'd say something is blocking your kubernetes node from being able to pull the image from twistlock.com. I'd first check that the exact image URL that the node is trying to pull actually exists e.g. by doing a manual pull from your own machine. If that works, then check if something might be blocking the new nodes from accessing the URL, e.g. a firewall.

Some more info on debugging that error in Kubernetes: https://www.tutorialworks.com/kubernetes-imagepullbackoff/

Re: Image Pull back on new node in Kuberenetes

twistlock — Wed, 04 May 2022 21:23:41 GMT

I am not facing issue with kubernetes nodes . i am facing issues with twistlock console when it pulls docker repo for scanning as hardly scans few repos then gives 429 error as too many request

Re: Image Pull back on new node in Kuberenetes

RPrasadi — Wed, 13 Jul 2022 21:05:23 GMT

The Access Token (u5ko4ug7ddtzhneqzja4fcyf1eekkuxc) on their license may have expired due to a contract renewal. They will have to update the Daemonset deployment with the new image name with the new access token, or just generate a new Daemonset YAML and redeploy.