Yonatan Kahana

@humblec since i've already tested the fix (https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/pull/120) with your branch, i can save you some time, even though they not released yet: 1. you will have change all the...

> There is some discussion in [kubernetes-csi/external-provisioner#737](https://github.com/kubernetes-csi/external-provisioner/pull/737) to figure out a consistent policy across all our repos. /hold

yes - it can be done. you can export multiple paths from your nfs server(s) and install as many provisioners as needed, you can read more about it in the...

@PraveenJP no, the best I can suggest is to use `helm template` with these settings and `kubectl apply` them where needed

the latest provisioner version is `4.0.2`. the latest helm version is `4.0.16` which defaults to `v4.0.2` image tag. it seems that most of the vulnerabilities already solved in our `master`...

> in addition the fixes already done to solve vulnerabilities , above new github action allows us to make sure we will keep it that way in the future by...

hi @darpan91, can you show us `kubectl describe all -Al app=nfs-subdir-external-provisioner` output? plus, can you make sure that you can manually mount the exported folder on the host machine?

/unassign @jackielii

we do have [`CHANGELOG.md`](https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/blob/master/CHANGELOG.md) to track changes in the provisioner itself. most of the releases are helm chart releases (sometimes its just changes in the README), are you talking about...

any updates about that? helm 2 is end-of-life and some charts are becoming not available to use in gravity, for example, it is enough that chart will use `deepCopy` in...