{"action":"created","issue":{"url":"https://api.github.com/repos/openshift/openshift-ansible/issues/1314","repository_url":"https://api.github.com/repos/openshift/openshift-ansible","labels_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/1314/labels{/name}","comments_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/1314/comments","events_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/1314/events","html_url":"https://github.com/openshift/openshift-ansible/issues/1314","id":130373727,"number":1314,"title":"DNS out-of-the-box configuration. ","user":{"login":"timothysc","id":169553,"avatar_url":"https://avatars.githubusercontent.com/u/169553?v=3","gravatar_id":"","url":"https://api.github.com/users/timothysc","html_url":"https://github.com/timothysc","followers_url":"https://api.github.com/users/timothysc/followers","following_url":"https://api.github.com/users/timothysc/following{/other_user}","gists_url":"https://api.github.com/users/timothysc/gists{/gist_id}","starred_url":"https://api.github.com/users/timothysc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timothysc/subscriptions","organizations_url":"https://api.github.com/users/timothysc/orgs","repos_url":"https://api.github.com/users/timothysc/repos","events_url":"https://api.github.com/users/timothysc/events{/privacy}","received_events_url":"https://api.github.com/users/timothysc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":38,"created_at":"2016-02-01T14:19:41Z","updated_at":"2016-02-24T21:24:27Z","closed_at":null,"body":"Post deployment our default configuration leaves DNS in a state where pods can not communicate with the outside world.   \r\n\r\nWhen running upstreams networking conformance tests the pods fail to resolve google.com.  In order to rectify, I had to setup dnsmasq on the master.  http://developerblog.redhat.com/2015/11/19/dns-your-openshift-v3-cluster/\r\n\r\nThis is not spelled out as a separate step post installation, but imho there is really no reason the installer can not properly configure dnsmasq on the master. \r\n\r\n/cc @rrati @jayunit100 @jeremyeder @mattf"},"comment":{"url":"https://api.github.com/repos/openshift/openshift-ansible/issues/comments/188458974","html_url":"https://github.com/openshift/openshift-ansible/issues/1314#issuecomment-188458974","issue_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/1314","id":188458974,"user":{"login":"sdodson","id":48161,"avatar_url":"https://avatars.githubusercontent.com/u/48161?v=3","gravatar_id":"","url":"https://api.github.com/users/sdodson","html_url":"https://github.com/sdodson","followers_url":"https://api.github.com/users/sdodson/followers","following_url":"https://api.github.com/users/sdodson/following{/other_user}","gists_url":"https://api.github.com/users/sdodson/gists{/gist_id}","starred_url":"https://api.github.com/users/sdodson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sdodson/subscriptions","organizations_url":"https://api.github.com/users/sdodson/orgs","repos_url":"https://api.github.com/users/sdodson/repos","events_url":"https://api.github.com/users/sdodson/events{/privacy}","received_events_url":"https://api.github.com/users/sdodson/received_events","type":"User","site_admin":false},"created_at":"2016-02-24T21:24:27Z","updated_at":"2016-02-24T21:24:27Z","body":"https://github.com/openshift/origin/pull/7598 adds dnsmasq via NetworkManager dispatcher works out of the box assuming default cluster dns values. My intention is to complete testing of that and deliver that via the origin/atomic-openshift node RPMs. We can then configure dnsIP = ansible_default_ipv4 to switch over to using node local dnsmasq once we're sure of how robust dnsmasq proves to be."}}