-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Add statefulset availablereplicas metric #1532
Add statefulset availablereplicas metric #1532
Conversation
Looks good from my side 👍. /hold |
cc @soltysh |
29c76a9
to
1c3071c
Compare
/lgtm |
1c3071c
to
a733640
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.
/lgtm
/approve
Thank you 🎉
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgrisonnet, lilic, ravisantoshgudimetla 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 |
* [FEATURE] Add --use-apiserver-cache flag to set resourceVersion=0 for ListWatch requests kubernetes#1548 * [FEATURE] Introduce metrics for Kubernetes object annotations kubernetes#1468 * [FEATURE] Introduce start time metric for containers in terminated state kubernetes#1519 * [FEATURE] Introduce metrics for cronjob job history limits kubernetes#1535 * [FEATURE] Add system_uuid dimension to kube_node_info metric kubernetes#1535 * [FEATURE] Add available replica metric for statefulsets kubernetes#1532 * [FEATURE] Add ready replica metric for deployments kubernetes#1534 * [CHANGE] Update go clients for Kubernetes to support 1.22 kubernetes#1545 * [CHANGE] Use new promlint package and update prometheus cli to 2.28.1 kubernetes#1531
What this PR does / why we need it:
StatefulSet minReadySeconds merged upstream and is in alpha stage. This PR bumps api and client-go to v1.22-beta to get AvailableReplicas field of StatefulSet and introduces available replicas metric. I can split bumping into another PR or drop it when 1.22 is released.
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
It increases the cardinality as we will start tracking available replicas. However, we have been using the similar metrics for deployment and daemonset.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
cc @simonpasquier