Skip to content
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

Closed
geoffcline opened this issue Sep 7, 2021 · 6 comments · Fixed by #845
Closed

document Karpenter's reaction to taints/tolerations #659

geoffcline opened this issue Sep 7, 2021 · 6 comments · Fixed by #845
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@geoffcline
Copy link
Contributor

geoffcline commented Sep 7, 2021

as of #643, Karpenter will "Generate matching taints on nodes for pods that contain tolerations"

This behavior should be added to the docs.

@geoffcline geoffcline changed the title document taints; document Karpenter's reaction to taints/tolerations Sep 7, 2021
@geoffcline geoffcline added the documentation Improvements or additions to documentation label Sep 7, 2021
@geoffcline geoffcline self-assigned this Sep 7, 2021
@stevehipwell
Copy link
Contributor

stevehipwell commented Nov 4, 2021

Are there always ignored taints and customisable ignored taints?

I'll read #628 before asking any further questions there.

@ellistarn
Copy link
Contributor

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.

@stevehipwell
Copy link
Contributor

Thanks @ellistarn. I was specifically thinking about the CriticalAddonsOnly=true:NoSchedule taint which gets added to EKS nodes and shows up in a number of AWS Helm charts by default.

@ellistarn
Copy link
Contributor

ellistarn commented Nov 23, 2021

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 karpenter.sh/isolation. Similarly, we would generate labels for the same label key. This avoids the undesirable taint generation you mentioned above. It also helps avoid confusing behavior from typos in label generation like node.kubernetes.i/instance-type.

Does this make sense to you?

@stevehipwell
Copy link
Contributor

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 karpenter.sh/isolation. Similarly, we would generate labels for the same label key. This avoids the undesirable taint generation you mentioned above. It also helps avoid confusing behavior from typos in label generation like node.kubernetes.i/instance-type.

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?

@ellistarn
Copy link
Contributor

Correct!

@geoffcline geoffcline linked a pull request Nov 24, 2021 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants