The module lifecycle stageGeneral Availability

The module has requirements for installation

v1.0.3

Changes

  • System metrics of the log collection agent now carry the d8_source="dkp" label. It allows platform metrics to be told apart from metrics exposed by user applications.
  • The module namespace is now checked against the restricted Pod Security Standards profile. Violations are reported as warnings only and do not block workloads. The deviations the agent requires — running as root and mounting node paths to read container and node logs and to store its read position — are declared and explained in the SecurityPolicyException resource shipped with the module, so log collection keeps working without any action.
  • The privileges of the agent are reduced as far as log collection permits: the RuntimeDefault seccomp profile is applied, all Linux capabilities are dropped, privilege escalation is denied, and the container root filesystem is read-only.
  • The registry.dockercfg module configuration parameter is removed. Module images are always pulled with the platform registry credentials, so if the parameter is set in the module configuration, remove it before updating.

Security

  • Fixed various vulnerabilities.

v1.0.2

Bug fixes

  • Fixed links between documentation pages and in custom resource descriptions that had been broken after the module was moved to a separate repository.

v1.0.1

Changes

  • Module images are now built using the container-base images and the pm package manager.

Security

  • Fixed various vulnerabilities. The module now ships a VEX document listing the vulnerabilities of its dependencies that cannot affect it, along with the reason for each.

v1.0.0

Changes

  • Resource management in the Static mode is reworked: CPU and memory requests are now set in the resourcesRequests.static.requests section, and CPU and memory limits for the agent can be configured in resourcesRequests.static.limits. Existing module configuration is converted automatically, so no action is required.

Bug fixes

  • Fixed the CPU and memory requests configured for the Static resource management mode not reaching the log collection agent container.