Closed otterley closed 2 years ago
Waiting for this
We will have a look shortly. @youngjeong46
@otterley - I'm working through this for a PR and have taints implemented in my working branch so far.
For the second part of your request, are you referring to support for multiple providers or multiple provisioners?
Provisioners - sorry for the confusion.
I figured as much, but wanted to confirm. Thanks!
Describe the feature
Support node taints and multiple provisioners in the Karpenter add-on.
Use Case
Taints are the key mechanism by which Karpenter can select which Provisioner should be associated with a scheduled Pod. Without support for such taints, only one Provisioner associated with a cluster will ever be used.
For example, the customer might want to schedule some pods only onto instances with GPUs.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
-
EKS Blueprints Version
No response
Node.js Version
-
Environment details (OS name and version, etc.)
-