Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

production config: add dot to some DNS address to reduce lookups #5789

Merged
merged 1 commit into from
May 2, 2022

Conversation

bboreham
Copy link
Contributor

@bboreham bboreham commented Apr 6, 2022

What this PR does / why we need it:

Kubernetes sets up a DNS search path like namespace.svc.cluster.local, svc.cluster.local, cluster.local, google.internal; any unqualified name is first tried as a prefix to each of these. These requests, which will never succeed, add latency and increase load on the DNS service.

Adding a . at the end makes the name fully-qualified, so Go's DNS client will skip the search path and use the name as-is.

Special notes for your reviewer:

Note this only changes a subset of addresses in the config; others didn't seem to be causing a problem and I don't have a good way to test them.

Checklist

  • NA Documentation added
  • NA Tests updated
  • Add an entry in the CHANGELOG.md about the changes.

@bboreham bboreham requested a review from a team as a code owner April 6, 2022 15:22
Copy link
Contributor

@sandeepsukhani sandeepsukhani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Kubernetes sets up a DNS search path like `namespace.svc.cluster.local,
svc.cluster.local, cluster.local, google.internal`; any unqualified name
is first tried as a prefix to each of these. These requests, which will
never succeed, add latency and increase load on the DNS service.

Adding a `.` at the end makes the name fully-qualified, so Go's DNS
client will skip the search path and use the name as-is.

Note only changes a subset of addresses in the config; others didn't
seem to be causing a problem.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants