Skip to main content

Updating CronJob API version for Cloud Platform - removed Kubernetes v1.25

The batch/v1beta1 API version of CronJob is deprecated as of Kubernetes release v1.21, and will no longer served as of v1.25.

Cloud Platform users must ensure any CronJob manifests are migrated to use the batch/v1 API version, which is supported on our current cluster version (v1.24 as of writing).

Further details can be found within the Kubernetes deprecation guide

How to check and replace the deprecated apiVersion

Prerequisite: Install pluto to find out whether any of the manifest has any of the deprecated APIs.

brew install FairwindsOps/tap/pluto

To check if you are using deprecated apiVersion, run the following command:

pluto detect-all-in-cluster --namespace <your namespace>

If there is any deprecated apiVersion of CronJob, the output will look like this:

0928 17:32:43.721283   34578 request.go:697] Waited for 1.045015006s due to client-side throttling, not priority and fairness, request: GET:https://DF366E49809688A3B16EEC29707D8C09.gr7.eu-west-2.eks.amazonaws.com/apis/mutations.gatekeeper.sh/v1beta1?timeout=32s
E0928 17:32:44.561983   34578 discovery_api.go:117] Failed to retrieve: /v1, Resource=bindings the server does not allow this method on the requested resource
E0928 17:32:44.791255   34578 discovery_api.go:117] Failed to retrieve: authorization.k8s.io/v1, Resource=localsubjectaccessreviews the server does not allow this method on the requested resource
NAME                    KIND                      VERSION               REPLACEMENT      REMOVED   DEPRECATED   REPL AVAIL
test-cronjob            CronJob                   batch/v1beta1         batch/v1         true      true         true

For resources deployed using helm chart, the above list shows that the helm manifest deployed has the deprecated API version irrespective of the resource exists in the cluster.

Update apiVersion as the following example and apply the manifest:

apiVersion: batch/v1
kind: CronJob
metadata:
  name: hello
spec:
  schedule: "1 2-14 * * 0-1,5-6"
  successfulJobsHistoryLimit: 1
  failedJobsHistoryLimit: 1
  jobTemplate:
    spec:
      ttlSecondsAfterFinished: 100
      template:
        spec:
          containers:
          - name: hello
            image: bitnami/nginx
            args:
            - /bin/sh
            - -c
            - date; echo "Hello, World!"
          restartPolicy: OnFailure

Run the following command to check if the manifest is updated:

pluto detect-all-in-cluster --namespace <your namespace>

For additional information on creating CronJobs see here

This page was last reviewed on 9 January 2024. It needs to be reviewed again on 9 April 2024 by the page owner #cloud-platform .
This page was set to be reviewed before 9 April 2024 by the page owner #cloud-platform. This might mean the content is out of date.