The module lifecycle stage: General Availability

The module has requirements for installation

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-target is 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 new sendLegacyBearerToken parameter (true by default), and the D8MonitoringCustomLegacyBearerTokenEnabled alert reminds you that the token is still in use. To migrate, start every kube-rbac-proxy that protects your metrics with --client-ca-file pointing at the automatically created prometheus-custom-scraper-ca.crt ConfigMap, 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 istio module 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 Default and Managed bundles

v1.0.0

Changes

  • The monitoring-custom module is delivered as a separate Deckhouse module with the General Availability stage