Set DHCP relay sourceInterface from LoadBalancerInterface config #10421
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
https://github.com/aws/eks-anywhere-internal/issues/3731
Description of changes:
Set DHCP relay sourceInterface from LoadBalancerInterface config.
When LoadBalancerInterface is configured in TinkerbellDatacenterConfig, propagate the same interface to the DHCP relay's sourceInterface. This ensures the relay listens for DHCP broadcasts on the correct network interface where bare metal machines are located.
Previously only kube-vip used this interface setting, leaving the relay to auto-detect which could pick the wrong interface in multi-NIC setups.
Testing (if applicable):
Specified a dummy interface in
loadbalancerinterfacein TinkerbellDatacenterConfig and tried to create a cluster and verified that relay has the specified interface in the argsBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.