Datadog re-appends latest
tag on top of image_tag
added through Tag Auto-discovery
#29327
Labels
latest
tag on top of image_tag
added through Tag Auto-discovery
#29327
Agent Environment
Agent Version: 7.54.1 pulled through
public.ecr.aws/datadog/agent:7.54.1
Describe what happened:
For example for a container with image
docker.io/library/alpine:3.20.1
the Datadog agent, reportsimage_tag
as3.20.1
. This is as expected.For container with image
docker.io/library/alpine@sha256:xxxx
, the Datadog agent reportsimage_tag
aslatest
. This must be a design choice? Further questions relating to this are asked below.For a pod spec:
There are two
image_tag
tags and are reported as3.20.1_own, latest
Describe what you expected:
image_tag
should've been3.20.1_own
and NOT another tag withlatest
Question 1:
Why is
latest
the default tag is no tag is present? This does not make sense, shouldn't this be empty or null and not added as a tag? Code Reference 1, Code Reference 2Question 2:
Why is the DD agent re-appending the
latest
tag to images with only digests, when theimage_tag
has already been added as annotation for Auto-Discovery?Steps to reproduce the issue:
Just launch a pod with the spec with Datadog agent setup for the cluster to forward logs to Datadog.
We will see that all logs from this node in the K8s cluster will report two
image_tag
as3.20.1_own
andlatest
.Additional environment details (Operating System, Cloud provider, etc):
The environment is aws-eks kubernetes
v1.28
with the agent installed.The text was updated successfully, but these errors were encountered: