K8s naming convention rational and additional documentation#2252
K8s naming convention rational and additional documentation#2252lmolkova merged 10 commits intoopen-telemetry:mainfrom
Conversation
|
@open-telemetry/semconv-k8s-approvers made some further edits, I would appreciate a 2nd look. Should we make some exceptions for fields if they map directly to a field in k8s spec? |
|
@jinja2 @joaopgrassi could we resolve open discussion (it seems that some changes have been made)? |
| The following guidelines are specific to Kubernetes: | ||
|
|
||
| - [Service in Kubernetes](../non-normative/k8s-attributes.md#service-attributes) | ||
| - [Additional naming guidance for Kubernetes](../non-normative/naming-known-exceptions.md#kubernetes-naming-exceptions) |
There was a problem hiding this comment.
All: just a reminder that links should not point to page level 1 headings, because those don't exist in the published website. To see how this breaks the website build, visit https://github.com/open-telemetry/opentelemetry.io/actions/runs/15373995491/job/43256707459?pr=6948.
I'll submit a fix shortly.
There was a problem hiding this comment.
Fixes #2245
Changes
Adds rationale and further guidance for naming Kubernetes resources.
Merge requirement checklist
[chore]