csa/devops/ansible-patches/openshift.git/roles/openshift_node_dnsmasq/templates, branch ands

Combine openshift_node and openshift_node_dnsmasq

2017-11-27T19:08:58+00:00

This commit combines these two roles.  This will
prevent openshift_node_facts from running twice.

Switch from bind-interfaces to bind-dynamic

2017-10-31T17:53:30+00:00

dnsmasq cache-size dns-forward-max change

2017-10-30T21:05:03+00:00

On very large clusters dnsmasq performance suffers due to
limited cache-size and dns-forward-max values.

bug: 1482847
https://bugzilla.redhat.com/show_bug.cgi?id=1482847

Change dnsmasq to bind-interfaces + except-interfaces

2017-10-25T21:03:27+00:00

Currently, we have to set the listen ip for dnsmasq via ansible
during installation.

This commit enables dnsmasq to bind-interfaces + exclude interfaces
to ensure dnsmasq doesn't listen on lo interface.

Use openshift.node.dns_ip as listening address

2017-08-14T20:41:45+00:00

Use default ports for dnsmasq and node dns

2017-06-30T20:22:53+00:00

Run dns on the node and use that for dnsmasq

2017-06-30T20:22:53+00:00

Disable negative caching, set cache TTL to 1s

2017-06-13T16:57:00+00:00

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

openshift_node_dnsmasq - Remove strict-order option from dnsmasq

2016-12-01T20:01:04+00:00

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

2016-04-19T20:44:18+00:00