csa/devops/ansible-patches/openshift.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use openshift.node.dns_ip as listening address	Scott Dodson	2017-08-14	1	-1/+1
\|
*	Use default ports for dnsmasq and node dns	Scott Dodson	2017-06-30	2	-2/+4
\|
*	Run dns on the node and use that for dnsmasq	Scott Dodson	2017-06-30	2	-1/+3
\|
*	Disable negative caching, set cache TTL to 1s	Steve Kuznetsov	2017-06-13	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \|	When running headless services as pods on OpenShift, no ClusterIP is assigned. In these cases, peer pods are relying on DNS to locate the service endpoints. When a pod is deleted or another trigger causes the endpoint to change, the OpenShift DNS is updated immediately. However, dnsmasq has a default TTL of 30s, so the wrong response is returned on name resolution. Removing negative caching and turning the TTL to a very short 1s should resolve the issue. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
*	openshift_node_dnsmasq - Remove strict-order option from dnsmasq	Scott Dodson	2016-12-01	1	-1/+0
\| \| \| \| \| \| \| \| \| \| \|	strict-order forces dnsmasq to iterate through nameservers in order. If one of the nameservers is down this will slow things down while dnsmasq waits for a timeout. Also, this option prevents dnsmasq from querying other nameservers if the first one returns a negative result. While I think it's odd to have a nameserver that returns negative results for a query that another returns positive results for this does seem to fix the issue in testing. Fixes Bug 1399577
*	Add openshift_node_dnsmasq	Scott Dodson	2016-04-19	1	-0/+4