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

[api] allow specifying pod tolerations #111

Merged
merged 1 commit into from
Apr 8, 2019
Merged

Conversation

schallert
Copy link
Collaborator

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 use
cases 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.

@codecov
Copy link

codecov bot commented Apr 3, 2019

Codecov Report

Merging #111 into master will increase coverage by 0.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #111      +/-   ##
==========================================
+ Coverage   68.55%   68.56%   +0.01%     
==========================================
  Files          26       26              
  Lines        1873     1874       +1     
==========================================
+ Hits         1284     1285       +1     
  Misses        489      489              
  Partials      100      100

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 61d54d0...9af4f40. Read the comment docs.

@schallert schallert marked this pull request as ready for review April 3, 2019 20:31
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 use
cases 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.
@schallert schallert merged commit 4531661 into master Apr 8, 2019
@schallert schallert deleted the schallert/tolerations branch April 8, 2019 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant