-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
docs(quota plugins): note on quotas for internal users #10803
docs(quota plugins): note on quotas for internal users #10803
Conversation
Signed-off-by: prmellor <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, I made one dodgy suggestion, and would ask the question:
how do you monitor the situation to avoid trottling?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks.
Signed-off-by: prmellor <[email protected]>
Signed-off-by: prmellor <[email protected]>
Signed-off-by: prmellor <[email protected]>
Signed-off-by: prmellor <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left one nit, but this looks reasonable to me.
Signed-off-by: prmellor <[email protected]>
Thanks @kyguy -- I've expanded on the potential impact to the TO operations as suggested. |
Documentation
Adds a description of the impact on internal users when applying quotas through the Kafka quotas plugin.
Describes how Topic Operator and Cruise Control operations can be affected and how to avoid any impact.
Checklist
Please go through this checklist and make sure all applicable tasks have been done