Skip to content
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

k8s cluster receiver uses to be removed k8s API kinds #2457

Closed
duritong opened this issue Jan 10, 2023 · 3 comments
Closed

k8s cluster receiver uses to be removed k8s API kinds #2457

duritong opened this issue Jan 10, 2023 · 3 comments
Assignees
Labels
bug Something isn't working enhancement Improvement to existing capability

Comments

@duritong
Copy link

Currently the otel-collector requests batch/v1beta1 CronJob and autoscaling/v2beta2 HorizontalPodAutoscaler from the API

These API kinds in that API version are going to be removed in k8s 1.25:

This is with otel 0.67.0

@atoulme atoulme added bug Something isn't working enhancement Improvement to existing capability labels Jan 10, 2023
@atoulme
Copy link
Contributor

atoulme commented Jan 10, 2023

Thank you for the report. We'll take a look and report upstream as needed.

@jvoravong
Copy link
Contributor

If I recall properly, this receiver spins up and checks the k8s environment to make sure it uses the proper api for these two kinds. We should be safe once those deprecated apis disappear, we may want to clean up some dead code paths later.

Reference: open-telemetry/opentelemetry-collector-contrib#9523

@jvoravong
Copy link
Contributor

jvoravong commented Mar 29, 2023

I originally only scoped validation testing for this ticket to Kuberenetes v1.25 because that was all the was mentioned in conversations and tickets, thus I am closing ticket. I’ll get the right tickets filed for supporting Kubernetes v1.26 with v2 HPA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement Improvement to existing capability
Projects
None yet
Development

No branches or pull requests

3 participants