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

Don't use unsupported batch/v1beta1 api for cron jobs #7289

Closed
jonesbr17 opened this issue Jul 21, 2022 · 0 comments · Fixed by #7301
Closed

Don't use unsupported batch/v1beta1 api for cron jobs #7289

jonesbr17 opened this issue Jul 21, 2022 · 0 comments · Fixed by #7301
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jonesbr17
Copy link

jonesbr17 commented Jul 21, 2022

What happened?

In Kubernetes 1.25, the batch/v1beta1 api goes unsupported. The dashboard is still attempting to use that api to list cronjobs, and fails on 1.25 clusters.

Logs from the kubernetes dashboard pod

2022/07/21 18:47:58 [2022-07-21T18:47:58Z] Incoming HTTP/2.0 GET /api/v1/cronjob/default?itemsPerPage=10&page=1&sortBy=d%!C(MISSING)creationTimestamp request from 2600:1700:9fa:0:f842:2501:9862:86e0: 
2022/07/21 18:47:58 Getting list of all cron jobs in the cluster
2022/07/21 18:47:58 [2022-07-21T18:47:58Z] Outcoming response to 2600:1700:9fa:0:f842:2501:9862:86e0 with 404 status code

What did you expect to happen?

Should use the supported api: batch/v1

How can we reproduce it (as minimally and precisely as possible)?

Attempt to view the dashboard of a 1.25 cluster. The Cron Jobs view will show a 404 error.

Anything else we need to know?

The references to "k8s.io/api/batch/v1beta1" in the code will need to be changed, like here for example.

What browsers are you seeing the problem on?

Chrome

Kubernetes Dashboard version

2.6.0

Kubernetes version

1.25

Go version

No response

Node.js version

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants