Open hugodopradofernandes opened 3 years ago
batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob
I can confirm this is still happening with apiVersion: batch/v1
CronJobs using 0.25.0
in windows
This should be a simple fix. Any chance to get a new release?
I'm facing the same issue when browsing a namespace with Cron jobs enabled (e.g. a nextcloud deployment from this chart https://github.com/nextcloud/helm/tree/master/charts/nextcloud). The cron jobs use the "batch/v1" API and the kubernetes version is v1.22.
I just hit the same issue.
Same issue here, on kubernetes v1.23.3
same issue
Same issue
same issue
Same issue, even after changing all cron jobs to be v1 instead of v1beta1
Same issue. Using batch/v1
I'm pretty sure the following needs to be updated to batchv1. I haven't fully vetted if it isn't going to break anything, but roughly fixed the issue at hand.
What steps did you take and what happened: Namespace does not load at all on Octant when it tries to display cronjobs.
What did you expect to happen: Items from workspace to load - cronjobs causing the issue. When displaying only workloads, works fine. When cronjob is part of the view, it fails
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] Namespace that Octant could not list
Log error that repeats when trying to load this namespace:
Environment:
octant version
):kubectl version
): v1.21.4