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.
This is a big change, not intentionally intended
It originally started by adding the Taint & Toleration feature to AgnosticS.
listening address of both servers.
DELETE /taint/{cloudName}/{taintIndex}
)DELETE /taints/{cloudName}
)policy.yaml
file that describes the behavior of the scheduler. Itis similar to the OpenShift scheduler policy configmap.
[]Taint
instead ofmap[string]Taint
)JSON. Notify other frontends on the taintMQ channel when a change happens.
[]cloud
and not amap. They should be identical so the order can be changed in the
policy.yaml
config indifferently.