-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 improves the existing capi metrics #7886
🌱 improves the existing capi metrics #7886
Conversation
Hi @bavarianbidi. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
59cd2e6
to
1aefe55
Compare
1aefe55
to
67e9cb3
Compare
- status | ||
- phase | ||
type: StateSet | ||
- name: created |
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.
wrong indent beginning here (or above)?! or tabs vs spaces?
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.
"wrong" is relative ;-)
i use the YAML
plugin in vscode which auto-format the yaml file. but anyhow - i fixed the format to allign with the existing generated yamls.
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.
uh, then the others may be wrong :-) happy to get it auto-formatted but also okay to keep as is :-)
Sad that there is not the only formatter for yaml, like there is gofmt for go 😂
@bavarianbidi thanks for this PR! Also, @bavarianbidi it will be great to have your opinion on #7158 which will hopefully replace these manually maintained files soon. |
67e9cb3
to
fea977e
Compare
/ok-to-test (potential flake?) /lgtm but pending squash |
* add control_plane and infrastructure reference information as label to cluster_info * introduce new capi_machine_addresses metric * rename containerRuntimeVersion label from cluster_machine_info to container_runtime_version * gen. changes due machine addresses comment update * add initial capi_machinepool metrics Signed-off-by: Mario Constanti <mario@constanti.de>
fea977e
to
938d9d3
Compare
Thank you very much!! Very nice to see contributions in this area :) /lgtm |
LGTM label has been added. Git tree hash: b3061e4cb6a854a3fc18eaa9257ce3f6c852ceec
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
What this PR does / why we need it:
This PR is intentionally split into three commits to make the review more easier for now:
add control plane and infra ref labels to cluster
add the following labels from the cluster cr spec to the cluster_info
metric:
control_plane_reference_kind
control_plane_reference_name
infrastructure_reference_kind
infrastructure_reference_name
introduce new capi_machine_addresses metric
to represent the different kind of addresses in an own metric.
containerRuntimeVersion
label got also renamed tocontainer_runtime_version
add initial capi_machinepool metrics
Regarding 2.
With the discussion in this slack thread in #kube-state-metrics i will change the metric implementation again.
Signed-off-by: Mario Constanti mario@constanti.de
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 #