Provision IP address in NetBox based on LoadBalancer ingress IP#507
Conversation
Signed-off-by: Christopher Svensson <christopher.svensson@stegra.com>
|
Thanks so much for the PR and contribution! To help us better evaluate this, could you share a bit more context? Specifically:
We’re still determining whether features like this should live in the main codebase or as a separate project, so understanding your use case will help us make that decision. |
|
Reasonable questions!
In our case we need the IP addresses that Cilium hands out to be present in NetBox, to be able to target a certain application/service from Terraform for example. While this could also be realized through something like external-dns we figured there's also a certain value of keeping NetBox the source of truth.
I reckon that the nature of this controller might deviate a bit from the others, as this one actually creates a CR instead of just reacting to one. Another approach would of course be to have a simple container running that based on Service object events creates the NetBox CRs. |
Add a new controller that tracks LoadBalancer Services and keeps matching NetBox
IPAddressCRs in sync.