The module lifecycle stage: Generally available version
The module has requirements for installation
v1.0.5
Security
- Fixed CVE-2026-56851, CVE-2026-56857, CVE-2026-56866, CVE-2026-78659, CVE-2026-78660, CVE-2026-78663, CVE-2026-78667, CVE-2026-78669, CVE-2026-94439, CVE-2026-94440, CVE-2026-94448, CVE-2026-97030, CVE-2026-97031 and CVE-2026-97032 in the module images.
- Fixed CVE-2026-111943 and CVE-2026-63209 in the module images.
v1.0.4
Security
- Prometheus now authenticates on custom HTTPS targets with a client certificate. For security reasons the bearer token that used to be sent to HTTPS targets labeled
prometheus.deckhouse.io/custom-targetis being replaced by a client certificate issued by the platform. During the transition the token is still sent alongside the certificate; this is controlled by the newsendLegacyBearerTokenparameter (trueby default), and theD8MonitoringCustomLegacyBearerTokenEnabledalert reminds you that the token is still in use. To migrate, start everykube-rbac-proxythat protects your metrics with--client-ca-filepointing at the automatically createdprometheus-custom-scraper-ca.crtConfigMap, then turn the parameter off. The steps are described in the module documentation - Fixed vulnerabilities in bundled base images
v1.0.3
Bug fixes
- Fixed a broken link to the
istiomodule in the module documentation
v1.0.2
Security
- Fixed vulnerabilities in third-party libraries and bundled base images. Non-exploitable CVEs are addressed via VEX statements
v1.0.1
Changes
- The module is now enabled by default in the
DefaultandManagedbundles
v1.0.0
Changes
- The
monitoring-custommodule is delivered as a separate Deckhouse module with theGeneral Availabilitystage