plugin/kubernetes: rate limits to api server#7771
Merged
Merged
Conversation
2658266 to
ad559aa
Compare
Signed-off-by: pasteley <ceasebeing@gmail.com>
ad559aa to
84fab77
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
1. Why is this pull request needed and what does it do?
This adds optional configuration knobs to the
kubernetesplugin to limit load on the Kubernetes API server, which allows to prevent CoreDNS from overwhelming it in large clusters or under high DNS load.2. Which issues (if any) are related?
None I am aware of
3. Which documentation changes (if any) need to be made?
Updated
kubernetesplugin doc with new directives4. Does this introduce a backward incompatible change or deprecation?
No