Closed cfitzw closed 3 weeks ago
Hello, thanks for reporting. Unfortunately I believe this is a Kubernetes architecture limitation. We have analyzed and reported this in the "run your own container registry" guide:
[Minkube] deploys a container registry as a Pod, and you can use the service cluster IP. We cannot use the service URL as it won’t be available in the Kubernetes components which are in charge to run the Deployment (it does not use Service/Pod cluster DNS). However, it can use the Cluster IP which is available throughout all the cluster or any Ingress which would expose the service publicly.
The Kubernetes DNS is not able to use any of it's internal service out of the box. I think you need to tweak the low level configuration of the platform to be able to do that (something in the same fashion as Kind does, for instance).
Excellent - already accounted for in the documentation, sorry for missing it. Feel free to close this out.
What happened?
While testing v2.5 and attempting to use minikube's dns uri (registry.kube-system.svc.cluster.local), the kit builds but the pull fails.
All other factors the same, when using the IP, everything works.
In conjunction with this code fix, I believe the documentation here should be updated...
from:
to:
Steps to reproduce
Run:
Relevant log output
Camel K version
v2.5.0-nightly