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
Introduce apiserver_flowcontrol_current_executing_seats metric #118960
Introduce apiserver_flowcontrol_current_executing_seats metric #118960
Conversation
/cc @wojtek-t |
/assign @wojtek-t |
/retest |
1 similar comment
/retest |
/assign @dgrisonnet - for the review from SIG instrucmentation POV |
This LGTM, but I would like @dgrisonnet to look to for newly introduced metric. |
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.
IMO the safest path forward here, is to:
- Mark
apiserver_flowcontrol_request_concurrency_in_use
as deprecated in 1.28 - Continue to set
apiserver_flowcontrol_request_concurrency_in_use
in 1.28 so that we don't break users right away and leave them one release to update - We remove
apiserver_flowcontrol_request_concurrency_in_use
in 1.29
So the only additional thing I would want in this PR is to set |
This is a duplicate of `apiserver_flowcontrol_request_concurrency_in_use` but with a better name. Hopefully we can later remove the copy with the inferior name. Signed-off-by: Mike Spreitzer <mspreitz@us.ibm.com>
55918a7
to
65e818d
Compare
The force-push to 65e818d adds that Since #118882 is also in flight, perhaps we should mark |
Let's do that in a separate PR. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MikeSpreitzer, wojtek-t The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Actually - wait.. /lgtm cancel |
No.. it's fine. /lgtm |
LGTM label has been added. Git tree hash: a3f1628ab24f8f9d3bce0b015f9abbfadb649186
|
This is a duplicate of
apiserver_flowcontrol_request_concurrency_in_use
but with a better name. Hopefully we can later remove the copy with the inferior name.What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR introduces the
apiserver_flowcontrol_current_executing_seats
metric, as a duplicate of theapiserver_flowcontrol_request_concurrency_in_use
metric --- because the latter has a confusing name and I hope to delete it later.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.: