Pod status InvalidImageName: couldn't parse image reference
The image field in the pod spec isn’t a valid image reference, so the kubelet can’t even try to pull it.
Seen on:
Kubernetes
Meaning
Kubernetes rejects references with uppercase letters, spaces, a trailing colon (image: app:), double slashes or unrendered template placeholders (image: {{ .Values.image }}). Helm/Kustomize values that came out empty are the most common cause.
Common causes
- Empty tag variable producing app: or app:@
- Uppercase letters or spaces in the name
- Unrendered template/placeholder in the manifest
- Protocol prefix (https://) in the image name
⚡ Quick fix
- kubectl describe pod to see the exact reference
- Fix the image value in values.yaml/kustomization
- Render locally and inspect: helm template / kustomize build
Detailed fix by platform
Kubernetes
- bash
kubectl get pod web-0 -o jsonpath='{.spec.containers[*].image}' helm template ./chart | grep -n 'image:'
How to diagnose
- Reference — Exact image string in the pod spec
- Templates — Rendered values empty?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Kubernetes
- error converting YAML to JSON error converting YAML to JSON: yaml: line 12: did not find expected key
- kubectl connection refused kubectl: The connection to the server localhost:8080 was refused — did you specify the right host or port?
- CreateContainerConfigError Kubernetes: CreateContainerConfigError — secret / configmap not found
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026