feat: Add IPAM integration #505
Open
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.
This pull request introduces dynamic IP address allocation for Tinkerbell machines by integrating with Cluster API IPAM providers. The changes add support for specifying an IPAM pool in the machine spec, automatically creating and managing IP address claims, updating hardware resources with allocated IPs, and cleaning up claims on deletion. Comprehensive unit tests for the new IPAM logic have also been added.
IPAM integration and dynamic IP allocation:
IPAMPoolRef
field to theTinkerbellMachineSpec
, allowing users to specify an IPAM pool for dynamic IP address allocation.controller/machine/ipam.go
, including logic for creating IP address claims, updating hardware with allocated IPs, and cleaning up claims.Controller logic enhancements:
scope.go
to handle IPAM pool configuration, trigger IP allocation, and update hardware resources accordingly.IPAddressClaim
if IPAM was configured, ensuring proper resource cleanup. [1] [2]Testing improvements:
ipam_test.go
to cover netmask conversion, hardware patching, and IPAM pool reference extraction, improving reliability and maintainability of the new IPAM logic.## DescriptionFixes: #
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: