Skip to content

Conversation

@nitinverma9
Copy link

Issue

Unable to set dnsConfig for pods

Description of changes

Adding in the ability to specify dns configuration for the aws-load-balancer-controller pods

Checklist

  • Added/modified documentation as required (such as the README.md for modified charts)
  • Incremented the chart version in Chart.yaml for the modified chart(s)
  • Manually tested. Describe what testing was done in the testing section below
  • Make sure the title of the PR is a good description that can go into the release notes

Testing

Deployed a version of the load-balancer controller in a test environment, by manually editing the deployment.yaml to include dnsConfig with options parameters of ndots as 1 and attempts as 3. Default value for ndots is 5, which means for dns resolution it sequentially go through all the local search domains first in /etc/resolv.conf and if none succeed, it will resolve it as an absolute name only at last, which can negatively affect app performance

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@nitinverma9 nitinverma9 requested a review from a team as a code owner July 29, 2025 09:20
@nitinverma9 nitinverma9 force-pushed the feature-add-dnsConfig branch from 8efb04c to 6f72e0d Compare July 29, 2025 12:59
….yaml. This is supported as a standard pattern across various public helm charts, so decided to make a PR here.
@nitinverma9 nitinverma9 force-pushed the feature-add-dnsConfig branch from 6f72e0d to e43f188 Compare July 31, 2025 07:50
@nitinverma9
Copy link
Author

Hello @shraddhabang can this be merged anytime soon?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant