-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Events+weighted borrowing #128974
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
Events+weighted borrowing #128974
Conversation
Signed-off-by: Mike Spreitzer <mspreitz@us.ibm.com>
Signed-off-by: Mike Spreitzer <mspreitz@us.ibm.com>
Signed-off-by: Mike Spreitzer <mspreitz@us.ibm.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: MikeSpreitzer The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cc @linxiulei |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
Trying out kubernetes/enhancements#4978 Signed-off-by: Mike Spreitzer <mspreitz@us.ibm.com>
371e5ad
to
863c90b
Compare
/test pull-kubernetes-e2e-gce-100-performance |
See https://docs.google.com/document/d/1C0sCkHqnWCHWlDuXvtM_2A72kZnIsFWKdRcXf4wT9js for a study of the Prometheus metrics from the pull-kubernetes-e2e-gce-100-performance run https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/128974/pull-kubernetes-e2e-gce-100-performance/1861315292341211136 |
Limited: &flowcontrol.LimitedPriorityLevelConfiguration{ | ||
NominalConcurrencyShares: ptr.To(int32(5)), | ||
LendablePercent: ptr.To(int32(0)), | ||
BorrowingLimitPercent: ptr.To(int32(100)), |
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.
Do we still need borrowing limit with weighted borrowing feature?
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.
Yes, I think so. For example, this makes it possible to "jail" some requests to a priority level with a fixed (over time, for a given sever) upper limit.
Subjects: groups(user.AllAuthenticated), // the nodes group | ||
ResourceRules: []flowcontrol.ResourcePolicyRule{ | ||
resourceRule( | ||
[]string{"create", "update", "delete"}, |
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.
Event client does use Patch requests for EventSeries https://github.com/kubernetes/client-go/blob/master/tools/events/event_broadcaster.go#L240
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.
Good catch. Fixed here and in #129008
/triage accepted |
Signed-off-by: Mike Spreitzer <mspreitz@us.ibm.com>
See https://docs.google.com/document/d/1Px2fEiYWG9YPlLpt13ko0L-fNmwmO9AFVnN4YoZ3PVQ for graphs for a trial that @linxiulei did on Dec 1. |
PRs to compare:
Also see:
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR updates the default API Priority and Fairness configuration to have a FlowSchema and a corresponding priority level for events. This is a draft implementation of kubernetes/enhancements#4978.
This is built on #128087.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: