Skip to content

IPAM support for CAPO #1377

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

Closed
1 task
geetikabatra opened this issue Nov 10, 2022 · 9 comments
Closed
1 task

IPAM support for CAPO #1377

geetikabatra opened this issue Nov 10, 2022 · 9 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@geetikabatra
Copy link

/kind feature
Umbrella issue for all tasks required to implement IPAM support for CAPO
This issue will be updated over time

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 10, 2022
@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 Feb 8, 2023
@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 Mar 10, 2023
@hiromu-a5a
Copy link

Hi, I am interested in this feature. Is there any roadmap for the implementation?

@mdbooth
Copy link
Contributor

mdbooth commented Mar 15, 2023

There is not, but I am also interested in it.

Out of curiosity, what is your use case? Why is this better than DHCP in your circumstances?

@huxcrux
Copy link
Contributor

huxcrux commented Mar 22, 2023

I could se this being used to manage public IPs. I currently looking into the possibility of having a list(or range) of public IP-addresses that could be assigned to workers. The reasons for this is to have a known source IP on each worker allowing for whitelisting at a 3rd party.

I'm willing looking into implementing the IPAM API however it would be good to know what use cases others have.

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 22, 2023
@hiromu-a5a
Copy link

Sorry for the delayed response.
For some historical reasons, our environment uses many fixed IPs, and IPs are used to connect services that are geographically isolated. We need to be aware of which IPs are used in which machines and by which services. DHCP is not enough to cover this use case.

@mdbooth
Copy link
Contributor

mdbooth commented Apr 13, 2023

Example use in CAPV: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/a5feda0b204f3351da0c16ba8cde82921d434025/apis/v1beta1/types.go#L321-L325

@mdbooth mdbooth added the tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open. label May 4, 2023
@mdbooth mdbooth moved this to Todo in CAPO Roadmap May 4, 2023
@mdbooth mdbooth removed the tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open. label May 5, 2023
@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 Jan 19, 2024
@mdbooth
Copy link
Contributor

mdbooth commented Jan 30, 2024

Tracked in #1750

@mdbooth mdbooth closed this as completed Jan 30, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in CAPO Roadmap Jan 30, 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/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
Archived in project
Development

No branches or pull requests

6 participants