Release of Stable versions for k8s cluster specific receivers

[chetanmehta94]

Component(s)

receiver/kubeletstatsreceiver/
receiver/k8sclusterreceiver/

Describe the issue you're reporting

When can we expect stable releases for metrics for the following receivers:

1. k8sclusterreceiver
2. kubeletstatsreceiver

In the meantime, can they be used in production directly or should a production tested wrapper be used like splunk otel collector ?

[chetanmehta94]

Pinging code owners @dmitryax @TylerHelmuth @povilasv @ChrsMark

[chetanmehta94]

/label receiver/k8sclusterreceiver receiver/kubeletstatsreceiver

[povilasv]

There won't be stable releases any time soon, there is currently a lot of work in progress on semantic conventions for k8s and we will do a lot of renaming.

[chetanmehta94]

Thanks for your reply @povilasv. The field renaming is not a concern for us, we can take care of it during the upgrade time. I just wanted to be sure that the overall quality is fit for production :)

[povilasv]

We use it in production, it's fine :) Check out OTEL definition of stability - https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#stable

Note I don't think in contrib we have any component that is deemed stable, as it would limit our ability to do breaking changes.