-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Collect data from sidecars #29623
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I believe this could affect any component which collects pod request metrics. Such as https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awscontainerinsightreceiver I believe this is one of the important bits from the linked blog post on sidecar containers.
We can also see that the k8s API changed the way in which Pod Requests are calculated due to sidecar containers. |
Pinging code owners for receiver/awscontainerinsight: @Aneurysm9 @pxaws. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/k8scluster
Is your feature request related to a problem? Please describe.
The Sidecars feature is enabled by default in Kubernetes 1.29 (https://kubernetes.io/blog/2023/08/25/native-sidecar-containers/). This receiver (and maybe more) should be updated to support them.
Describe the solution you'd like
This code only reports metrics from from containers in the pod. Sidecars are an init container with a restart policy of Always and run for the lifetime of the pod, so they should probably be reported here as well.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: