We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
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:
Expected behavior View existing cronjob fine & create new cronjob fine.
The text was updated successfully, but these errors were encountered:
Try 3.4.0 and it suits for 1.26 😊
Sorry, something went wrong.
fix: workspace gateway styles (kubesphere#4162)
8a33e43
Co-authored-by: 51wangping <253423846@qq.com>
Successfully merging a pull request may close this issue.
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.
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:
Expected behavior
View existing cronjob fine & create new cronjob fine.
The text was updated successfully, but these errors were encountered: