Added toleration support for iam operator jupyter #18
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
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.
At Anaconda, we have deployed the datalayer stack into a shared tenant cluster and are using karpenter to manage our various nodepools. Because the datalayer nodepool doesn't currently specify any taints on the nodes that come up, pods from other services are able to be scheduled on it and we are now hitting some limits.
By introducing tolerations here, I will be able to introduce taints to datalayer nodes in our cluster and simultaneously make datalayer pods immune to its effects thereby only allowing datalayer pods to be schedulable on the nodes.
k8s doc for taints/tolerations: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/