-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optional floating IPs in cluster machines #2140
Comments
Is this different to the functionality provided by the floating IP IPAM provider? /cc @huxcrux |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
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). |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/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.
The text was updated successfully, but these errors were encountered: