[api] allow specifying pod tolerations #111
Merged
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.
Some users wish to use taints/tolerations to pin M3DB instances to
dedicated nodes, and keep other pods off of them. This allows specifying
tolerations in the cluster spec.
Note that we currently allow specifying tolerations on the cluster level
and not the
isolationgroup
level, as it seems like most common usecases would be setting aside nodes for M3DB using a single taint rather
than a per-zone taint. If user requests for per-isogroup tolerations
arise we can reconsider.