Tyler Helmuth

@paulius-valiunas condition 1. states that `k8s.container.name` can be extracted as long as the `container.id` resource attribute is already present. Does your data have the resource attribute `container.id`? This feels like...

If you're trying to associate the telemetry to pod data using `k8s.container.name` it must be present in the resource attributes already - you cannot use the processor to add `k8s.container.name`...

@swiatekm-sumo you're right. We should add to the README that container fields can't be used for association. > Seems like this sentence is incorrect or in need of clarification, because...

@paulius-valiunas while `container` fields do nothing in the `pod_association` section, they have meaning in the `extract.metadata` section. This section of the README is accurate: ``` Additional container level attributes can...

Experienced this today during the release

It is cumbersome, but there is also an option to fork the transformprocessor and add the desired Converter for your own use.

@joegoldman2 what kind of k8s cluster are you using? I have still not been able to reproduce this issue.

The debug message is coming from here: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/2f55fec09dfca011191fb892bf6b496a167ab957/processor/k8sattributesprocessor/processor.go#L122. The preset's pod associations are: ```yaml pod_association: - sources: - from: resource_attribute name: k8s.pod.ip - sources: - from: resource_attribute name: k8s.pod.uid -...

I was also unable to reproduce with the latest minikube and collector.

> AKS clusters where fine To clarify, you were able to get AKS to populate correctly?