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

Add total IP count and available IP count in IPPool.Status #161

Open
jessehu opened this issue Oct 25, 2022 · 13 comments
Open

Add total IP count and available IP count in IPPool.Status #161

jessehu opened this issue Oct 25, 2022 · 13 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@jessehu
Copy link

jessehu commented Oct 25, 2022

User Story

As a developer/user I would like to get the total IP count and available IP count of an IPPool CR by checking its status field.

Detailed Description

[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.]

/kind feature

@metal3-io-bot metal3-io-bot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Oct 25, 2022
@Rozzii
Copy link
Member

Rozzii commented Nov 2, 2022

/cc @lentzi90 @furkatgofurov7 @schrej
What is your opinion?

@schrej
Copy link
Member

schrej commented Nov 2, 2022

I thought about adding that to telekom/cluster-api-ipam-provider-in-cluster, definitely useful.

Maybe also a condition that indicates whether the pool is exhausted. The condition should then be standardized as part of the capi IPAM contract.

@furkatgofurov7
Copy link
Member

furkatgofurov7 commented Nov 2, 2022

+1 from my side

@lentzi90
Copy link
Member

lentzi90 commented Nov 3, 2022

+1

@Rozzii
Copy link
Member

Rozzii commented Nov 16, 2022

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Nov 16, 2022
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 14, 2023
@Rozzii
Copy link
Member

Rozzii commented Feb 15, 2023

@lentzi90 Was there a PR related to this merged ?

@lentzi90
Copy link
Member

I don't think so

@Rozzii
Copy link
Member

Rozzii commented Mar 1, 2023

Is anyone working on this @lentzi90 @furkatgofurov7 @schrej @jessehu ? If nobody is interested atm I will move this to frozen as the feature proposal was already accepted so the feature makes sense .

@jessehu
Copy link
Author

jessehu commented Mar 3, 2023

I'm sorry that no bandwidth for the PR right now.

@furkatgofurov7
Copy link
Member

/remove-lifecycle stale
/help wanted

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2023
@furkatgofurov7
Copy link
Member

cc (note to myself) configure lifecycle frozen on the repo and label it with frozen label.

@furkatgofurov7
Copy link
Member

/lifecycle frozen

@metal3-io-bot metal3-io-bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Mar 15, 2023
@mboukhalfa mboukhalfa moved this from Backlog to IPAM WIP in Metal3 - Roadmap Jun 27, 2024
@mboukhalfa mboukhalfa moved this from IPAM WIP to IPAM on hold / blocked in Metal3 - Roadmap Jun 27, 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/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: IPAM on hold / blocked
Development

No branches or pull requests

6 participants