Optional floating IPs in cluster machines

[bartekle]

/kind feature

Describe the solution you'd like
Possibility to associate floating IP with default port of cluster machine.

Anything else you would like to add:
This feature may be redundant in case of debuging and bastion host availability, but floating IP is also used as egress strategy - node has other, specific network path rather than default network nodes.

[mdbooth]

Is this different to the functionality provided by the floating IP IPAM provider?

/cc @huxcrux

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[huxcrux]

Is this different to the functionality provided by the floating IP IPAM provider?

/cc @huxcrux

A late reply but yes sounds like exactly what the FIP IPAM provides :)

So it should just be to create a Pool: https://cluster-api-openstack.sigs.k8s.io/api/v1alpha1/api#infrastructure.cluster.x-k8s.io/v1alpha1.OpenStackFloatingIPPool

And then refer to it in the OpenStackMachineTemplate by setting floatingIPPoolRef to point towards the pool.

Just be aware that the pool will create new FIPs by default meaning if you want to use an IP already in the project/tenant it needs to be added to the spec by setting preAllocatedFloatingIPs (a list).

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten