Revert "Introduce APIs to support multiple ClusterCIDRs (#108290)"

[JamesLaverack]

This reverts commit b9792a9.

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This change reverts #108290, see kubernetes/enhancements#2593 (comment) for further details.

API Changes:

• Removes networking.k8s.io/v1alpha1 API group
• Removes ClusterCIDRConfig type in networking.k8s.io/v1alpha1 API group

Which issue(s) this PR fixes:

NONE

Special notes for your reviewer:

Please bring comments about the nature of this revert to the k/enhancements issue here: kubernetes/enhancements#2593 (comment)

Does this PR introduce a user-facing change?

Remove a v1alpha1 networking API for ClusterCIDRConfig

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]:  https://github.com/kubernetes/enhancements/pull/2594

/sig network
/release-blocker
/priority critical-urgent
/milestone 1.24

[k8s-ci-robot]

@JamesLaverack: The provided milestone is not valid for this repository. Milestones in this repository: [next-candidate, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26]

Use /milestone clear to clear the milestone.

In response to this:

This reverts commit b9792a9.

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This change reverts #108290, see kubernetes/enhancements#2593 (comment) for further details.

API Changes:

• Removes networking.k8s.io/v1alpha1 API group
• Removes ClusterCIDRConfig type in networking.k8s.io/v1alpha1 API group

Which issue(s) this PR fixes:

NONE

Special notes for your reviewer:

Please bring comments about the nature of this revert to the k/enhancements issue here: kubernetes/enhancements#2593 (comment)

Does this PR introduce a user-facing change?

Remove a v1alpha1 networking API for ClusterCIDRConfig

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]:  https://github.com/kubernetes/enhancements/pull/2594

/sig network
/release-blocker
/priority critical-urgent
/milestone 1.24

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@JamesLaverack: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[JamesLaverack]

/milestone v1.24

[saschagrunert]

/lgtm

From a SIG Release perspective.

[sftim]

/retest-required

[sftim]

D'oh, I meant /retest - sorry

[liggitt]

I don't have context on the PR being reverted, will defer to Tim on this one
/unassign

[k8s-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[lavalamp]

I agree that reverting this is probably the right thing to do, I'll let @thockin give the approve though.

[thockin]

Sigh.

I'm a little grumpy about this but not enough to argue it against the decision of release folks.

/lgtm
/approve

[liggitt]

CI failure is legitimate, need to regen openapi

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[saschagrunert]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JamesLaverack, justaugustus, saschagrunert, thockin

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

The pull request process is described here

Needs approval from an approver in each of these files:

• api/OWNERS [thockin]
• cmd/kube-apiserver/OWNERS [thockin]
• hack/OWNERS [thockin]
• pkg/apis/OWNERS [thockin]
• pkg/controlplane/OWNERS [thockin]
• pkg/generated/openapi/OWNERS [thockin]
• pkg/kubeapiserver/OWNERS [thockin]
• pkg/printers/OWNERS [thockin]
• pkg/registry/OWNERS [thockin]
• plugin/pkg/auth/authorizer/OWNERS [thockin]
• staging/src/k8s.io/api/OWNERS [thockin]
• staging/src/k8s.io/client-go/OWNERS [thockin]
• staging/src/k8s.io/kubectl/OWNERS [thockin]
• test/integration/etcd/OWNERS [thockin]
• vendor/OWNERS [thockin]

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

[liggitt]

Refetch tags before you regen the openapi, your local tags are incorrectly including v1alpha1 flowcontrol APIs which are no long served in 1.24

[dims]

/lgtm

[k8s-ci-robot]

@JamesLaverack: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-conformance-kind-ipv6-parallel	7d57d5c	link	false	/test pull-kubernetes-conformance-kind-ipv6-parallel

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.