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

batch/v1beta1 CronJob is deprecated in v1.21+ #97

Closed
tommady opened this issue Feb 17, 2022 · 4 comments
Closed

batch/v1beta1 CronJob is deprecated in v1.21+ #97

tommady opened this issue Feb 17, 2022 · 4 comments

Comments

@tommady
Copy link

tommady commented Feb 17, 2022

Hi,
I am using the kubegres for a while in the EKS k8s v1.21 cluster and my log keeps showing the below message

batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob

I am not sure if it needed to be fixed right now, but I'd be glad to upgrade it.

I tried to create a PR,
(yet but following the contribution guide I have to open an issue first)

so here I am.
please guide me if I was doing anything wrong 🙇🏻
Thanks!

@samstride
Copy link

@tommady , that's just a warning, and such warnings are quite popular when things are deprecated.

Remember, people still run older version of k8s, for example, a cluster could be on say, v1.18 and if we try to use batch/v1 (instead of batch/v1beta1) on such a cluster, it might fail.

Applying this upgrade means that a minimum k8s version of 1.21. is needed. In the end it will be up to the maintainers to decide.

I think it might be better to update the readme with the supported k8s versions for each release.

@tommady
Copy link
Author

tommady commented Mar 13, 2022

@tommady , that's just a warning, and such warnings are quite popular when things are deprecated.

Remember, people still run older version of k8s, for example, a cluster could be on say, v1.18 and if we try to use batch/v1 (instead of batch/v1beta1) on such a cluster, it might fail.

Applying this upgrade means that a minimum k8s version of 1.21. is needed. In the end it will be up to the maintainers to decide.

I think it might be better to update the readme with the supported k8s versions for each release.

Oh yes you are right.
Sorry for the bothering.

@tommady tommady closed this as completed Mar 13, 2022
@sambonbonne
Copy link

I'm sorry to comment this issue but Kubernetes 1.25 is out now, it means Kubegres can't work anymore if a cluster is upgraded to the latest version. It can prevent some people to upgrade their cluster(s).

Maybe this issue should be re-opened? At least a warning on the README.md would be nice.

alex-arica added a commit that referenced this issue Sep 20, 2022
…131: Upgrade Kubegres to use the framework Kubebuilder 3.6.0
@alex-arica alex-arica reopened this Sep 20, 2022
@alex-arica
Copy link
Member

Kubegres 1.16 is compatible with Kubernetes 1.25
https://github.com/reactive-tech/kubegres/releases/tag/v1.16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants