You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the VPA metrics were (re-)added, code was added to not try to
watch VPAs unless the CRDs had been created, to avoid spurious errors.
But it appears that ksm has since been fixed to not need this; it
watches for CRD creation/deletion itself, and ignores the VPA metric
definitions if the VPA CRDs don't exist.
Signed-off-by: Dan Winship <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,9 @@
1
1
# Note: This CHANGELOG is only for the monitoring team to track all monitoring related changes. Please see OpenShift release notes for official changes.
2
2
3
+
## 4.20
4
+
5
+
-[#2595](https://github.com/openshift/cluster-monitoring-operator/pull/2595) Multi-tenant support for KSM's CRS feature-set downstream.
6
+
3
7
## 4.18
4
8
5
9
-[#2503](https://github.com/openshift/cluster-monitoring-operator/issues/2503) Expose `scrapeInterval` setting for UWM Prometheus.
// The custom resource state configmap is always mounted in the kube-state-metrics container and only when the VPA CRD is installed, CMO will add `--custom-resource-state-config-file` to the container arguments list.
0 commit comments