-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubernetes cannot pull from a Harbor Registry deployed with ClusterIP #1838
Comments
you may need set proper dns mapping for your domain name |
Sorry @MinerYang can you elaborate? Where can i find the information for this? |
Could you provide the log of harbor-registry and proxy log while you unable to pull |
@MinerYang here are the harbor registry logs. I first push using kaniko, then try to assign the built image to a kubernetes deployment
I'm not running a proxy, but here are the
and here are the harbor nginx logs
|
I don't see any pulling requesting arriving at harbor side. This above logs more like a push request.
|
The kubelet uses the host DNS config for lookups so cannot resolve service IPs by DNS lookups of the service such as |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
I have a helmfile like such
I am able to push to it using a simple kaniko job like such
However, when I try to make a dimple deployment based on this image that I've successfully pushed, I get this erroring event
Here is my deployment.yaml
The text was updated successfully, but these errors were encountered: