Adding self taint toleration for wasp-agent deployment #75
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.
Signed-off-by: Igor Bezukh [email protected]
When node is under pressure and we evict pods, we also taint the node. If for some reason wasp-agent would be restarted, the wasp-agent pod won't be able to run on a tainted node.
This is bad since wasp-agent needs to complete the eviction process, and clear the taint as far as node resources are stable again.