medium10 pts · first answer countskubernetestroubleshooting

ImagePullBackOff from a private registry

A new Deployment is stuck. kubectl describe pod shows the events below. What is the most likely fix?

Warning  Failed   kubelet  Failed to pull image "registry.example.com/team/api:2.3.0":
  failed to authorize: 401 Unauthorized
Warning  Failed   kubelet  Error: ErrImagePull
Normal   BackOff  kubelet  Back-off pulling image "registry.example.com/team/api:2.3.0"

A.Raise the container memory limit so the kubelet has room to unpack the image layers.B.Create a registry credential Secret and reference it in imagePullSecrets or the ServiceAccount.C.Switch the readiness probe from HTTP to TCP so the Pod is allowed to start the pull.D.Restart the kube-scheduler so the Pod is placed on a different node that already has the image cached.

← CPU vs memory limits Pod stuck Pending on CPU →