Hello folks. I'm working on this issue [0] for the openstack provider. The WIP solution has a blocker [1] in the deployment logic, and I'm pretty sure this problem (the order of configuring dnsmasq vs cluster nodes) had been already solved for openshift-ansible/contrib, for another cloud providers. So could you please share existing solutions ensuring persistent DNS configuration for cluster nodes?
I suppose, I need to configure dnsmasq for nodes before the cluster nodes' sercices, so those would be able to resolve external and authoritative (cluster) domain resolve requests early, like: * Call playbooks/byo/openshift-cluster/enable_dnsmasq.yml for provisioned nodes * Call playbooks/byo/config.yml to deploy the cluster Thoughts? [0] https://github.com/openshift/openshift-ansible-contrib/issues/455 [1] https://github.com/openshift/openshift-ansible-contrib/pull/471#issuecomment-311891654 -- Best regards, Bogdan Dobrelya, Irc #bogdando _______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
