-
Notifications
You must be signed in to change notification settings - Fork 11
feat: add capacity type node groups to allow for spot nodes #152
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
Conversation
|
@dpappa:Thanks for your contribution. For this PR, do we need to update docs? |
|
@dpappa:Thanks for providing doc info! |
|
@dpappa:Thanks for your contribution. For this PR, do we need to update docs? |
|
@dpappa:Thanks for providing doc info! |
🤖 I have created a release *beep* *boop* --- ## [4.5.0](v4.4.0...v4.5.0) (2025-12-24) ### Features * add capacity type node groups to allow for spot nodes ([#152](#152)) ([eb6f292](eb6f292)) * **iam:** add iam:ListInstanceProfiles permission for karpenter 1.7.0+ ([#171](#171)) ([b49e353](b49e353)) ### Bug Fixes * **iam:** make karpenter and cluster-autoscaler mutual exclusion ([#175](#175)) ([0998bb4](0998bb4)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Motivation
This PR will allow us to specify the capacity type, which is typically "on-demand". There are some instances where we would like to make node groups spot for cost savings on lower level environments.
Modifications
I've exposed the
node_pool_capacity_typewhich allows modification to the capacity types of all node groups created via the eks-managed-node-group submodule.Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Documentation
Check the box below.
Need to update docs?
doc-required(If you need help on updating docs, create a doc issue)
no-need-doc(Please explain why)
doc(If this PR contains doc changes)