fix(kubereserved): allow custom AMI bypass and floor kubeReserved to … #8705
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…min(maxPods, ENI limit) per #8497
Fixes #N/A
Description
NewInstanceTypelogic to respect these behaviors for Custom AMIs.This change provides flexibility for Custom AMI users and improves accuracy in allocable estimation when user-defined
maxPodsis lower than the ENI limit.-This PR focuses on logic correctness and configurability.
-If approved, follow-up PRs can adjust test expectations and documentation for
kubeReservedbehavior in Custom AMI families.How was this change tested?
Local test suite executed under envtest:
go vetandgo fmtare clean.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.