The module lifecycle stage: General Availability

The module has requirements for installation

v1.0.6

Features

  • Added SecurityPolicyException resources for node-exporter and oom-kills-exporter, so the exporters keep working in clusters with security policies enforced by the admission-policy-engine module

Changes

  • Added the d8_source="dkp" label to the metrics and recording rules shipped with the module, so metrics produced by the platform can be told apart from the user ones

Bug fixes

  • Fixed PVC panels on the Controller, Namespace and Pod dashboards: the panels now respect the selected PVC and show the data broken down by pod
  • Fixed the Receive / Transmit network panels on the Controller dashboard for pods running with hostNetwork: true
  • Fixed the troubleshooting command in the LoadBalancerServiceWithoutExternalIP alert description: it now also takes the load balancer hostname into account, not only the IP address

v1.0.5

Security

  • Fixed various vulnerabilities in third-party libraries and bundled base images. Non-exploitable CVEs are addressed via VEX statements

v1.0.4

Bug fixes

  • Fixed the registry secret generation for modules installed from a custom ModuleSource

v1.0.3

Changes

  • Removed the StorageClassCloudManual alert and the hook that detected manually created StorageClasses

Bug fixes

  • Fixed the relabeling regular expression for the OOM kills metrics collected by ebpf-exporter

v1.0.2

Changes

  • Added the new VPA update modes (InPlaceOrRecreate, InPlaceOnly) to the kube_verticalpodautoscaler_spec_updatepolicy_updatemode metric produced by kube-state-metrics

v1.0.1

Changes

  • The module is now enabled by default in the Default and Managed bundles

v1.0.0

Changes

  • The monitoring-kubernetes module is now shipped as a separate Deckhouse module instead of being a part of the Deckhouse Kubernetes Platform core
  • Module lifecycle stage is set to General Availability