-
Notifications
You must be signed in to change notification settings - Fork 40.6k
Promote automatic_reloads of authn config metrics to BETA #131798
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 automatic_reloads of authn config metrics to BETA #131798
Conversation
/assign enj liggitt |
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. |
/lgtm |
LGTM label has been added. Git tree hash: 6478147e9a6f1b4f8b8a33389f751365755e3c83
|
/assign @rexagod |
/lgtm |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
Signed-off-by: Anish Ramasekar <anish.ramasekar@gmail.com>
d4d62c3
to
60b5338
Compare
/lgtm |
LGTM label has been added. Git tree hash: 425fa41cf35176d92445d6a15c5d55a11c8b830a
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aramase, liggitt, rexagod 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 |
/test pull-kubernetes-e2e-kind |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Promote
apiserver_authentication_config_controller_automatic_reloads_total
andapiserver_authentication_config_controller_automatic_reload_last_timestamp_seconds
metrics to BETA. The feature has been BETA since 1.32 and is planned for GA in 1.34.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.:
/triage accepted
/sig auth
/priority important-soon