Debugging ImagePullBackOff on a private registry
WHAT IT TESTS: registry auth and systematic debugging. OUTLINE: imagePullSecrets reference a dockerconfigjson Secret on the pod or service account, kubelet uses it to authenticate, and you inspect events to isolate auth versus name versus network errors.
WHAT IT TESTS: whether you understand how kubelet authenticates to private registries and can debug methodically. ANSWER OUTLINE: explain that a docker-registry Secret of type dockerconfigjson holds credentials, referenced via imagePullSecrets on the pod or attached to its service account, and kubelet uses it at pull time. Then troubleshoot with kubectl describe pod to read the exact event, distinguishing wrong image name, missing or wrong secret, expired token, and node network or RBAC issues.
Read the original → interview
- #kubernetes
- #imagepullbackoff
- #secrets
- #registry
- #troubleshooting
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.