Merge upstream Release v0.194.0 ,Con 22743 add aggressive scale down#671
Merged
yehielnetapp merged 789 commits intofeat-spot-oceanfrom Nov 13, 2024
Merged
Merge upstream Release v0.194.0 ,Con 22743 add aggressive scale down#671yehielnetapp merged 789 commits intofeat-spot-oceanfrom
yehielnetapp merged 789 commits intofeat-spot-oceanfrom
Conversation
Prepare for next development iteration
…rade Upgrade Bottlerocket node with explicit `Version` field
* Add release notes for v0.175.0 * remove empty acknowledgements section --------- Co-authored-by: yuxiang-zhang <[email protected]> Co-authored-by: Tibi <[email protected]>
* bump dependencies * update mocks * fix lint * bump helm
ensure namespace uniqueness across parallel specs
Include MixedInstancesPolicy LaunchTemplate for validation
* allow GPU instance type for Windows nodes * update unit test for case gpus:0
Update release-drafter.yaml
bump mkdocs version
* add support for AL2023 for EKS-managed and self-managed nodes * ensure AL2023 only supports containerd * add GPU related validations + small nits * add support for upgrades * add support for EFA * improve validations * fix lint and unit tests * update docs * add validation error for maxpods limitation * add integration tests for al2023 * improve validation message
…-auth configmap` when EKS access entries are disabled (eksctl-io#7698) * Disable access entry creation for self-managed nodes on clusters with CONFIG_MAP only * fix logic for updating aws-auth configmap
Make authenticationMode:CONFIG_MAP default on Outposts
Co-authored-by: TiberiuGC <[email protected]>
Prepare for next development iteration
Bump dependencies
Bump dependencies
Fix arn build logic to support different aws partitions
…ries This changelist changes the design of creating access entries for self-managed nodegroups that use a pre-existing instanceRoleARN by creating the access entry resource outside of the CloudFormation stack by making a separate call to the AWS API. When deleting such a nodegroup, it's the user's responsibility to also delete the corresponding access entry when no more nodegroups are associated with it. This is because eksctl cannot tell if an access entry resource is still in use by non-eksctl created self-managed nodegroups. Self-managed nodegroups not using a pre-existing instanceRoleARN will continue to have the access entry resource in the CloudFormation stack, making delete nodegroup an atomic operation for most use cases. Fixes eksctl-io#7502
add support for EKS accelerated AMIs based on AL2023
Co-authored-by: TiberiuGC <[email protected]>
Signed-off-by: cpu1 <[email protected]>
Add support for M8g instance types
Correct the description of version drift during upgrade to match the current kubernetes documentation. Node version should not be newer than the cluster version.
Documentation: correct version drift limits in cluster-upgrade.md
Add release notes for v0.193.0
Prepare for next development iteration
…ncer Controller v2.9.0
…-listener-attributes-actions Fix missing ELB listener attribute actions required for AWS Load Balancer Controller v2.9.0
Signed-off-by: cpu1 <[email protected]>
Signed-off-by: cpu1 <[email protected]>
Support EKS zonal shift config
Add release notes for v0.194.0
…aggressiveScaleDown
yehielnetapp
changed the title
oded7hoffman
approved these changes
Nov 13, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 participants
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.
Description
Checklist
README.md, or theuserdocsdirectory)area/nodegroup) and kind (e.g.kind/improvement)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯