A scheduled reports CronJob still uses batch/v1beta1 and fails on a newer cluster. Which migration fixes the application schedule object?
Select an answer to reveal the explanation.
Short Explanation
CronJob grew up: the beta house number is gone, and it lives at batch/v1 now. Update the apiVersion (and any field renames the stable schema needs) so the schedule object applies again.
Full Explanation
CronJob graduated; batch/v1 is the supported version on modern clusters, and v1beta1 has been removed. Kind changes to Deployment, stuffing YAML into Service annotations, or laptop log loops do not restore a valid CronJob API object.