We briefly discussed this during the k8s SemConv WG meeting. There is no consensus on the document yet, but we decided to recommend moving it from the k8s resource section of the semantic conventions repo to service because it prescribes a way of populating values of service attributes, not attributes in k8s namespace.

We briefly discussed this during the k8s SemConv WG meeting. There is no consensus on the document yet, but we decided to recommend moving it from the k8s resource section of the semantic conventions repo to service because it prescribes a way of populating values of service attributes, not attributes in k8s namespace.

@open-telemetry/specs-semconv-approvers the service page is automatically generated - how can I move the content of this PR to the service page?

@open-telemetry/specs-semconv-approvers the service page is automatically generated - how can I move the content of this PR to the service page?

maybe as subsection(s) under https://github.com/open-telemetry/semantic-conventions/blob/main/docs/resource/README.md#service

@jsuereth @tigrannajaryan thanks for the positive feedback in the entities SIG call. A added the notes about the object hierarchy for service.name and value stability for service.instance.id. Please let me know if this addresses everything.

@jinja2 thanks for the detailed review - everything should be addressed now

@open-telemetry/specs-semconv-approvers please take a look

Approval from the k8s semconv and entities SIG has been granted now

@open-telemetry/specs-semconv-maintainers this seems like a good PR to include in https://changelog.opentelemetry.io. Should we add the label to it? 🤔

@open-telemetry/specs-semconv-maintainers this seems like a good PR to include in https://changelog.opentelemetry.io. Should we add the label to it? 🤔

sure! I don't think it strictly falls under "New semantic convention areas or stability changes, as well as releases", but I think it's always ok for @open-telemetry/specs-semconv-maintainers to call out particularly interesting or broadly relevant changes on https://changelog.opentelemetry.io

cc @austinlparker

@open-telemetry/specs-semconv-maintainers this seems like a good PR to include in https://changelog.opentelemetry.io. Should we add the label to it? 🤔

now that the content is moved to non-normative, it should automatically get published under https://opentelemetry.io/docs/specs/semconv/non-normative/ - IIUC

@zeitlinger can you change this line in CODEOWNERS to cover this new file also (I think /docs/non-normative/k8s-*)?

@open-telemetry/semconv-k8s-approvers does anyone else want to review before we merge? thanks!

@zeitlinger can you change this line in CODEOWNERS to cover this new file also (I think /docs/non-normative/k8s-*)?

thanks - added

@zeitlinger could you please resolve discussions (that are resolved)? Thanks!

@zeitlinger could you please resolve discussions (that are resolved)? Thanks!

@lmolkova all are resolved now 😄

need #1939 to be merged first to fix CI