Conversation
0dcfd63 to
b33eb28
Compare
There was a problem hiding this comment.
Thanks for this, @appkins. I actually tried to use ko but i couldn't get it to allow overwriting the registry. I'd also prefer the changes to the build and release process be a separate PR. I'll start reviewing the rest of the PR. Thanks again for this!
601847e to
8661d4b
Compare
- Added RBAC rules - Fixed reconcile Signed-off-by: appkins <nbatkins@gmail.com>
All ko related changes are removed and will be in a new PR shortly. |
|
Hey @appkins, I tried running this with the CAPT playground and got a bunch of nil pointer errors. I threw in some fixes for nil values but then ended up with errors around |
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:
IPAMPoolReffield 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.goto handle IPAM pool configuration, trigger IP allocation, and update hardware resources accordingly.IPAddressClaimif IPAM was configured, ensuring proper resource cleanup. [1] [2]Testing improvements:
ipam_test.goto 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: