Rename ScheduledJobs to CronJobs

[soltysh]

I went with @smarterclayton idea of registering named types in schema. This way we can support both the new (CronJobs) and old (ScheduledJobs) resource name. Fixes #32150.

fyi @erictune @caesarxuchao @janetkuo

Not ready yet, but getting close there...

Release note:

Rename ScheduledJobs to CronJobs.

---

This change is

[soltysh]

@smarterclayton after registering ScheduledJobs with in pkg/apis/batch/v2alpha1/register.go using scheme.AddKnownTypeWithName(SchemeGroupVersion.WithKind("ScheduledJob"), &CronJob{}) I'm getting failures when invoking pkg/api/defaulting_test.go. The error is pointing me as if ClusterRoleBindingList didn't need defaulting. I'm 100% positive this is caused by that AddKnownTapeWithName call, any ideas what I might be missing here? I'll add I've tried registering defaulter for ScheduledJob and that didn't help. Or maybe that defaulting_test.go doesn't handle SJ registered that way properly?

[smarterclayton]

It's hard to help debug without seeing the actual failure.

[soltysh]

It's hard to help debug without seeing the actual failure.

nvmd, the rebase solved the problem

[soltysh]

@sttts fyi

[k8s-ci-robot]

Jenkins GCE etcd3 e2e failed for commit 4483764c23de80a8542f758972d243e09937b884. Full PR test history.

The magic incantation to run this job again is @k8s-bot gce etcd3 e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GKE smoke e2e failed for commit 4483764c23de80a8542f758972d243e09937b884. Full PR test history.

The magic incantation to run this job again is @k8s-bot cvm gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GCI GKE smoke e2e failed for commit 4483764c23de80a8542f758972d243e09937b884. Full PR test history.

The magic incantation to run this job again is @k8s-bot gci gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GCE e2e failed for commit 4483764c23de80a8542f758972d243e09937b884. Full PR test history.

The magic incantation to run this job again is @k8s-bot cvm gce e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins Kubemark GCE e2e failed for commit 4483764c23de80a8542f758972d243e09937b884. Full PR test history.

The magic incantation to run this job again is @k8s-bot kubemark e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GCI GCE e2e failed for commit 4483764c23de80a8542f758972d243e09937b884. Full PR test history.

The magic incantation to run this job again is @k8s-bot gci gce e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[soltysh]

This is ready for review @smarterclayton, @janetkuo, @erictune @caesarxuchao I'd like to merge it for 1.5. The current state of this PR allows transparently accessing CronJobs or ScheduledJobs. Everything is stored as CronJobs, so no matter what you're creating it'll work in future versions. Unfortunately that also means what was created previously will have to be re-created, but I guess that's a minor issue. The only problem I'm struggling right now, is that I can't get SJ to appear in the swagger, which means kubectl create needs to be run with --validate=false, but that's the only limitation I'll try to fix asap.

fyi @justinsb @chrislovecnm

[soltysh]

Fixed bazel.

[smarterclayton]

Yeah, there was a lot of code added to make this work well for minions, and it only slightly rotted.

[soltysh]

Changing name looks easy. Wonder if we want to do that for the petset renaming as well.

Yup, since I know the knobs already I can volunteer to add it, if that's desirable.

[smarterclayton]

/lgtm

[caesarxuchao]

Petset also changed the version from v1alpha1 to v1beta1, I bet that will complicate things. @erictune seems to be fine with abandoning petset completely.

[caesarxuchao]

LGTM. Thanks.

[soltysh]

Rebased, re-applying the label back.

[k8s-ci-robot]

Jenkins verification failed for commit fdcdc95c3255d7c81f13956d6e4eaf78e7aafae4. Full PR test history.

The magic incantation to run this job again is @k8s-bot verify test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[soltysh]

Fixed the verification failure (codegen).

[k8s-github-robot]

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue