-
Notifications
You must be signed in to change notification settings - Fork 981
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
feat: Add support for custom ssm parameters in amiSelectorTerms #7341
base: main
Are you sure you want to change the base?
feat: Add support for custom ssm parameters in amiSelectorTerms #7341
Conversation
✅ Deploy Preview for karpenter-docs-prod ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
6ff77e6
to
b0d3183
Compare
This PR has been inactive for 14 days. StaleBot will close this stale PR after 14 more days of inactivity. |
9347ba5
to
ee3fd83
Compare
/remove-lifecycle stale |
Hey @wesley-yep-canva sorry that it's taken us so long to get around to this stuff :) Team has been pretty back-logged. Since this is a feature, there's also going to be some discussion around it I think. |
Fixes #3657
Description
Adds
ssmParameterName
toamiSelectorTerms
to allow Karpenter to read a custom ssm parameter to get the AMI Image ID.Karpenter already has ssm parameter IAM permissions and a ssm provider class as it's used to retrieve the public ssm params for alias based amiSelectorTerms. The reason I've added a separate function
GetCustomParameter
to the ssm provider is because we'd prefer not to use the cache for custom parameters, since it won't suffer from the same "thundering herd" behavior compared to if a public parameter was changed.How was this change tested?
make test
Does this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.