Skip to main content
Skip table of contents

DKP 2.4.2 Customer Incidents

The following issues are corrected or resolved in this release:

Unable to change kube-prometheus-stack values in overrides


When migrating existing workloads onto DKP, you had to manually edit all pod/service monitors to make the migration possible. An issue arises due to the fact that DKP passes the label value "true" for PodMonitor and ServiceMonitor. With this fix, using null instead of {} resulted in prometheus getting updated to serviceMonitorSelector: {} and podMonitorSelector: {} meaning you can use these override values.

Duplicate apiserver scrape targets in Prometheus


The default values in the kube-prometheus-stack chart included a duplicate scrape target for the Kubernetes API server. The duplicate scrape target is removed.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.