Propose a new K8s SemConv SIG project

[ChrsMark]

The Opentelemetry community would like to work on K8s Semantic Conventions in order to add any missing attributes and/or metrics and stabilize the existing ones. The primary goal of this is to help with the adoption of the respective OTel Collector receivers and processors.

TODOS:

1. Expand the list of domain experts
2. Define meeting time
3. Create the slack channel, agenda doc, calendar event, project board

[ChrsMark]

Pinging relevant people here. Please explicitly ask for being included in the domain experts list if you are not already.

/cc @open-telemetry/semconv-k8s-approvers @open-telemetry/semconv-container-approvers @TylerHelmuth @dmitryax @dashpole @jinja2 @frzifus @mx-psi @povilasv @jamesmoessis @AlexanderWert @rogercoll @braydonk @jsuereth

Feel free to advertise this and/or proposing people for joining this project.

[rogercoll]

Thanks for pushing this SIG @ChrsMark ! I think it is really needed to standardize all the k8s and container metrics, which should help with the alignment between the different collector's related receivers (kubeletstats, dockerstats, podmanstats, etc.)

I would gladly join the SIG and share my domain expertise, specially in the containers area.

[braydonk]

I support the new SIG! I don't have enough expertise in the general k8s area to join, but will spread the word with some more knowledgeable folks to see who would be interested.

[jaronoff97]

As a maintainer of the operator and helm charts, id love to be added to this effort. It would be great if we could improve and standardize more in the k8s world.

[gyliu513]

Thanks @ChrsMark , happy to see this proposal, can we extend this SIG a little bit to cover k8s cost as well by https://github.com/opencost?

[ChrsMark]

Thank's for the suggestion @gyliu513!
This SIG will initially focus on the k8s.* (and a bit of container.*) namespace. The primary focus is to stabilize the basic resource attributes and metrics which are already widely used by the Collector. Then of course we can examine additional semantic conventions.

@gyliu513 do you have specific semantic conventions in mind that you would like to introduce? If so, you can always propose them with an issue and it could be added in the SIG's backlog.

[jsuereth]

A few things you'll need to work w/ Entities/Semconv group on ->

(1) Should type on resource semconv have all identifying attributes or locally identifying attributes.

E.g. k8s.namespace today only contains k8s.namespace.name. How does the interact with k8s.pod type? Do I always put both when I can?

(2) Discovery of these attributes (locally and externally) (a.k.a. multi-observer problem). I'd like if each of the resources (and attributes) had some description in the markdown for how they can be discovered BOTH inside an SDK and externally (e.g. via collector).

[ChrsMark]

We can note them down on a SemConv issue, right? I will create one.

[jaronoff97]

I would also note this one which was closed from inactivity but still remains problematic

[dmitryax]

Thanks for starting the SIG! I'm happy to help with this effort