Skip to content
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

Open
bartekle opened this issue Jul 4, 2024 · 4 comments
Open

Optional floating IPs in cluster machines #2140

bartekle opened this issue Jul 4, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@bartekle
Copy link

bartekle commented Jul 4, 2024

/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.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 4, 2024
@mdbooth
Copy link
Contributor

mdbooth commented Jul 15, 2024

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

/cc @huxcrux

@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 13, 2024
@huxcrux
Copy link
Contributor

huxcrux commented Oct 16, 2024

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

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
Status: Inbox
Development

No branches or pull requests

5 participants