squakez commented on issue #5914: URL: https://github.com/apache/camel-k/issues/5914#issuecomment-2449033244
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](https://camel.apache.org/camel-k/next/installation/registry/special/own.html#configuring-registry-run-pod)" 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](https://kind.sigs.k8s.io/docs/user/local-registry/) does, for instance). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
