[api] expand node affinity; support multiple reqs #131
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.
Previously we supported node affinity by either 1) using the default
heuristic of the isolation group name being the zone, or 2) by
specifying a single key and a set of values to match an m3db pod to a
node.
This limits users from specifying more complex terms such as "nodes in
zone A with instance type 'large'".
This change allows users to specify multiple node affinity terms, as
well as specifying none at all if they have no need for node affinity.
This is a breaking change as users must specify the zone key in their
cluster configs to get the same zone affinity as before, and this will
be called out in the release notes.
Eventually we'll add the ability to specify entire affinity terms per
isolation-group, but those can be extremely verbose and this still
provides a nice shortcut for most use cases.