You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue you're experiencing is related to Kubernetes not being able to pull a private image from Docker Hub, as indicated by the error messages related to imagePullBackOff and ErrImagePull.
The likely causes are:
The secret push-secret-docker is not correctly configured with the right Docker credentials.
The image name xuybin/podinfo:latest does not exist or is misspelled in Docker Hub.
The Docker Hub repository xuybin/podinfo is not set to public, and Kubernetes is unable to authenticate with the provided credentials.
To resolve this:
Ensure that the Docker Hub repository exists and the image tag is correct.
Verify that the push-secret-docker Kubernetes secret contains the correct Docker credentials (username and password/token).
If the repository is private, make sure the secret is created with the dockerconfigjson type and the correct .dockerconfigjson content.
Apply the secret to the same namespace where your Kubernetes service is running.
If you have confirmed the above and the issue persists, you may want to manually pull the image on a local machine using the same credentials to ensure they are working. If they are, then reapply the secret and try to pull the image again on your cluster.
Description
imageCredentials pull private images fail.
Environmental
Tell us what your cluster environment is like, e.g.
Expected behavior
use imageCredentials pull private images ok
Actual behavior
Tell us what happens instead. Provide a log message if relevant.
To Reproduce
Steps to reproduce the behavior:
. See error
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: