CephRBD volume plugin and its csi migration support are removed

[carlory]

What type of PR is this?

/kind cleanup
/kind api-change
/kind deprecation

What this PR does / why we need it:

the CephRBD plugin and csi migration were deprecated in 1.28. In 1.31, we want to remove the support.

• deprecate csi migration for ceph rbd #118303
• deprecate RBD plugin from available in-tree drivers #118552

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

ACTION REQUIRED:

CephRBD volume plugin ( `kubernetes.io/rbd`) was removed in this release. And its csi migration support was also removed, so the `rbd` volume type became non-functional. Alternative is to use RBD CSI driver (https://github.com/ceph/ceph-csi/) in your Kubernetes Cluster. A re-deployment of your application is required to use the new driver if you were using `kubernetes.io/rbd` volume plugin before upgrading cluster version to 1.31+.

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

[k8s-ci-robot]

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.

[carlory]

/cc @humblec @saad-ali @dims @jsafrane

#124519 want to remove the file cmd/kube-controller-manager/app/plugins_providers.go. that file is used to register some volume plugins for the kube-controller-manager. i.e. kubernetes.io/rbd is one of them.

In 1.31, we plan to remove the kubernetes.io/rbd support. so let's merge this PR before #124519. It's more reasonable.

[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.

[dims]

/assign @msau42 @xing-yang

[dims]

@carlory hit me up after rebase and the CI jobs are green please

[carlory]

/remove-sig api-machinery

[carlory]

/retest

[carlory]

/test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer

[carlory]

/test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer

[carlory]

Ping @dims, the unrequired job /test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer always fails, I tested it on master branch and got same result #124776. #124729 is trying to fix it.

Do we need block this PR to be merged?

[dims]

Do we need block this PR to be merged?

Not for this PR.

/approve
/lgtm
/skip

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: ac4567120687ec2f775f36652ccf551cfb586f38

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: carlory, dims, jsafrane

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:

• cmd/kube-controller-manager/OWNERS [dims]
• cmd/kubelet/OWNERS [dims]
• pkg/features/OWNERS [dims,jsafrane]
• pkg/kubemark/OWNERS [dims]
• pkg/scheduler/framework/plugins/nodevolumelimits/OWNERS [dims,jsafrane]
• pkg/scheduler/framework/plugins/volumebinding/OWNERS [dims,jsafrane]
• pkg/volume/OWNERS [dims,jsafrane]
• staging/src/k8s.io/csi-translation-lib/OWNERS [dims,jsafrane]
• test/e2e/storage/OWNERS [dims,jsafrane]

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

[k8s-ci-robot]

@carlory: 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-e2e-kind-cloud-provider-loadbalancer	c8e91b9	link	false	/test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer

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-sigs/prow repository. I understand the commands that are listed here.