Remove CronJobControllerV2 feature gate

[soltysh]

Part of kubernetes/enhancements#19

/assign @chrisnegus @pacoxu @alaypatel07

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

🔨 Explore the source changes: a55dd09

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/61851d920126d0000721fae8

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign savitharaghunathan after the PR has been reviewed.
You can assign the PR to them by writing /assign @savitharaghunathan in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/en/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pacoxu]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 58651fa0337eecd945db65b5e5c3fa70455c6830

[chrisnegus]

/lgtm

[tengqm]

I don't think we should remove this.

[soltysh]

@tengqm I did wonder about that too, but on the other hand that value is not present anymore, so you can't set it. It'll make senese for previous versions of k8s, but those have their own docs, that's why I've decided to go with it.

[reylejano]

I agree with @tengqm , these are left in even though we maintain docs for the current + past 4 releases

[soltysh]

Fair, I'm closing the PR in that case.

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[soltysh]

Rebased.

[chrisnegus]

@reylejano I'm going to look for a place for us to document that people reviewing release docs not remove content from the feature gate from previous releases, even if the feature no longer exists in the current release. Any suggestions where might be a good place to document that?

[reylejano]

@reylejano I'm going to look for a place for us to document that people reviewing release docs not remove content from the feature gate from previous releases, even if the feature no longer exists in the current release. Any suggestions where might be a good place to document that?

@chrisnegus
It's stated in:
https://kubernetes.io/docs/contribute/new-content/new-features/#pr-ready-for-review

If your feature is an Alpha or Beta feature and is behind a feature gate, make sure you add it to Alpha/Beta Feature gates table as part of your pull request. With new feature gates, a description of the feature gate is also required. If your feature is GA'ed or deprecated, make sure to move it from that table to Feature gates for graduated or deprecated features table with Alpha and Beta history intact.