Break out snapshot CRD libraries into separate repo

[msau42]

This makes it easier to update external-provisioner dependencies

[xing-yang]

This is a good idea. I'll work on this after the v1.13 release.

[msau42]

cc @nikhita is this something that the k8s publishing bot can help with?

[nikhita]

cc @nikhita is this something that the k8s publishing bot can help with?

Yes :)

From our conversation on Slack: iiuc this repo is supposed to be canonical source of truth and the client (and maybe the api) directory needs to be published/synced to another repo.

For this, we'll just need a set of rules like https://github.com/kubernetes/kubernetes/blob/master/staging/publishing/rules.yaml. Very roughly, it'll look something like:

rules:
- destination: published-client-repo-name
  library: true
  branches:
  - source:
      branch: master
      dir: pkg/client
    name: master
    dependencies:
    - repository: api
      branch: master
    - repository: apimachinery
      branch: master
    - repository: client-go
      branch: master

Edit: since this new repo would be in kubernetes-csi, the list of dependencies will be different...but the idea is that other "staging" repos in kubernetes-csi which the published repo depends on will be mentioned there.

We'll also need a cluster to run this bot. Maybe wg-k8s-infra can help with this? cc @dims

/cc @sttts

[nikhita]

To describe more concrete next steps: If we can get approval from sig-architecture (i'm guessing this falls under code-organization) and sig-storage, I can help move forward with this.

[msau42]

We discussed this in the sig-arch meeting today. The suggestion is to first look into switching over to go modules. If that doesn't work, then we can come back and discuss the staging/publishing bot option.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close