We've had the work queued for a while (to use a service or DNS name) and the problems you are roughly things we know we'd have to fix. The end goal would be to ensure that the hosts have access to the cluster CA (so the Docker daemon can verify the name of the service against a CA) and resolve.conf would also need to be set up. SkyDNS runs on the masters today and is load balanced over the service network, so you can use the master's service IP on the nodes as the resolver on the same address that the master users (that has some issues because of DNS lookups). Practically, most services *in* the cluster don't need to talk to the registry directly, so it's also possible that we could simply use an assigned name. You can set OPENSHIFT_DEFAULT_REGISTRY on the API servers in order to force the value to be a particular name, which you could then make whatever you want in /etc/hosts on each node, but you'd want to do that on a new cluster. We have a card queued up to make it easy to migrate the internal registry URL data.
There is no limiter on build pod nodes today other than the project limiter, but it is planned. On Tue, Jan 26, 2016 at 11:24 AM, Brandon Richins <brandon.rich...@imail.org> wrote: > I’ve recently gone through setting up an OpenShift registry and adding its > IP to the NO_PROXY environment variable for Docker. (See > https://docs.openshift.org/latest/install_config/http_proxies.html). I > noticed most builds (in the log files) reference the registry by IP and port > like 172.30.126.115:5000. I was wondering if it is possible to have builds > and other components refer to the registry through the service DNS name such > as docker-registry.default.svc.cluster.local instead of by its IP address. > I’m guessing I’d need to add the master’s IP address to /etc/resolv.conf > since Sky DNS doesn’t appear to run on the nodes (port 53 doesn’t appear to > be bound). > > Another question that came up is what nodes are build pods be scheduled to > run on? Is there a way to restrict build and or deploy pods to a subset of > nodes via a selector? > > Thanks, > > Brandon Richins > > _______________________________________________ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > _______________________________________________ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
