Ensure that k8s labels and annotations follow SemConv

[ChrsMark]

Component(s)

processor/k8sattributes

Describe the issue you're reporting

This is issue is to keep track of any pending task to align the k8sattributes processor with SemConv's pod's labels and annotations spec.

Ref PRs:

• Add attribute for k8s pod annotations semantic-conventions#573 (comment)
• Expanding k8s.pod resource to include pod labels semantic-conventions#494 (comment)

This might also applies on the kubeletstats and k8scluster receivers as well.

[github-actions]

Pinging code owners:

• processor/k8sattributes: @dmitryax @rmfitzpatrick @fatsheep9146 @TylerHelmuth

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[TylerHelmuth]

We do need to do this, I'd prefer not doing it until the Kubernetes resource attributes are stabilized, that way we only have to do the breaking change once.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• processor/k8sattributes: @dmitryax @rmfitzpatrick @fatsheep9146 @TylerHelmuth

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[ChrsMark]

Still valid. Should we mark this as "never stale" to avoid having this closed at some point in case we miss updating it?

[ChrsMark]

Related to open-telemetry/semantic-conventions#1242.

[venkatesh-thatham]

the k8sattributesprocessor is still using old semantic convention version v1.6.1 and the latest version v1.25.0 includes both k8s.cluster.name and k8s.container.restart_count.

when I try to add cluster name k8s attribute according to this semantic convention documentation, I'm getting validation error: "k8s.cluster.name is not a supported metadata field"

[TylerHelmuth]

@venkatesh-thatham although k8s.cluster.name is the semantically correct value to represent the name of a kubernetes cluster in an attribute, the k8sattributesprocessor does not support adding that information to the telemetry. This is because there isn't a good way to get the information.

You should set an attribute with the static cluster name via an env var or static string using the resource processor or transformprocessor.

[ChrsMark]

The resourcedetectionprocessor can also provide the k8s.cluster.name for some cloud providers.