The module lifecycle stage: Generally available version

The module has requirements for installation

v1.0.9

Bug fixes

  • image-availability-exporter no longer queries the AWS instance metadata service (IMDS) at startup, so in clusters outside AWS it no longer logs the Unable to fetch metadata from IMDS error or delays startup by a few seconds. The AWS region for ECR authentication is taken from the image registry address; imageAvailability.awsRegion still overrides it.
  • The D8ImageAvailabilityExporterMalfunctioning alert no longer goes into the pending state for about imageAvailability.imageCheckInterval after every start of the image-availability-exporter pod and after its removal.

Changes

  • The default of imageAvailability.imageCheckInterval is 60s again (it was 5m in v1.0.8). The image-availability-exporter pod is recreated once on upgrade unless the parameter is set explicitly.
  • The window of the D8ImageAvailabilityExporterMalfunctioning alert is 10 minutes again (it was 15 minutes in v1.0.8).

v1.0.8

Features

  • image-availability-exporter now trusts the CA of the upstream container registry configured in the deckhouse ModuleConfig (Direct and Proxy registry modes), so it no longer has to be duplicated in imageAvailability.registry.tlsConfig.ca.
  • Added access roles for the role model of DKP 1.78 and later: d8:system-capability:extended-monitoring:view and d8:system-capability:extended-monitoring:edit. Earlier DKP versions keep the previous roles.

Bug fixes

  • The image-availability-exporter pod is recreated when any registry CA changes, so a changed CA no longer causes false *ImageAvailabilityUnknownError alerts until a manual restart. Brief unknown_error results are still possible while the cluster applies a registry mode switch; the *ImageAvailabilityUnknownError alerts tolerate them thanks to their 30-minute for.
  • When the cluster pulls images through the node agent of the registry module, image-availability-exporter no longer checks images under registry.d8-system.svc:5001: only a node can pull them, and the registry module alerts on their availability itself.

Changes

  • The default of imageAvailability.imageCheckInterval changed from 60s to 5m. Set the parameter explicitly to keep the previous check rate.
  • The exporter checks up to 50 images per interval, so a full pass over all monitored images takes about N/50 intervals (for the ~200 Deckhouse images of a typical cluster — about 20 minutes with the 5m default); a missing image is reported after it is checked plus the 30-minute for of the *ImageAbsent alert. The D8ImageAvailabilityExporterMalfunctioning window was widened to 15 minutes accordingly.
  • The image-availability-exporter pod is recreated once on upgrade because of the new checksum/*-ca annotations and the new default --check-interval; open *ImageAbsent alerts resolve until the image is re-checked.

Security

  • Fixed CVEs in the module images and hooks.
  • Bumped image-availability-exporter to v0.18.0, which includes the dependency and Go toolchain updates that fix the known CVEs (previously carried as a local patch).

v1.0.7

Security

  • Fixed CVE-2026-78661 and CVE-2026-97045 in the module images.

v1.0.6

Security

  • Fixed CVE-2026-85747 in the image-availability-exporter image.
  • Fixed CVE-2026-111943 and CVE-2026-63209 in the module images.

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.

v1.0.4

Security

  • Fixed vulnerabilities in the module’s images: the base images were updated and the x509-certificate-exporter dependencies were patched (CVE-2026-46595, CVE-2026-56854, CVE-2026-56855, CVE-2026-78662).

v1.0.3

Security

  • Fixed a security issue in the module’s templates.

Changes

  • Added the d8_source="dkp" label to all metrics scraped from the module’s exporters (events-exporter, extended-monitoring-exporter, image-availability-exporter, x509-certificate-exporter), so that metrics originating from DKP can be distinguished from other sources.
  • Reworked the module documentation: the usage guide (enabling metrics export for a namespace, overriding alert trigger thresholds, the reference of standard labels and supported Kubernetes objects) moved from the configuration page to the module overview page.
  • Added missing descriptions of the module parameters (tolerations, container registry mirrors,TLS settings) on the configuration page.

v1.0.2

Bug fixes:

  • Fixed a template rendering error that prevented the module from being deployed.

v1.0.1

Features

  • Added awsRegion parameter for the image-availability-exporter to support ECR authentication when the cluster and the registry are located in different AWS regions.

Bug fixes

  • Bumped image-availability-exporter to v0.16.0, in which an issue was fixed where a configured mirror was not applied to images resolved via defaultRegistry.