# K8s
LLMS index: [llms.txt](/llms.txt)
---
- [Kubernetes Attributes](#kubernetes-attributes)
- [Deprecated Kubernetes Attributes](#deprecated-kubernetes-attributes)
## Kubernetes Attributes
Kubernetes resource attributes.
**Attributes:**
| Key | Stability | Value Type | Description | Example Values |
| --- | --- | --- | --- | --- |
| `k8s.cluster.name` |  | string | The name of the cluster. | `opentelemetry-cluster` |
| `k8s.cluster.uid` |  | string | A pseudo-ID for the cluster, set to the UID of the `kube-system` namespace. [1] | `218fc5a9-a5f1-4b54-aa05-46717d0ab26d` |
| `k8s.container.name` |  | string | The name of the Container from Pod specification, must be unique within a Pod. Container runtime usually uses different globally unique name (`container.name`). | `redis` |
| `k8s.container.restart_count` |  | int | Number of times the container was restarted. This attribute can be used to identify a particular container (running or stopped) within a container spec. | |
| `k8s.container.status.last_terminated_reason` |  | string | Last terminated reason of the Container. | `Evicted`; `Error` |
| `k8s.container.status.reason` |  | string | The reason for the container state. Corresponds to the `reason` field of the: [K8s ContainerStateWaiting](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#containerstatewaiting-v1-core) or [K8s ContainerStateTerminated](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#containerstateterminated-v1-core) | `ContainerCreating`; `CrashLoopBackOff`; `CreateContainerConfigError`; `ErrImagePull`; `ImagePullBackOff`; `OOMKilled`; `Completed`; `Error`; `ContainerCannotRun` |
| `k8s.container.status.state` |  | string | The state of the container. [K8s ContainerState](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#containerstate-v1-core) | `terminated`; `running`; `waiting` |
| `k8s.cronjob.annotation.` |  | string | The cronjob annotation placed on the CronJob, the `` being the annotation name, the value being the annotation value. [2] | `4`; `` |
| `k8s.cronjob.label.` |  | string | The label placed on the CronJob, the `` being the label name, the value being the label value. [3] | `weekly`; `` |
| `k8s.cronjob.name` |  | string | The name of the CronJob. | `opentelemetry` |
| `k8s.cronjob.uid` |  | string | The UID of the CronJob. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.daemonset.annotation.` |  | string | The annotation placed on the DaemonSet, the `` being the annotation name, the value being the annotation value, even if the value is empty. [4] | `1`; `` |
| `k8s.daemonset.label.` |  | string | The label placed on the DaemonSet, the `` being the label name, the value being the label value, even if the value is empty. [5] | `guestbook`; `` |
| `k8s.daemonset.name` |  | string | The name of the DaemonSet. | `opentelemetry` |
| `k8s.daemonset.uid` |  | string | The UID of the DaemonSet. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.deployment.annotation.` |  | string | The annotation placed on the Deployment, the `` being the annotation name, the value being the annotation value, even if the value is empty. [6] | `1`; `` |
| `k8s.deployment.label.` |  | string | The label placed on the Deployment, the `` being the label name, the value being the label value, even if the value is empty. [7] | `guestbook`; `` |
| `k8s.deployment.name` |  | string | The name of the Deployment. | `opentelemetry` |
| `k8s.deployment.uid` |  | string | The UID of the Deployment. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.hpa.metric.type` |  | string | The type of metric source for the horizontal pod autoscaler. [8] | `Resource`; `ContainerResource` |
| `k8s.hpa.name` |  | string | The name of the horizontal pod autoscaler. | `opentelemetry` |
| `k8s.hpa.scaletargetref.api_version` |  | string | The API version of the target resource to scale for the HorizontalPodAutoscaler. [9] | `apps/v1`; `autoscaling/v2` |
| `k8s.hpa.scaletargetref.kind` |  | string | The kind of the target resource to scale for the HorizontalPodAutoscaler. [10] | `Deployment`; `StatefulSet` |
| `k8s.hpa.scaletargetref.name` |  | string | The name of the target resource to scale for the HorizontalPodAutoscaler. [11] | `my-deployment`; `my-statefulset` |
| `k8s.hpa.uid` |  | string | The UID of the horizontal pod autoscaler. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.hugepage.size` |  | string | The size (identifier) of the K8s huge page. | `2Mi` |
| `k8s.job.annotation.` |  | string | The annotation placed on the Job, the `` being the annotation name, the value being the annotation value, even if the value is empty. [12] | `1`; `` |
| `k8s.job.label.` |  | string | The label placed on the Job, the `` being the label name, the value being the label value, even if the value is empty. [13] | `ci`; `` |
| `k8s.job.name` |  | string | The name of the Job. | `opentelemetry` |
| `k8s.job.uid` |  | string | The UID of the Job. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.namespace.annotation.` |  | string | The annotation placed on the Namespace, the `` being the annotation name, the value being the annotation value, even if the value is empty. [14] | `0`; `` |
| `k8s.namespace.label.` |  | string | The label placed on the Namespace, the `` being the label name, the value being the label value, even if the value is empty. [15] | `default`; `` |
| `k8s.namespace.name` |  | string | The name of the namespace that the pod is running in. | `default` |
| `k8s.namespace.phase` |  | string | The phase of the K8s namespace. [16] | `active`; `terminating` |
| `k8s.node.annotation.` |  | string | The annotation placed on the Node, the `` being the annotation name, the value being the annotation value, even if the value is empty. [17] | `0`; `` |
| `k8s.node.condition.status` |  | string | The status of the condition, one of True, False, Unknown. [18] | `true`; `false`; `unknown` |
| `k8s.node.condition.type` |  | string | The condition type of a K8s Node. [19] | `Ready`; `DiskPressure` |
| `k8s.node.label.` |  | string | The label placed on the Node, the `` being the label name, the value being the label value, even if the value is empty. [20] | `arm64`; `` |
| `k8s.node.name` |  | string | The name of the Node. | `node-1` |
| `k8s.node.uid` |  | string | The UID of the Node. | `1eb3a0c6-0477-4080-a9cb-0cb7db65c6a2` |
| `k8s.pod.annotation.` |  | string | The annotation placed on the Pod, the `` being the annotation name, the value being the annotation value. [21] | `true`; `x64`; `` |
| `k8s.pod.hostname` |  | string | Specifies the hostname of the Pod. [22] | `collector-gateway` |
| `k8s.pod.ip` |  | string | IP address allocated to the Pod. [23] | `172.18.0.2` |
| `k8s.pod.label.` |  | string | The label placed on the Pod, the `` being the label name, the value being the label value. [24] | `my-app`; `x64`; `` |
| `k8s.pod.name` |  | string | The name of the Pod. | `opentelemetry-pod-autoconf` |
| `k8s.pod.start_time` |  | string | The start timestamp of the Pod. [25] | `2025-12-04T08:41:03Z` |
| `k8s.pod.status.phase` |  | string | The phase for the pod. Corresponds to the `phase` field of the: [K8s PodStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.33/#podstatus-v1-core) | `Pending`; `Running` |
| `k8s.pod.status.reason` |  | string | The reason for the pod state. Corresponds to the `reason` field of the: [K8s PodStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.33/#podstatus-v1-core) | `Evicted`; `NodeAffinity` |
| `k8s.pod.uid` |  | string | The UID of the Pod. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.replicaset.annotation.` |  | string | The annotation placed on the ReplicaSet, the `` being the annotation name, the value being the annotation value, even if the value is empty. [26] | `0`; `` |
| `k8s.replicaset.label.` |  | string | The label placed on the ReplicaSet, the `` being the label name, the value being the label value, even if the value is empty. [27] | `guestbook`; `` |
| `k8s.replicaset.name` |  | string | The name of the ReplicaSet. | `opentelemetry` |
| `k8s.replicaset.uid` |  | string | The UID of the ReplicaSet. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.replicationcontroller.name` |  | string | The name of the replication controller. | `opentelemetry` |
| `k8s.replicationcontroller.uid` |  | string | The UID of the replication controller. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.resourcequota.name` |  | string | The name of the resource quota. | `opentelemetry` |
| `k8s.resourcequota.resource_name` |  | string | The name of the K8s resource a resource quota defines. [28] | `count/replicationcontrollers` |
| `k8s.resourcequota.uid` |  | string | The UID of the resource quota. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.service.annotation.` |  | string | The annotation placed on the Service, the `` being the annotation name, the value being the annotation value, even if the value is empty. [29] | `true`; `` |
| `k8s.service.endpoint.address_type` |  | string | The address type of the service endpoint. [30] | `IPv4`; `IPv6` |
| `k8s.service.endpoint.condition` |  | string | The condition of the service endpoint. [31] | `ready`; `serving`; `terminating` |
| `k8s.service.endpoint.zone` |  | string | The zone of the service endpoint. [32] | `us-east-1a`; `us-west-2b`; `zone-a`; `` |
| `k8s.service.label.` |  | string | The label placed on the Service, the `` being the label name, the value being the label value, even if the value is empty. [33] | `my-service`; `` |
| `k8s.service.name` |  | string | The name of the Service. | `my-service` |
| `k8s.service.publish_not_ready_addresses` |  | boolean | Whether the Service publishes not-ready endpoints. [34] | `true`; `false` |
| `k8s.service.selector.` |  | string | The selector key-value pair placed on the Service, the `` being the selector key, the value being the selector value. [35] | `my-app`; `v1` |
| `k8s.service.traffic_distribution` |  | string | The traffic distribution policy for the Service. [36] | `PreferSameZone`; `PreferSameNode` |
| `k8s.service.type` |  | string | The type of the Kubernetes Service. [37] | `ClusterIP`; `NodePort`; `LoadBalancer` |
| `k8s.service.uid` |  | string | The UID of the Service. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.statefulset.annotation.` |  | string | The annotation placed on the StatefulSet, the `` being the annotation name, the value being the annotation value, even if the value is empty. [38] | `1`; `` |
| `k8s.statefulset.label.` |  | string | The label placed on the StatefulSet, the `` being the label name, the value being the label value, even if the value is empty. [39] | `guestbook`; `` |
| `k8s.statefulset.name` |  | string | The name of the StatefulSet. | `opentelemetry` |
| `k8s.statefulset.uid` |  | string | The UID of the StatefulSet. | `275ecb36-5aa8-4c2a-9c47-d8bb681b9aff` |
| `k8s.storageclass.name` |  | string | The name of K8s [StorageClass](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#storageclass-v1-storage-k8s-io) object. | `gold.storageclass.storage.k8s.io` |
| `k8s.volume.name` |  | string | The name of the K8s volume. | `volume0` |
| `k8s.volume.type` |  | string | The type of the K8s volume. | `emptyDir`; `persistentVolumeClaim` |
**[1] `k8s.cluster.uid`:** K8s doesn't have support for obtaining a cluster ID. If this is ever
added, we will recommend collecting the `k8s.cluster.uid` through the
official APIs. In the meantime, we are able to use the `uid` of the
`kube-system` namespace as a proxy for cluster ID. Read on for the
rationale.
Every object created in a K8s cluster is assigned a distinct UID. The
`kube-system` namespace is used by Kubernetes itself and will exist
for the lifetime of the cluster. Using the `uid` of the `kube-system`
namespace is a reasonable proxy for the K8s ClusterID as it will only
change if the cluster is rebuilt. Furthermore, Kubernetes UIDs are
UUIDs as standardized by
[ISO/IEC 9834-8 and ITU-T X.667](https://www.itu.int/ITU-T/studygroups/com17/oid.html).
Which states:
> If generated according to one of the mechanisms defined in Rec.
> ITU-T X.667 | ISO/IEC 9834-8, a UUID is either guaranteed to be
> different from all other UUIDs generated before 3603 A.D., or is
> extremely likely to be different (depending on the mechanism chosen).
Therefore, UIDs between clusters should be extremely unlikely to
conflict.
**[2] `k8s.cronjob.annotation.`:** Examples:
- An annotation `retries` with value `4` SHOULD be recorded as the
`k8s.cronjob.annotation.retries` attribute with value `"4"`.
- An annotation `data` with empty string value SHOULD be recorded as
the `k8s.cronjob.annotation.data` attribute with value `""`.
**[3] `k8s.cronjob.label.`:** Examples:
- A label `type` with value `weekly` SHOULD be recorded as the
`k8s.cronjob.label.type` attribute with value `"weekly"`.
- A label `automated` with empty string value SHOULD be recorded as
the `k8s.cronjob.label.automated` attribute with value `""`.
**[4] `k8s.daemonset.annotation.`:** Examples:
- A label `replicas` with value `1` SHOULD be recorded
as the `k8s.daemonset.annotation.replicas` attribute with value `"1"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.daemonset.annotation.data` attribute with value `""`.
**[5] `k8s.daemonset.label.`:** Examples:
- A label `app` with value `guestbook` SHOULD be recorded
as the `k8s.daemonset.label.app` attribute with value `"guestbook"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.daemonset.label.injected` attribute with value `""`.
**[6] `k8s.deployment.annotation.`:** Examples:
- A label `replicas` with value `1` SHOULD be recorded
as the `k8s.deployment.annotation.replicas` attribute with value `"1"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.deployment.annotation.data` attribute with value `""`.
**[7] `k8s.deployment.label.`:** Examples:
- A label `replicas` with value `0` SHOULD be recorded
as the `k8s.deployment.label.app` attribute with value `"guestbook"`.
- A label `injected` with empty string value SHOULD be recorded as
the `k8s.deployment.label.injected` attribute with value `""`.
**[8] `k8s.hpa.metric.type`:** This attribute reflects the `type` field of spec.metrics[] in the HPA.
**[9] `k8s.hpa.scaletargetref.api_version`:** This maps to the `apiVersion` field in the `scaleTargetRef` of the HPA spec.
**[10] `k8s.hpa.scaletargetref.kind`:** This maps to the `kind` field in the `scaleTargetRef` of the HPA spec.
**[11] `k8s.hpa.scaletargetref.name`:** This maps to the `name` field in the `scaleTargetRef` of the HPA spec.
**[12] `k8s.job.annotation.`:** Examples:
- A label `number` with value `1` SHOULD be recorded
as the `k8s.job.annotation.number` attribute with value `"1"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.job.annotation.data` attribute with value `""`.
**[13] `k8s.job.label.`:** Examples:
- A label `jobtype` with value `ci` SHOULD be recorded
as the `k8s.job.label.jobtype` attribute with value `"ci"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.job.label.automated` attribute with value `""`.
**[14] `k8s.namespace.annotation.`:** Examples:
- A label `ttl` with value `0` SHOULD be recorded
as the `k8s.namespace.annotation.ttl` attribute with value `"0"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.namespace.annotation.data` attribute with value `""`.
**[15] `k8s.namespace.label.`:** Examples:
- A label `kubernetes.io/metadata.name` with value `default` SHOULD be recorded
as the `k8s.namespace.label.kubernetes.io/metadata.name` attribute with value `"default"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.namespace.label.data` attribute with value `""`.
**[16] `k8s.namespace.phase`:** This attribute aligns with the `phase` field of the
[K8s NamespaceStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#namespacestatus-v1-core)
**[17] `k8s.node.annotation.`:** Examples:
- An annotation `node.alpha.kubernetes.io/ttl` with value `0` SHOULD be recorded as
the `k8s.node.annotation.node.alpha.kubernetes.io/ttl` attribute with value `"0"`.
- An annotation `data` with empty string value SHOULD be recorded as
the `k8s.node.annotation.data` attribute with value `""`.
**[18] `k8s.node.condition.status`:** This attribute aligns with the `status` field of the
[NodeCondition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#nodecondition-v1-core)
**[19] `k8s.node.condition.type`:** K8s Node conditions as described
by [K8s documentation](https://v1-32.docs.kubernetes.io/docs/reference/node/node-status/#condition).
This attribute aligns with the `type` field of the
[NodeCondition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#nodecondition-v1-core)
The set of possible values is not limited to those listed here. Managed Kubernetes environments,
or custom controllers MAY introduce additional node condition types.
When this occurs, the exact value as reported by the Kubernetes API SHOULD be used.
**[20] `k8s.node.label.`:** Examples:
- A label `kubernetes.io/arch` with value `arm64` SHOULD be recorded
as the `k8s.node.label.kubernetes.io/arch` attribute with value `"arm64"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.node.label.data` attribute with value `""`.
**[21] `k8s.pod.annotation.`:** Examples:
- An annotation `kubernetes.io/enforce-mountable-secrets` with value `true` SHOULD be recorded as
the `k8s.pod.annotation.kubernetes.io/enforce-mountable-secrets` attribute with value `"true"`.
- An annotation `mycompany.io/arch` with value `x64` SHOULD be recorded as
the `k8s.pod.annotation.mycompany.io/arch` attribute with value `"x64"`.
- An annotation `data` with empty string value SHOULD be recorded as
the `k8s.pod.annotation.data` attribute with value `""`.
**[22] `k8s.pod.hostname`:** The K8s Pod spec has an optional hostname field, which can be used to specify a hostname.
Refer to [K8s docs](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-hostname-and-subdomain-field)
for more information about this field.
This attribute aligns with the `hostname` field of the
[K8s PodSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podspec-v1-core).
**[23] `k8s.pod.ip`:** This attribute aligns with the `podIP` field of the
[K8s PodStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podstatus-v1-core).
**[24] `k8s.pod.label.`:** Examples:
- A label `app` with value `my-app` SHOULD be recorded as
the `k8s.pod.label.app` attribute with value `"my-app"`.
- A label `mycompany.io/arch` with value `x64` SHOULD be recorded as
the `k8s.pod.label.mycompany.io/arch` attribute with value `"x64"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.pod.label.data` attribute with value `""`.
**[25] `k8s.pod.start_time`:** Date and time at which the object was acknowledged by the Kubelet.
This is before the Kubelet pulled the container image(s) for the pod.
This attribute aligns with the `startTime` field of the
[K8s PodStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podstatus-v1-core),
in ISO 8601 (RFC 3339 compatible) format.
**[26] `k8s.replicaset.annotation.`:** Examples:
- A label `replicas` with value `0` SHOULD be recorded
as the `k8s.replicaset.annotation.replicas` attribute with value `"0"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.replicaset.annotation.data` attribute with value `""`.
**[27] `k8s.replicaset.label.`:** Examples:
- A label `app` with value `guestbook` SHOULD be recorded
as the `k8s.replicaset.label.app` attribute with value `"guestbook"`.
- A label `injected` with empty string value SHOULD be recorded as
the `k8s.replicaset.label.injected` attribute with value `""`.
**[28] `k8s.resourcequota.resource_name`:** The value for this attribute can be either the full `count/[.]` string (e.g., count/deployments.apps, count/pods), or, for certain core Kubernetes resources, just the resource name (e.g., pods, services, configmaps). Both forms are supported by Kubernetes for object count quotas. See [Kubernetes Resource Quotas documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#quota-on-object-count) for more details.
**[29] `k8s.service.annotation.`:** Examples:
- An annotation `prometheus.io/scrape` with value `true` SHOULD be recorded as
the `k8s.service.annotation.prometheus.io/scrape` attribute with value `"true"`.
- An annotation `data` with empty string value SHOULD be recorded as
the `k8s.service.annotation.data` attribute with value `""`.
**[30] `k8s.service.endpoint.address_type`:** The network address family or type of the endpoint.
This attribute aligns with the `addressType` field of the
[K8s EndpointSlice](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/).
It is used to differentiate metrics when a Service is backed by multiple address types
(e.g., in dual-stack clusters).
**[31] `k8s.service.endpoint.condition`:** The current operational condition of the service endpoint.
An endpoint can have multiple conditions set at once (e.g., both `serving` and `terminating` during rollout).
This attribute aligns with the condition fields in the [K8s EndpointSlice](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/).
**[32] `k8s.service.endpoint.zone`:** The zone where the endpoint is located, typically corresponding to a failure domain.
This attribute aligns with the `zone` field of endpoints in the
[K8s EndpointSlice](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/).
It enables zone-aware monitoring of service endpoint distribution and supports
features like [Topology Aware Routing](https://kubernetes.io/docs/concepts/services-networking/topology-aware-routing/).
If the zone is not populated (e.g., nodes without the `topology.kubernetes.io/zone` label),
the attribute value will be an empty string.
**[33] `k8s.service.label.`:** Examples:
- A label `app` with value `my-service` SHOULD be recorded as
the `k8s.service.label.app` attribute with value `"my-service"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.service.label.data` attribute with value `""`.
**[34] `k8s.service.publish_not_ready_addresses`:** Whether the Service is configured to publish endpoints before the pods are ready.
This attribute is typically used to indicate that a Service (such as a headless
Service for a StatefulSet) allows peer discovery before pods pass their readiness probes.
It aligns with the `publishNotReadyAddresses` field of the
[K8s ServiceSpec](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/service-v1/#ServiceSpec).
**[35] `k8s.service.selector.`:** These selectors are used to correlate with pod labels. Each selector key-value pair becomes a separate attribute.
Examples:
- A selector `app=my-app` SHOULD be recorded as
the `k8s.service.selector.app` attribute with value `"my-app"`.
- A selector `version=v1` SHOULD be recorded as
the `k8s.service.selector.version` attribute with value `"v1"`.
**[36] `k8s.service.traffic_distribution`:** Specifies how traffic is distributed to endpoints for this Service.
This attribute aligns with the `trafficDistribution` field of the
[K8s ServiceSpec](https://kubernetes.io/docs/reference/networking/virtual-ips/#traffic-distribution).
Known values include `PreferSameZone` (prefer endpoints in the same zone as the client) and
`PreferSameNode` (prefer endpoints on the same node, fallback to same zone, then cluster-wide).
If this field is not set on the Service, the attribute SHOULD NOT be emitted.
When not set, Kubernetes distributes traffic evenly across all endpoints cluster-wide.
**[37] `k8s.service.type`:** This attribute aligns with the `type` field of the
[K8s ServiceSpec](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/service-v1/#ServiceSpec).
**[38] `k8s.statefulset.annotation.`:** Examples:
- A label `replicas` with value `1` SHOULD be recorded
as the `k8s.statefulset.annotation.replicas` attribute with value `"1"`.
- A label `data` with empty string value SHOULD be recorded as
the `k8s.statefulset.annotation.data` attribute with value `""`.
**[39] `k8s.statefulset.label.`:** Examples:
- A label `replicas` with value `0` SHOULD be recorded
as the `k8s.statefulset.label.app` attribute with value `"guestbook"`.
- A label `injected` with empty string value SHOULD be recorded as
the `k8s.statefulset.label.injected` attribute with value `""`.
---
`k8s.container.status.reason` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `Completed` | The container has completed execution. |  |
| `ContainerCannotRun` | The container cannot run. |  |
| `ContainerCreating` | The container is being created. |  |
| `CrashLoopBackOff` | The container is in a crash loop back off state. |  |
| `CreateContainerConfigError` | There was an error creating the container configuration. |  |
| `ErrImagePull` | There was an error pulling the container image. |  |
| `Error` | There was an error with the container. |  |
| `ImagePullBackOff` | The container image pull is in back off state. |  |
| `OOMKilled` | The container was killed due to out of memory. |  |
---
`k8s.container.status.state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `running` | The container is running. |  |
| `terminated` | The container has terminated. |  |
| `waiting` | The container is waiting. |  |
---
`k8s.namespace.phase` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `active` | Active namespace phase as described by [K8s API](https://pkg.go.dev/k8s.io/api@v0.31.3/core/v1#NamespacePhase) |  |
| `terminating` | Terminating namespace phase as described by [K8s API](https://pkg.go.dev/k8s.io/api@v0.31.3/core/v1#NamespacePhase) |  |
---
`k8s.node.condition.status` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `false` | condition_false |  |
| `true` | condition_true |  |
| `unknown` | condition_unknown |  |
---
`k8s.node.condition.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `DiskPressure` | Pressure exists on the disk size—that is, if the disk capacity is low |  |
| `MemoryPressure` | Pressure exists on the node memory—that is, if the node memory is low |  |
| `NetworkUnavailable` | The network for the node is not correctly configured |  |
| `PIDPressure` | Pressure exists on the processes—that is, if there are too many processes on the node |  |
| `Ready` | The node is healthy and ready to accept pods |  |
---
`k8s.pod.status.phase` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `Failed` | All containers in the pod have terminated, and at least one container has terminated in a failure (exited with a non-zero exit code or was stopped by the system). |  |
| `Pending` | The pod has been accepted by the system, but one or more of the containers has not been started. This includes time before being bound to a node, as well as time spent pulling images onto the host. |  |
| `Running` | The pod has been bound to a node and all of the containers have been started. At least one container is still running or is in the process of being restarted. |  |
| `Succeeded` | All containers in the pod have voluntarily terminated with a container exit code of 0, and the system is not going to restart any of these containers. |  |
| `Unknown` | For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod. |  |
---
`k8s.pod.status.reason` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `Evicted` | The pod is evicted. |  |
| `NodeAffinity` | The pod is in a status because of its node affinity |  |
| `NodeLost` | The reason on a pod when its state cannot be confirmed as kubelet is unresponsive on the node it is (was) running. |  |
| `Shutdown` | The node is shutdown |  |
| `UnexpectedAdmissionError` | The pod was rejected admission to the node because of an error during admission that could not be categorized. |  |
---
`k8s.service.endpoint.address_type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `FQDN` | FQDN address type |  |
| `IPv4` | IPv4 address type |  |
| `IPv6` | IPv6 address type |  |
---
`k8s.service.endpoint.condition` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `ready` | The endpoint is ready to receive new connections. |  |
| `serving` | The endpoint is currently handling traffic. |  |
| `terminating` | The endpoint is in the process of shutting down. |  |
---
`k8s.service.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `ClusterIP` | ClusterIP service type |  |
| `ExternalName` | ExternalName service type |  |
| `LoadBalancer` | LoadBalancer service type |  |
| `NodePort` | NodePort service type |  |
---
`k8s.volume.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
| Value | Description | Stability |
| --- | --- | --- |
| `configMap` | A [configMap](https://v1-30.docs.kubernetes.io/docs/concepts/storage/volumes/#configmap) volume |  |
| `downwardAPI` | A [downwardAPI](https://v1-30.docs.kubernetes.io/docs/concepts/storage/volumes/#downwardapi) volume |  |
| `emptyDir` | An [emptyDir](https://v1-30.docs.kubernetes.io/docs/concepts/storage/volumes/#emptydir) volume |  |
| `local` | A [local](https://v1-30.docs.kubernetes.io/docs/concepts/storage/volumes/#local) volume |  |
| `persistentVolumeClaim` | A [persistentVolumeClaim](https://v1-30.docs.kubernetes.io/docs/concepts/storage/volumes/#persistentvolumeclaim) volume |  |
| `secret` | A [secret](https://v1-30.docs.kubernetes.io/docs/concepts/storage/volumes/#secret) volume |  |
## Deprecated Kubernetes Attributes
Describes deprecated k8s attributes.
**Attributes:**
| Key | Stability | Value Type | Description | Example Values |
| --- | --- | --- | --- | --- |
| `k8s.pod.labels.` | 
Replaced by `k8s.pod.label`. | string | Deprecated, use `k8s.pod.label` instead. | `my-app` |