From d74c89b3224ac138c40a973fbcf4c80fb3a748dd Mon Sep 17 00:00:00 2001 From: Cedric Lamoriniere Date: Fri, 18 Mar 2022 21:30:04 +0100 Subject: [PATCH] fix: rename daemonset.updated metrics source The kube-state-metrics metric `kube_daemonset_updated_number_scheduled` was renamed to `kube_daemonset_status_updated_number_scheduled` in a late v2.0.0 alpha version (see: https://github.com/kubernetes/kube-state-metrics/pull/1181) our check was still using the old name so the `daemonset.updated` metrics was not generated. --- .../corechecks/cluster/ksm/kubernetes_state_defaults.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkg/collector/corechecks/cluster/ksm/kubernetes_state_defaults.go b/pkg/collector/corechecks/cluster/ksm/kubernetes_state_defaults.go index 4af353340c910..0b23a3cb3ad48 100644 --- a/pkg/collector/corechecks/cluster/ksm/kubernetes_state_defaults.go +++ b/pkg/collector/corechecks/cluster/ksm/kubernetes_state_defaults.go @@ -50,7 +50,7 @@ var ( "kube_daemonset_status_desired_number_scheduled": "daemonset.desired", "kube_daemonset_status_number_misscheduled": "daemonset.misscheduled", "kube_daemonset_status_number_ready": "daemonset.ready", - "kube_daemonset_updated_number_scheduled": "daemonset.updated", + "kube_daemonset_status_updated_number_scheduled": "daemonset.updated", "kube_deployment_spec_paused": "deployment.paused", "kube_deployment_spec_replicas": "deployment.replicas_desired", "kube_deployment_spec_strategy_rollingupdate_max_unavailable": "deployment.rollingupdate.max_unavailable",