The module lifecycle stage: General Availability

The module has requirements for installation

v1.0.7

Security

  • Fixed vulnerabilities CVE-2026-56854, CVE-2026-56855 and CVE-2026-78662 in the prometheus-operator and prometheus-config-reloader images, and updated base images.

v1.0.6

Changes

  • The module namespace is now checked against the restricted Pod Security Standards profile. Violations are reported as warnings only and do not block workloads.

Bug fixes

  • Fixed pulling module images when the module is installed from a custom ModuleSource: the ModuleSource registry credentials are now combined with the cluster registry credentials instead of replacing them.

v1.0.5

Bug fixes

  • Monitoring resources that reference secrets of type kubernetes.io/service-account-token (for example, a bearer token in a ServiceMonitor) are processed again: the operator no longer excludes these secrets from its watch.

v1.0.4

Bug fixes

  • Fixed running Prometheus with several rule-file volumes in Deckhouse CSE: the prometheus-config-reloader image now contains the required mount points.

v1.0.3

Security

  • Fixed vulnerabilities in third-party libraries of the prometheus-operator and prometheus-config-reloader images, and updated base images.

v1.0.2

Changes

  • Updated base images.

v1.0.1

Bug fixes

  • Fixed pulling the prometheus-operator image: the Deployment now uses the module’s own registry secret.

v1.0.0

Changes

  • First stable release of the module. Requires Deckhouse 1.76 or newer.

Bug fixes

  • Fixed publishing of the Russian module documentation.

v0.1.1

Changes

  • Updated the Helm library used by the module.

v0.1.0

Features

  • Initial release. The module deploys prometheus-operator, which manages Prometheus, Alertmanager and their configuration in the cluster via ServiceMonitor, PodMonitor, Probe, ScrapeConfig, PrometheusRule and other resources.