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

Change dnsLookupFamily to ALL in vpn seed envoy config. #9102

Merged
merged 1 commit into from
Feb 1, 2024

Conversation

axel7born
Copy link
Contributor

How to categorize this PR?

/area networking
/kind enhancement

What this PR does / why we need it:
The envoy property dnsLookupFamily determines the address family for DNS lookups.
V4_PREFERED means, that a DNS lookup for the IPv4 address is made and if there is no result a lookup for IPv6 is made.
The meaning of ALL would be that both IPv4 and IPv6 lookups are made.
However, the property has the side effect, that with IPV4_PREFERED envoy tries to resolve IPv6 addresses as hostnames.
This results in unnecessary DNS queries.
The envoy proxy in the VPN seed server doesn't need to to do any DNS lookups. Unnecessary lookups for addresses as hostnames can prevented by setting dnsLookupFamily to ALL.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:

Change dnsLookupFamily to ALL in vpn seed envoy config, to prevent unnecessary DNS lookups.

@gardener-prow gardener-prow bot added area/networking Networking related kind/enhancement Enhancement, improvement, extension labels Feb 1, 2024
@gardener-prow gardener-prow bot added cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 1, 2024
@axel7born
Copy link
Contributor Author

/cc @DockToFuture @ScheererJ

Copy link
Member

@ScheererJ ScheererJ left a comment

Choose a reason for hiding this comment

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

Thanks a lot for the nice improvement to reduce the DNS load in IPv6 scenarios.

/lgtm
/approve

@gardener-prow gardener-prow bot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2024
Copy link
Contributor

gardener-prow bot commented Feb 1, 2024

LGTM label has been added.

Git tree hash: 0146cdf4f85baf01c57fb1b151252703ee99aca5

@gardener-prow gardener-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 1, 2024
Copy link
Member

@DockToFuture DockToFuture left a comment

Choose a reason for hiding this comment

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

/lgtm

Copy link
Contributor

gardener-prow bot commented Feb 1, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DockToFuture, ScheererJ

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gardener-prow gardener-prow bot merged commit 990f41f into gardener:master Feb 1, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/networking Networking related cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. kind/enhancement Enhancement, improvement, extension lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants