Skip to content

fix: Force node group replacement - #196

Open
zacharyblasczyk wants to merge 1 commit into
mainfrom
zacharyb/node-group-replacement
Open

fix: Force node group replacement#196
zacharyblasczyk wants to merge 1 commit into
mainfrom
zacharyb/node-group-replacement

Conversation

@zacharyblasczyk

Copy link
Copy Markdown
Contributor

This causes 60 seconds of downtime.

@zacharyblasczyk
zacharyblasczyk requested a review from gls4 as a code owner March 26, 2024 23:52
@zacharyblasczyk zacharyblasczyk changed the title Force node group replacement fix: Force node group replacement Mar 29, 2024

@gls4 gls4 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this definitively solve the issue (which is that we can't alter the desired_size specified in the EKS module once the cluster has been created).

I know this will work on new clusters, but has this been tested on existing clusters?

Do consecutive changes to the max size take effect when applied?

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.

2 participants