Skip to main content

Agent 0.5.39 (Sep 2026)

Breaking Changes​

Kubernetes label and annotation attributes renamed​

The Kubernetes attributes processor now emits the stable OpenTelemetry Kubernetes semantic conventions. Extracted pod, node and namespace labels and annotations are published under singular attribute names, and the previous plural names are no longer emitted.

Downstream dashboards, alerts, detection rules and exporter field mappings that reference the old attribute names must be updated. Collector configuration itself does not change.

Attribute renames:

  • k8s.pod.labels.<key> becomes k8s.pod.label.<key>
  • k8s.pod.annotations.<key> becomes k8s.pod.annotation.<key>
  • k8s.node.labels.<key> becomes k8s.node.label.<key>
  • k8s.node.annotations.<key> becomes k8s.node.annotation.<key>
  • k8s.namespace.labels.<key> becomes k8s.namespace.label.<key>
  • k8s.namespace.annotations.<key> becomes k8s.namespace.annotation.<key>
  • container.image.tag (single value) becomes container.image.tags (list)

Other changes in this release:

  • The processor is now marked stable for traces, metrics and logs.
  • The deployment_name_from_replicaset option has been removed. Deployment names are always derived from the ReplicaSet name by trimming the pod-template-hash suffix. Enable the k8s.deployment.uid attribute if you need the name resolved from the Kubernetes API instead.
  • replicaset and cronjob are now accepted as from sources for label and annotation extraction.
  • Two pod association rules with the same set of sources are now rejected at startup instead of being silently accepted.
  • The processor's own internal telemetry metrics are emitted in the new format only.