Add k8s entity attributes

[jinja2]

Area(s)

area:k8s

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

K8scluster receiver currently emits entity events for k8s objects. We are working on adding descriptive attributes (values may be mutable) to k8s entities. I'd like to use this issue to track existing and any new attributes to k8s entities.

Describe the solution you'd like

Listing the descriptive attributes for various k8s entity types we'd like to add.

Add following attributes for k8s.pod -

• k8s.pod.phase - The phase of a Pod is a simple, high-level summary of where the Pod is in its lifecycle. Possible Values - Pending, Running, Succeeded, Failed, Unknown.
• k8s.pod.status_reason - A brief CamelCase message indicating details about why the pod is in this state. e.g. value Evicted.
• k8s.workload.kind - k8s workload kind associated with the pod. E.g. values - Deployment, CronJob, StatefulSet, Node. For pods associated with a deployment, the value of this attribute will be Deployment even though the true owner of the pod as seen in metadata.ownerReferences is ReplicaSet.
• k8s.workload.uid - The uid for the workload associated with this pod.
• k8s.pod.creation_timestamp - Pod's creation time in RFC3339 format. E.g. value - 2020-06-18T17:24:53Z

Attributes for k8s.node -

• k8s.node.condition_{type} - Attributes for node condition types set by kubelet in response to node resource pressure. Possible values for below attributes are false, true and unknown
  • k8s.node.conditon_ready
  • k8s.node.condition_memory_pressure
  • k8s.node.condition_network_unavailable
  • k8s.node.condition_pid_pressure
  • k8s.node.condition_disk_pressure
• k8s.node.creation_timestamp - Node's creation time in RFC3339 format. E.g. value - 2020-06-18T17:24:53Z

Attributes for k8s.namespace -

• k8s.namespace.creation_timestamp - Namespace's creation time in RFC3339 format. E.g. value - 2020-06-18T17:24:53Z
• k8s.namespace.phase - Phase of the namespace; values - active, terminating

Describe alternatives you've considered

No response

Additional context

These are experimental attributes sent as part of entity events from the k8scluster receiver. Majority of these are mutable and meant to be used in descriptive capacity. We'd like to use this issue to track attributes used in the experimental entity type in k8s receivers.