Area(s)
area:k8s
What's missing?
As part of the K8s SemConv stability work we should think forwards and define k8s namespace labels and annotations that will be used by the Opentelemetry Collector in the future to avoid multiple versions of label and annotations attributes present in the components. Currently there is already a usage of k8s.namespace.labels.<key> and k8s.namespace.annotations.<key> present in k8sattributes processor.
We should try to align it with the existing Pod and Node strategy.
Describe the solution you'd like
k8s.namespace.label.<key>
k8s.namespace.annotation.<key>
Area(s)
area:k8s
What's missing?
As part of the K8s SemConv stability work we should think forwards and define k8s namespace labels and annotations that will be used by the Opentelemetry Collector in the future to avoid multiple versions of label and annotations attributes present in the components. Currently there is already a usage of
k8s.namespace.labels.<key>andk8s.namespace.annotations.<key>present in k8sattributes processor.We should try to align it with the existing Pod and Node strategy.
Describe the solution you'd like
k8s.namespace.label.<key>k8s.namespace.annotation.<key>