Skip to main content

Pod Status: ImagePullBackOff or InvalidImageName

This means there is something wrong with the credentials used to authenticate to the repository or the referenced image does not exist. Describe the pod to get events to see which specific image is failing and what specific failure it is running into.

# Get pod events
kubectl describe pod ${POD_NAME} -n ${NAMESPACE}

Image name is incorrect​

Check the relevant kustomization.yaml in the .platform repo. Double-check that the new and old names for the image are correct. If the image name is incorrect, you need to actually make fixes in the .platform directory for your application's repo. Most likely you need to fix the parameters for the p6m-actions/platform-application-manifest-dispatch action. See the action's README for help on the parameters.

No Permissions or Access Denied​

Follow the troubleshooting steps from Image name is incorrect above. If you have verified the image exists, there may be a problem rotating the artifactory token. Contact Ybor support to validate that your artifactory tokens are being rotated properly.

Image Not Found​

Make sure the image being referenced actually exists. See if you can manually find the image on the appropriate docker registry and verify that it has the referenced tag.

For artifactory, go to the relevant artifactory URL and find the image from the docker package page. Select all tags and verify that the referenced tag is in the list. If the image or the tag is not available, there might be a failure or misconfiguration in the CI/CD pipelines. See CI/CD troubleshooting