ironcore-dev / ironcore-dev/FeDHCP
Add support for CAPI IPAM
Open
Nobody has claimed this yet.
area/metal-automation
enhancement
- Dominant language
- Go
- Stars
- 3
- Forks
- 8
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 7
Description
Summary
Instead of relying only on our home grown IPAM solution we might think about integrating: https://github.com/kubernetes-sigs/cluster-api/tree/main/api/ipam/v1beta2 to manage IP addresses in FeDHCP.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing FeDHCP’s existing home-grown IPAM implementation and the Kubernetes Cluster API IPAM v1beta2 API linked in the issue. Determine the integration boundaries and how FeDHCP should manage IP addresses through CAPI; done means a concrete, tested integration plan or implementation with compatible IPAM behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100