-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Promote kube-apiserver flowcontrol metrics to Beta #119110
Conversation
/hold On-going discussion in #118882 |
/triage accepted |
I have updated #118959 to deprecate rather than remove |
@@ -227,7 +227,7 @@ var ( | |||
Subsystem: subsystem, | |||
Name: "request_concurrency_limit", | |||
Help: "Shared concurrency limit in the API Priority and Fairness subsystem", | |||
StabilityLevel: compbasemetrics.ALPHA, | |||
StabilityLevel: compbasemetrics.BETA, |
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.
Since we are deprecating this metric and plan to delete it, I think that we should promote the equal metric apiserver_flowcontrol_nominal_limit_seats
to BETA instead of this one.
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.
Kept this as alpha and updated nominal_limit_seats
to BETA
@@ -247,7 +247,7 @@ var ( | |||
Subsystem: subsystem, | |||
Name: "request_concurrency_in_use", | |||
Help: "Concurrency (number of seats) occupied by the currently executing (initial stage for a WATCH, any stage otherwise) requests in the API Priority and Fairness subsystem", | |||
StabilityLevel: compbasemetrics.ALPHA, | |||
StabilityLevel: compbasemetrics.BETA, |
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.
Since we plan to deprecate and remove this metric, and the equal metric apiserver_flowcontrol_current_executing_seats
is available (since #118960), I think that the latter should become BETA rather than the former.
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.
This has been resolved (and GitHub moved the comment to the resolution!)
3819c47
to
875326a
Compare
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.
@wojtek-t @MikeSpreitzer I updated the PR to leave request_concurrency_in_use
as ALPHA and promote nominal_limit_seats
to BETA. PTAL
@@ -227,7 +227,7 @@ var ( | |||
Subsystem: subsystem, | |||
Name: "request_concurrency_limit", | |||
Help: "Shared concurrency limit in the API Priority and Fairness subsystem", | |||
StabilityLevel: compbasemetrics.ALPHA, | |||
StabilityLevel: compbasemetrics.BETA, |
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.
Kept this as alpha and updated nominal_limit_seats
to BETA
apiserver_flowcontrol_request_wait_duration_seconds apiserver_flowcontrol_request_concurrency_in_use apiserver_flowcontrol_request_concurrency_limit apiserver_flowcontrol_rejected_requests_total apiserver_flowcontrol_dispatched_requests_total apiserver_flowcontrol_current_inqueue_requests apiserver_flowcontrol_current_executing_requests Signed-off-by: Andrew Sy Kim <[email protected]>
875326a
to
0bb419b
Compare
/assign @wojtek-t @MikeSpreitzer |
Signed-off-by: Andrew Sy Kim <[email protected]>
This PR may require stable metrics review. Stable metrics are guaranteed to not change. Please review the documentation for the requirements and lifecycle of stable metrics and ensure that your metrics meet these guidelines. |
/assign @dgrisonnet /retest |
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
LGTM label has been added. Git tree hash: 63d5fa0aa328eb6080a5557ce4a65db3b9a8c783
|
@andrewsykim : I think you can remove the hold here, we have agreed on what to do. |
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.
/hold cancel
/assign @logicalhan |
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
/approve
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewsykim, dgrisonnet, logicalhan, MikeSpreitzer 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 |
/retest |
LGTM |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Promote the following apiserver flowcontrol metrics to Beta:
apiserver_flowcontrol_request_wait_duration_seconds
apiserver_flowcontrol_current_executing_seats
apiserver_flowcontrol_nominal_limit_seats
apiserver_flowcontrol_rejected_requests_total
apiserver_flowcontrol_dispatched_requests_total
apiserver_flowcontrol_current_inqueue_requests
apiserver_flowcontrol_current_executing_requests
These metrics have been around for a while and are very valuable in monitoring flowcontrol state in apiserver.
Which issue(s) this PR fixes:
Fixes #118882
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: