-
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
[receiver/k8scluster] deprecate k8s.kubeproxy.version attr #29748
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I agree, thanks for the issue. Opened PR for this -> #29768 |
…te (#29768) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Deprecating k8s.kubeproxy.version resource attribute **Link to tracking Issue:** <Issue number if applicable> #29748 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.>
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. |
…31180) **Description:** Remove deprecated resource attribute. Deprecation happened in 0.92.0 **Link to tracking Issue:** #29748 (comment)
…pen-telemetry#31180) **Description:** Remove deprecated resource attribute. Deprecation happened in 0.92.0 **Link to tracking Issue:** open-telemetry#29748 (comment)
Component(s)
receiver/k8scluster
Is your feature request related to a problem? Please describe.
k8scluster receiver has the optional attribute
k8s.kubeproxy.version
, the value of which is set to thev1.Node
field.status.nodeInfo.kubeProxyVersion
. This field is not accurate and is set by kubelet, which does not actually know the kube-proxy version, or even if kube-proxy is running. k8s v1.29 starts the deprecation process of this field.Describe the solution you'd like
We should start deprecation of the
k8s.kubeproxy.version
attribute given the value is not accurate, and k8s itself plans to remove it.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: