Provision IP address in NetBox based on LoadBalancer ingress IP

[christopher-svensson-stegra]

Add a new controller that tracks LoadBalancer Services and keeps matching NetBox IPAddress CRs in sync.

[jstudler]

Thanks so much for the PR and contribution!

To help us better evaluate this, could you share a bit more context? Specifically:

• What problem does this solve for you?
• Why do you think this fits well within NetBox Operator?

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.

[christopher-svensson-stegra]

Reasonable questions!

What problem does this solve for you?

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.

Why do you think this fits well within NetBox Operator?

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.

[jstudler]

Thanks again for your draft PR, looks great and we support having this feature in NetBox Operator. Please add a viper configuration parameter that allows enabling the controller and make sure it's disabled by default. Also, please make sure to add unit tests for the helper functions. Thanks!

[jstudler]

@christopher-svensson-stegra just checking to see if you're still interested in merging this PR?

[jstudler]

Closing due to inactivity. Please reopen if you want to continue work on it.