Skip to content

Provision IP address in NetBox based on LoadBalancer ingress IP#507

Open
christopher-svensson-stegra wants to merge 1 commit intonetbox-community:mainfrom
christopher-svensson-stegra:create-ip-address-from-load-balancers
Open

Provision IP address in NetBox based on LoadBalancer ingress IP#507
christopher-svensson-stegra wants to merge 1 commit intonetbox-community:mainfrom
christopher-svensson-stegra:create-ip-address-from-load-balancers

Conversation

@christopher-svensson-stegra

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

Signed-off-by: Christopher Svensson <christopher.svensson@stegra.com>
@jstudler
Copy link
Collaborator

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
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants