Support karpenter 0.32+ #368
Merged
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
shimpeko
approved these changes
Jul 18, 2024
Karpenter 0.32 introduces new v1beta apis and depricates the existing v1alpha apis. These APIs require a different IAM policy for the controler to work. This PR adds 2 new variables to the karpenter module. `v1alpha` and `v1beta` which will allow one or both policies to be used (useful during the migration process) We will enable both policies by default in the 1.28 release, then drop support for the `v1alpha` policy in 1.30 (as karpenter 1.31 doesn't work properly with k8s 1.30).
errm
force-pushed
the
errm/support-karpenter-0-32
branch
from
8570166 to
75851a3
Compare
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.
Karpenter 0.32 introduces new v1beta apis and depricates the existing v1alpha apis.
🔗 https://karpenter.sh/v0.32/upgrading/v1beta1-migration/#upgrade-procedure
These APIs require a different IAM policy for the controler to work.
This PR adds 2 new variables to the karpenter module.
v1alphaandv1betawhich will allow one or both policies to be used (useful during the migration process)We will enable both policies by default in the 1.28 release, then drop support for the
v1alphapolicy in 1.30 (as karpenter 1.31 doesn't work properly with k8s 1.30).