Robert Ruf

/lifecycle frozen

@srm09 I can write a docs draft for the quickstart.md on how to assign static IPs if that's what you're asking.

Sure. I'll schedule some time for it this weekend. Will link the PR to this issue when done.

@sathieu I'm not sure but I doubt it since the preKubeadmCommand is executed after the node is reachable (thus, has a IP). The management cluster communicates the IPs to vSphere...

@Cellebyte do you have a working IPAM solution with CAPV or are you patching in static IPs?

> We've built a small custom controller that interfaces with Infoblox which is available here. You got that working with the "wait until static IP is available" behaviour CAPV offers...

> > > @omniproc for IPaddresses there is some kind of same CRD which we use for our general purpose CNI. > > It has the following CRDs. > >...

> Our current approach is similar to the spectrocloud one, it just directly talks to Infoblox instead of interfacing with metal3-ip-address-manager. It relies on CAPV waiting for the IP and...

@Cellebyte according to @jzhoucliqr [this spectrocloud implementation I refered to earlier](https://github.com/spectrocloud/cluster-api-provider-vsphere-static-ip ) is going to be merged with upstream CAPV, see #728

> No, it's not. They were referring to spectrocloud/cluster-api-provider-vsphere-static-ip#26, which adds support for v1alpha4 to their implementation. Oh sorry, you're right. I got that wrong. In that case forget what...