-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release of Stable versions for k8s cluster specific receivers #36932
Comments
Pinging code owners @dmitryax @TylerHelmuth @povilasv @ChrsMark |
/label receiver/k8sclusterreceiver receiver/kubeletstatsreceiver |
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. |
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 :) |
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. |
Pinging code owners for receiver/kubeletstats: @dmitryax @TylerHelmuth @ChrsMark. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label. |
Pinging code owners for receiver/k8scluster: @dmitryax @TylerHelmuth @povilasv @ChrsMark. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label. |
It looks like this issue has been sufficiently addressed, but feel free to ask more questions if you have any! |
Component(s)
receiver/kubeletstatsreceiver/
receiver/k8sclusterreceiver/
Describe the issue you're reporting
When can we expect stable releases for metrics for the following receivers:
In the meantime, can they be used in production directly or should a production tested wrapper be used like splunk otel collector ?
The text was updated successfully, but these errors were encountered: