csi-driver-nfs icon indicating copy to clipboard operation
csi-driver-nfs copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-csi

Generic native CSI Driver should not have reference to specific vendor packages

Open sean-freeman opened this issue 1 year ago • 10 comments

What happened:

Generic native CSI Driver should not have reference to specific vendor packages. Code should not contain az specific references in code

Vendor specific code within a generic driver should not exist, unless additional handling is required for functionality with that vendor. Unnecessary dependency is created on cloud-provider-azure, with reference to cloud-provider-azure/pkg/cache as a wrapper for k8s.io/client-go/tools/cache

What you expected to happen:

N/A

How to reproduce it:

N/A

Anything else we need to know?:

Environment:

  • CSI Driver version: all
  • Kubernetes version (use kubectl version): all
  • OS (e.g. from /etc/os-release): all
  • Kernel (e.g. uname -a): all

sean-freeman avatar Aug 12 '24 15:08 sean-freeman

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 avatar Nov 10 '24 15:11 k8s-triage-robot

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

k8s-triage-robot avatar Dec 10 '24 16:12 k8s-triage-robot

/remove-lifecycle rotten

sean-freeman avatar Dec 11 '24 12:12 sean-freeman

@andyzhangx Please acknowledge

sean-freeman avatar Dec 11 '24 12:12 sean-freeman

@sean-freeman do you have time to contribute on this?

andyzhangx avatar Dec 11 '24 13:12 andyzhangx

@andyzhangx I am engaged in multiple other open source projects of significant scale, I cannot provide help here. I noticed this dependency problem by accident when performing K8S testing, I am not a K8S Dev and would be lost in this CSI code.

sean-freeman avatar Dec 11 '24 13:12 sean-freeman

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 avatar Mar 11 '25 13:03 k8s-triage-robot

/remove-lifecycle stale

sean-freeman avatar Mar 11 '25 13:03 sean-freeman

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 avatar Jun 09 '25 13:06 k8s-triage-robot

/remove-lifecycle stale

sean-freeman avatar Jun 09 '25 23:06 sean-freeman

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 avatar Sep 08 '25 00:09 k8s-triage-robot

/remove-lifecycle stale

sean-freeman avatar Sep 12 '25 11:09 sean-freeman