Add k8s.node semantic convention

CHANGELOG.md

@@ -55,6 +55,7 @@ Updates:
 - Clarify that Jaeger/Zipkin exporters must rely on the default Resource to
   get service.name if none was specified.
   ([#1386](https://github.com/open-telemetry/opentelemetry-specification/pull/1386))
+- Add `k8s.node` semantic conventions ([#1390](https://github.com/open-telemetry/opentelemetry-specification/pull/1390))
 
 ## v0.7.0 (11-18-2020)
 

semantic_conventions/resource/k8s.yaml

@@ -10,6 +10,22 @@ groups:
           The name of the cluster.
         examples: ['opentelemetry-cluster']
 
+  - id: k8s.node
+    prefix: k8s.node
+    brief: >
+      A Kubernetes Node object.
+    attributes:
+      - id: name
+        type: string
+        brief: >
+          The name of the Node.
+        examples: ['node-1']
+      - id: uid
+        type: string
+        brief: >
+          The UID of the Node.
+        examples: ['1eb3a0c6-0477-4080-a9cb-0cb7db65c6a2']
+
   - id: k8s.namespace
     prefix: k8s.namespace
     brief: >

specification/resource/semantic_conventions/k8s.md

@@ -25,6 +25,19 @@ Kubernetes object, but "name" is usually more user friendly so can be also set.
 | `k8s.cluster.name` | string | The name of the cluster. | `opentelemetry-cluster` | No |
 <!-- endsemconv -->
 
+## Node
+
+**type:** `k8s.node`
+
+**Description:** A Kubernetes Node.
+
+<!-- semconv k8s.node -->
+| Attribute  | Type | Description  | Examples  | Required |
+|---|---|---|---|---|
+| `k8s.node.name` | string | The name of the Node. | `node-1` | No |
+| `k8s.node.uid` | string | The UID of the Node. | `1eb3a0c6-0477-4080-a9cb-0cb7db65c6a2` | No |
+<!-- endsemconv -->
+
 ## Namespace
 
 Namespaces provide a scope for names. Names of objects need to be unique within