Area(s)

area:k8s

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

As part of the K8s SemConv stability work we need to define k8s cpu metrics that are already in use by the Opentelemetry Collector.

Related to #1032

Describe the solution you'd like

The existing metrics in use that we need to define as semantic conventions are the following:

k8s.node.cpu.usage:✅ #1320
k8s.node.cpu.utilization: Blocked until open-telemetry/opentelemetry-collector-contrib#27885 (comment) is covered
k8s.node.cpu.time: ✅ #1320
k8s.pod.cpu.usage: ✅ #1320
k8s.pod.cpu.utilization: Deprecated
k8s.pod.cpu.time: ✅ #1320
container.cpu.usage: ✅ #1128
container.cpu.utilization: Deprecated
container.cpu.time ✅ #282
k8s.container.cpu_limit_utilization: ✅ #2514
k8s.container.cpu_request_utilization: ✅ #2514
k8s.container.cpu.node.utilization
k8s.pod.cpu.node.utilization
k8s.pod.cpu_limit_utilization: waiting for open-telemetry/opentelemetry-collector-contrib#42485
k8s.pod.cpu_request_utilization: waiting for open-telemetry/opentelemetry-collector-contrib#42485

• verify if container.cpu.usage is the same when collected from k8s, compared to when collected from docker: [k8s] Define semantic conventions for k8s cpu metrics #1489 (comment)

Describe alternatives you've considered

No response

Additional context

No response