-
Notifications
You must be signed in to change notification settings - Fork 192
ignore dns servers from dhcp when providing nameservers #4023
ignore dns servers from dhcp when providing nameservers #4023
Conversation
Cluster Generation A/B Results: |
Codecov Report
@@ Coverage Diff @@
## main #4023 +/- ##
==========================================
- Coverage 48.53% 48.43% -0.11%
==========================================
Files 446 434 -12
Lines 44110 43345 -765
==========================================
- Hits 21410 20993 -417
+ Misses 20657 20359 -298
+ Partials 2043 1993 -50
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
b57dc06
to
9d8c52a
Compare
/test install-vc7 |
Cluster Generation A/B Results: |
Build failed! Build no: 3418 |
/test install-vc7 |
9d8c52a
to
07dba41
Compare
Cluster Generation A/B Results: |
Looks like the install-vc7 tests passed, we should be good to go after a review |
07dba41
to
a601b39
Compare
Cluster Generation A/B Results: |
/test install-vc7 |
a601b39
to
0896e22
Compare
Cluster Generation A/B Results: |
/test install-vc7 |
0896e22
to
f809d42
Compare
Cluster Generation A/B Results: |
/test install-vc7 |
Tests failed! Build no: 3561 |
f809d42
to
4c47eb4
Compare
98dd506
to
762860e
Compare
/test install-vc7 |
Cluster Generation A/B Results: |
/test install-vc7 |
/test install-vc7 |
762860e
to
4978716
Compare
Cluster Generation A/B Results: |
/test install-vc7 |
It looks like the tests didn't run the last two times :( |
/test install-vc7 |
4978716
to
b2e5267
Compare
/test install-vc7 |
Cluster Generation A/B Results: |
/test install-vc7 |
Build failed! Build no: 3889 |
/test install-vc7 |
/test install-vc7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Tyler Schultz <tschultz@vmware.com> Co-authored-by: Edwin Xie <exie@vmware.com> Co-authored-by: Christian Ang <angc@vmware.com>
b2e5267
to
cd44e89
Compare
Cluster Generation A/B Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This feature had been feature-flagged because it had unexpected behavior. Previously, when setting custom nameservers, they would not always apply becuase nameservers supplied by DHCP would 'compete' with the configured nameservers. Typically the OS would only apply 3 nameservers and ignoring the rest. This meant that often the addresses supplied by DHCP would take precedence over the configured nameservers. Recent changes, made in PR vmware-tanzu#4023, causes the OS to ignore nameservers supplied from DHCP when using the WORKER_NODE_NAMESERVERS or CONTROL_PLANE_NAMESERVERS variables. Now that the functionality for specifying custom nameservers works as expected, the feature flags can be removed. Co-authored-by: Edwin Xie <exie@vmware.com>
What this PR does / why we need it
When users specify nameservers via CONTROL_PLANE_NODE_NAMESERVERS or WORKER_NODE_NAMESERVERS, CAPV is configured to ignore nameservers configured from DHCP. Without this change nameservers from DHCP will be added to the list of available nameservers.
CAPV v1.5+ was recently bumped, which contains the ability to configure DHCP overrides, so this change can be validated
Which issue(s) this PR fixes
Fixes #1103
Describe testing done for PR
Deployed clusters while using WORKER_NODE_NAMESERVERS and CONTROL_PLANE_NODE_NAMESERVERS and saw that CAPV was correctly configured with the VSphereMachineTemplate
.spec.template.spec.network.dhcpOverrides.useDNS
is set to false. SSH onto node vms and verfiy networkctl is configured correctly.Release note
Additional information
Special notes for your reviewer