New repo for kubernetes-incubator/external-storage/ceph

[cofyc]

New Repo, Staging Repo, or migrate existing

new repository

Requested name for new repository

sig-storage-ceph-provisioner

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

@rootfs
@wongma7
@cofyc

If not a staging repo, who should have write access

@rootfs
@wongma7
@cofyc

If a new repo, who should be listed as approvers in OWNERS

@rootfs
@wongma7
@cofyc

If a new repo, who should be listed in SECURITY_CONTACTS

@rootfs
@wongma7
@cofyc

What should the repo description be

Ceph external provisioners for rbd and cephfs

What SIG and subproject does this fall under in sigs.yaml

this is part of the external-storage subproject for sig-storage

Approvals

Need sig-storage approval from: @saad-ali and @wongma7
See kubernetes-retired/external-storage#1083.

Additional context for request

Current, kubernetes-incubator/external-storage houses a lot of different provisioners. Different provisioners may have theirs own dependency/ci requirements or development/release workflow, etc. As for dependency management, it resulted that external-storage repo has huge dependency chain, and updating dependencies for one provisioner requires updating it for all provisioners which is not convenient and may have risk.
Xref: #244
Xref: #88

/area github-repo

[cofyc]

cc @saad-ali @wongma7
What do you think?

[wongma7]

sgtm 👍

[saad-ali]

Ceph external provisioners for rbd and cephfs

Why is this needed? Why add a ceph external-provisioner? There is already a Ceph CSI driver (https://github.com/ceph/ceph-csi) that handles dynamic provisioning.

[saad-ali]

Oh I see it was a legacy external-provisioner (https://github.com/kubernetes-incubator/external-storage/tree/master/ceph) and because that repo is being split up, the ask is for a new home for this. My recommendation would be to deprecate this Ceph external-provisioner, and not find a new home for it, and recommend folks use the Ceph CSI driver.

[wongma7]

I think it is too soon to deprecate, the csi driver is still alpha. There could be a note in the README to say that someday it will be made obsolete by the CSI driver and to consider using that first, but we can't recommend switching yet. The provisioner project's still healthy and will benefit from having separate release scheme/cadence/branching (e.g. different images for mimic/luminous/etc...). When csi is matures it will be easier to steer people watching the repo in the right direction

[cblecker]

@saad-ali is this still needed?

[nikhita]

/lifecycle stale

Marking this as stale.. please advise if this is still required.

[wongma7]

ceph org may be a better home for this. @cofyc any progress on that?

[cofyc]

/close

[k8s-ci-robot]

@cofyc: Closing this issue.

Details

In response to this:

/close

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.