-
Notifications
You must be signed in to change notification settings - Fork 74
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
Comments
@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, Applying this upgrade means that a minimum k8s version of I think it might be better to update the readme with the supported k8s versions for each release. |
Oh yes you are right. |
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 |
…131: Upgrade Kubegres to use the framework Kubebuilder 3.6.0
Kubegres 1.16 is compatible with Kubernetes 1.25 |
Hi,
I am using the kubegres for a while in the EKS k8s v1.21 cluster and my log keeps showing the below message
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!
The text was updated successfully, but these errors were encountered: