Skip to content

fix: avoid selecting subnets with insufficient available IP address#7310

Closed
Vacant2333 wants to merge 1 commit intoaws:mainfrom
Vacant2333:feat-select-the-most-availalbe-ip-count-subnet
Closed

fix: avoid selecting subnets with insufficient available IP address#7310
Vacant2333 wants to merge 1 commit intoaws:mainfrom
Vacant2333:feat-select-the-most-availalbe-ip-count-subnet

Conversation

@Vacant2333
Copy link
Copy Markdown
Contributor

@Vacant2333 Vacant2333 commented Nov 1, 2024

Fixes #5234
#2921

Description
its a feature that when launchInstance select the subnet which has the most available ip count.

How was this change tested?

Does this change impact docs?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@Vacant2333 Vacant2333 requested a review from a team as a code owner November 1, 2024 09:02
@Vacant2333 Vacant2333 requested a review from jmdeal November 1, 2024 09:02
@netlify
Copy link
Copy Markdown

netlify bot commented Nov 1, 2024

Deploy Preview for karpenter-docs-prod canceled.

Name Link
🔨 Latest commit 66d3323
🔍 Latest deploy log https://app.netlify.com/sites/karpenter-docs-prod/deploys/67919f76ae3b830008907692

@Vacant2333 Vacant2333 force-pushed the feat-select-the-most-availalbe-ip-count-subnet branch from 22ed451 to 4348646 Compare November 1, 2024 09:15
@Vacant2333 Vacant2333 changed the title [WIP]feat: select the most available ip count subnet when launchInstance fix: avoid selecting subnets with insufficient available IP address Nov 1, 2024
@Vacant2333
Copy link
Copy Markdown
Contributor Author

@jmdeal @jonathan-innis hi, can u help me review, this pr will resolve the issue #5234

@github-actions
Copy link
Copy Markdown
Contributor

This PR has been inactive for 14 days. StaleBot will close this stale PR after 14 more days of inactivity.

@Vacant2333 Vacant2333 force-pushed the feat-select-the-most-availalbe-ip-count-subnet branch from 4348646 to d120906 Compare November 26, 2024 02:02
@Vacant2333
Copy link
Copy Markdown
Contributor Author

@jmdeal can u help me reveiw? thanks

@Talbalash-legit
Copy link
Copy Markdown
Contributor

@rschalo I know you're incredibly busy, but this PR would be a game-changer for us. It addresses the persistent issue we've been struggling with in #5234, and getting it merged would genuinely make a world of difference for our team. We're counting on your expertise to give it the green light. Thank you so much for considering this 🙏

@rschalo
Copy link
Copy Markdown
Contributor

rschalo commented Dec 16, 2024

Hi All - there is not currently a unit test around this behavior. Could we add one where we assert a subnet is no longer considered if IP exhaustion is expected? From a quick look I think it'd be tested via targeting one zone in a test for InstanceProvider create and an with update to the mock EC2 provider that adds a subnet with 0 available IPs for the targeted zone but not sure how that affects other tests.

@github-actions
Copy link
Copy Markdown
Contributor

This PR has been inactive for 14 days. StaleBot will close this stale PR after 14 more days of inactivity.

@Talbalash-legit
Copy link
Copy Markdown
Contributor

Hey can we have an update on this please? 🙏 @rschalo

@saurav-agarwalla
Copy link
Copy Markdown
Contributor

/assign

@saurav-agarwalla
Copy link
Copy Markdown
Contributor

Can we bring in #7549 to this PR? Related changes should be a part of the same PR.

Can you please also address the errors flagged by the CI?

Signed-off-by: Vacant2333 <vacant2333@gmail.com>
@Vacant2333 Vacant2333 force-pushed the feat-select-the-most-availalbe-ip-count-subnet branch from 390c0d6 to 66d3323 Compare January 23, 2025 01:46
@Vacant2333
Copy link
Copy Markdown
Contributor Author

Can we bring in #7549 to this PR? Related changes should be a part of the same PR.

Can you please also address the errors flagged by the CI?

Hello @saurav-agarwalla ! I’m inviting the author of #7549 to co-edit this PR with me. I’ve already addressed your comments and fixed the CI issues. Thank you for helping me move this PR forward!

@saurav-agarwalla
Copy link
Copy Markdown
Contributor

Closing this in favor of #7623 so that we can track the discussions in a single thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Avoid subnets that don't have available IP Addresses

4 participants