-
Notifications
You must be signed in to change notification settings - Fork 40.7k
Promote automatic_reloads of encryption config metrics to BETA #131824
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
base: master
Are you sure you want to change the base?
Conversation
/assign enj |
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. |
Signed-off-by: Anish Ramasekar <[email protected]>
a8edbd7
to
b491f97
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: aramase 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 |
type: Gauge | ||
stabilityLevel: BETA | ||
labels: | ||
- apiserver_id_hash |
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.
Is the apiserver_id_hash meant to identify which apiserver instance this metrics corresponds to?
Usually we expect the monitoring platform to be able to identify where the metric is coming from. For example via the kubernetes service discovery in Prometheus you can tell from which node/pod/container a metric is from.
The problem with a custom identifier is that you won't be able to correlate existing apiserver metrics that don't have this label with it. So generally we leave that to the monitoring system. Would that make sense in this case?
PR needs rebase. 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 cleanup
What this PR does / why we need it:
Promote
apiserever_encryption_config_controller_automatic_reloads_total
andapiserver_encryption_config_controller_automatic_reload_last_timestamp_seconds
metrics to BETA. The feature has been GA since 1.29.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