Backport cluster critial fargate profiles + karpenter module #352
Conversation
This file contains 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
This feature is backported to 1.24 to ease the upgrade process to 1.25 By upgrading to the latest 1.24 module version we can add the fargate profile before the cluster critical autoscaling group is removed.
Allows karpenter to be installed or updated before upgrading a cluster to 1.25
errm
force-pushed
the
errm/backport-karpenter
branch
from
5062a19
to
38fd07b
Compare
errm
added a commit
that referenced
this pull request
Oct 31, 2023
This config was missing from #352
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backporting these features to 1.24 makes the upgrade process to the 1.25 module much simpler.
This way we can ensure that the fargate profiles for cluster critical workloads (and karpenter) are setup properly before the ASG managed nodes they ran on previously are removed!