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

E1229 16:38:40.249137 1 reflector.go:126] pkg/mod/k8s.io/client-go@v11.0.1-0.20190516230509-ae8359b20417+incompatible/tools/cache/reflector.go:94: Failed to list *v1beta1.CronJob: the server could not find the requested resource #698

Closed
tn8or opened this issue Dec 29, 2022 · 2 comments · Fixed by #706

Comments

@tn8or
Copy link

tn8or commented Dec 29, 2022

Hi,

Just installed keel 0.16.1 via the helm chart on my microk8s cluster, but my logs are flooded with messages like:

E1229 16:38:38.244452       1 reflector.go:126] pkg/mod/k8s.io/client-go@v11.0.1-0.20190516230509-ae8359b20417+incompatible/tools/cache/reflector.go:94: Failed to list *v1beta1.CronJob: the server could not find the requested resource
E1229 16:38:39.246345       1 reflector.go:126] pkg/mod/k8s.io/client-go@v11.0.1-0.20190516230509-ae8359b20417+incompatible/tools/cache/reflector.go:94: Failed to list *v1beta1.CronJob: the server could not find the requested resource
E1229 16:38:40.249137       1 reflector.go:126] pkg/mod/k8s.io/client-go@v11.0.1-0.20190516230509-ae8359b20417+incompatible/tools/cache/reflector.go:94: Failed to list *v1beta1.CronJob: the server could not find the requested resource

... Apparently, we're looking for CronJobs in the wrong api resource :-)

$ kubectl api-resources |grep cron
cronjobs                          cj           batch/v1                               true         CronJob

@mts-dyt
Copy link

mts-dyt commented Jan 26, 2023

it seems that keel is no more compatible with Kubernetes > 1.24.x
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#cronjob-v125

The batch/v1beta1 API version of CronJob is no longer served as of v1.25.

@zhulik
Copy link

zhulik commented Feb 6, 2023

Any updates on this? It makes keel hardly usable with kubernetes >=1.25 which is around for 6 months already.

Any hints on how this can be fixed? I could try to do it myself

rusenask added a commit that referenced this issue Mar 5, 2023
Resolves #698

In Kubernetes 1.25 several of the beta apis used by Keel are removed and replaced by the stable v1 equivalents. For those of us that are using Keel as a critical part of our deployment processes and who want to use current/future versions of Kubernetes this presents a huge problem.

I've created a build using the Kubernetes 1.24 libraries, updated golang, etc.

This change is breaking because it removes Helm 2 support. Helm 2 was EOL back in 2020.

I couldn't figure out how to get the ci/circleci: install-charts check working. This check is also failing on the master branch and I would appreciate any help in getting that or a similar check working.

Please let me know if there is anything I can do to speed up getting this merged released.
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

Successfully merging a pull request may close this issue.

3 participants