[processor/k8s_attributes] Consider moving k8s.cluster.uid detection to the resource detection processor

[dmitryax]

Component(s)

No response

Is your feature request related to a problem? Please describe.

It can be valuable to set k8s.cluster.uid resource attribute to all telemetry in a particular cluster. However, k8s attributes processor requires having a pod association to set even the attribute that is taken from the configured k8s api without using any pod information. This mode of applying attributes is better suited in the resource detection processor, not k8s attributes processor.

Describe the solution you'd like

The detector can be called k8scluster (we already have k8snode detector). Similarly we can add k8s.cluster.name in this detector as requested in #35116.

Describe alternatives you've considered

It's possible to also update the k8s attributes processor to set k8s.cluster.uid on all telemetry, but that goes against its main purpose.

[github-actions]

Pinging code owners for processor/resourcedetection: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[github-actions]

Pinging code owners for processor/k8sattributes: @dmitryax @fatsheep9146 @TylerHelmuth @ChrsMark. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[dehaansa]

Issue #35116 was actually addressed in #35450 , so I think this issue would be proposing adding this resource attribute to the kubeadm detector.

[dmitryax]

@dehaansa, thanks for pointing to the PR. I missed that. Makes sense. k8s.cluster.uid can be added to the kubeadm detector I guess. I'd still prefer k8scluster name, but not sure it worth renaming now

[odubajDT]

Hi, I would like to handle this issue if possible

[odubajDT]

Prepared a PR #38216