Thanks!
-James _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Is there any reason (other than bugs :) ) that pods instantiated to
execute builds of Docker-based apps wouldn't be able to resolve
*.svc.cluster.local names? I have two apps in a project, one built using
a Docker strategy, and one using s2i.. the s2i one is able (at
buildtime) to contact other services in the cluster using
foo.bar.svc.cluster.local but the Docker one cannot (it is trying to use
a local Maven mirror and failing to resolve the nexus server hostname
using the *.svc.cluster.local name). Using the externally-exposed name
works fine.
- dns failures from build pods James Falkner
- Re: dns failures from build pods Ben Parees
- Re: dns failures from build pods James Falkner
