kubernetes-sigs / kubernetes-sigs/node-feature-discovery
Security Vulnerability: Go Package: github.com/grpc-ecosystem/go-grpc-prometheus - End of Life Notification (EOL)
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 317
- Avg merge
- 21h 39m
- Merged PRs (30d)
- 5
Description
Hello Team,
The latest node-feature-discovery (v0.18.3) still uses grpc-ecosystem/go-grpc-prometheus package which reached its EOL -> https://github.com/kubernetes-sigs/node-feature-discovery/blob/v0.18.3/go.mod#L83
Based on this issue -> #2287, We got to know that, this is due to indirect dependency from kubernetes.
Kubernetes released a new version v1.36.0 (https://github.com/kubernetes/kubernetes/releases/tag/v1.36.0) which contains the fix.
Can we please upgrade node-feature-discovery to use the latest kubernetes? Currently it uses Kubernetes v1.34.1 (https://github.com/kubernetes-sigs/node-feature-discovery/blob/v0.18.3/go.mod#L36)
Thanks in advance
Contributor guide
Research direction
Start with go.mod at the Kubernetes v1.34.1 dependency referenced in the issue, then compare it with the Kubernetes v1.36.0 release information. Update node-feature-discovery to the newer Kubernetes version and verify that the resolved dependency no longer uses github.com/grpc-ecosystem/go-grpc-prometheus.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100