kubernetes-csi/external-provisioner

Remove dependencies on k8s.io/kubernetes

msau42 opened this issue · 11 comments

msau42 commented

What happened:
Packages from k8s.io/kubernetes were not designed to be imported and adds a lot of complexity to our dependency management where we need to inject "replace" statements into go.mod. It is also not supported by dependabot, which we would like to use to help automate our releases.

It looks like the dependencies are all coming from the e2e tests, which are importing the kubernetes e2e test framework libraries:
https://github.com/search?q=repo%3Akubernetes-csi%2Fexternal-provisioner+k8s.io%2Fkubernetes+path%3A*.go&type=code

@xing-yang I think we may want to move this out to its own repo, or maybe into the csi-test repo?

xing-yang commented

@msau42 Right, we need to think about this. Maybe csi-test repo is a better choice rather than creating another repo.

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

msau42 commented

/remove-lifecycle rotten

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale