-
Notifications
You must be signed in to change notification settings - Fork 979
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
document Karpenter's reaction to taints/tolerations #659
Comments
I'll read #628 before asking any further questions there. |
We desperately need to publish docs for this. They are currently WIP. This is the best explanation I can give (if you can read go). https://github.com/awslabs/karpenter/blob/main/pkg/controllers/allocation/scheduling/taints.go#L26. Feel free to contact me on Kubernetes slack for quick questions. |
Thanks @ellistarn. I was specifically thinking about the |
Hey @stevehipwell, I've temporarily removed taint generation from karpenter (for our next release). I'm currently leaning towards a solution of only tainting nodes for tolerations with the key Does this make sense to you? |
@ellistarn this makes a lot of sense to me. I like the fact that we're talking "isolation" and that the taints and labels are just the implementation. I assume there is still the ability to define static taints and labels on a provisioner? |
Correct! |
as of #643, Karpenter will "Generate matching taints on nodes for pods that contain tolerations"
This behavior should be added to the docs.
The text was updated successfully, but these errors were encountered: