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

cronjob UI broken after the kubernetes cluster upgrade to v1.26.3 #4162

Open
LQBing opened this issue Jul 10, 2023 · 1 comment
Open

cronjob UI broken after the kubernetes cluster upgrade to v1.26.3 #4162

LQBing opened this issue Jul 10, 2023 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@LQBing
Copy link

LQBing commented Jul 10, 2023

General remarks

Describe the bug

After Kubernetes cluster upgrade to v1.26.3, the 'Cronjob' detail fail, and create new 'Cronjob' fail

For UI issues please also add a screenshot that shows the issue.
image

I find the the documention from kubernetes say that they removed 'batch/v1beta1' in v1.25
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#cronjob-v125

Versions used(KubeSphere/Kubernetes)
KubeSphere: v3.3.2
Kubernetes: v1.26.3

Environment
How many nodes and their hardware configuration:

For example:
3 masters: 8cpu/8g
3 nodes: 8cpu/16g

(and other info are welcomed to help us debugging)

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Application Workloads'
  2. Click on 'Jobs'
  3. Click on 'Cronjobs'
  4. Click one cronjob with api version 'batch/v1'
  5. See error

Expected behavior
View existing cronjob fine & create new cronjob fine.

@LQBing LQBing added the kind/bug Categorizes issue or PR as related to a bug. label Jul 10, 2023
@VioZhang
Copy link
Member

Try 3.4.0 and it suits for 1.26 😊

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

Successfully merging a pull request may close this issue.

2 participants