-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: add restartPolicy to kube_pod_init_container_info
metric
#2239
feat: add restartPolicy to kube_pod_init_container_info
metric
#2239
Conversation
This issue is currently awaiting triage. If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
Welcome @changhyuni! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: changhyuni 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 |
Resolves: add-wilcard-allowlist-annotations
5e21ce6
to
2b0e761
Compare
2b0e761
to
85e0401
Compare
What this PR does / why we need it:
This PR adds a label to
kube_pod_init_container_info
to track therestartPolicy
set in the init_containerWith sidecar support starting with kubernetes 1.28,
init_container
can be usedrestartPolicy
This metric tells you which pods are using the sidecar feature
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
adds a label that is never updated for a given init container
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 #