-
Notifications
You must be signed in to change notification settings - Fork 2.8k
k8sobjects receiver fails when some unrelated Kubernetes API is down #29706
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
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
…wn (#29707) **Description:** <Describe what has changed.> This change allows passing validation even some of K8S APIs is down, we will look thru the groups and resources for the ones available. <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** <Issue number if applicable> #29706 **Testing:** <Describe what testing was performed and which tests were added.> - manually in a kind cluster with metrics-server being down. **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. |
…wn (#29707) **Description:** <Describe what has changed.> This change allows passing validation even some of K8S APIs is down, we will look thru the groups and resources for the ones available. <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** <Issue number if applicable> open-telemetry/opentelemetry-collector-contrib#29706 **Testing:** <Describe what testing was performed and which tests were added.> - manually in a kind cluster with metrics-server being down. **Documentation:** <Describe the documentation added.>
Component(s)
receiver/k8sobjects
What happened?
Description
When unrelated Kubernetes API is down K8s Discovery client.ServerPreferredResources() will return a partial result and an error, we should ignore the error if it's unrelated.
Steps to Reproduce
Install metrics-server and delete deployment, launch k8sobjectreceiver to collect events.
Expected Result
no crashes
Actual Result
crashes with the error
Collector version
v0.90.1
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
Error: invalid configuration: receivers::k8sobjects: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
Additional context
No response
The text was updated successfully, but these errors were encountered: