external-provisioner
external-provisioner copied to clipboard
Sidecar container that watches Kubernetes PersistentVolumeClaim objects and triggers CreateVolume/DeleteVolume against a CSI endpoint
**What type of PR is this?** /kind feature **What this PR does / why we need it**: It adds TLS support for diagnostics HTTP server. In our cluster we require...
**What type of PR is this?** /kind feature **What this PR does / why we need it**: Support secret in NodeExpansion Call **Which issue(s) this PR fixes**: Fixes #499 **Special...
**What type of PR is this?** /kind cleanup **What this PR does / why we need it**: Embracing go-logr as logger has several advantages: - adding a certain prefix and/or...
**What type of PR is this?** /kind failing-test **What this PR does / why we need it**: test: add tirvy vulnerability scanner github action **Which issue(s) this PR fixes**: Fixes...
**What type of PR is this?** > /kind feature **What this PR does / why we need it**: Setting pv labels by cloning pvc's labels. We may add some custom...
**What type of PR is this?** > Uncomment only one ` /kind ` line, hit enter to put that in a new line, and remove leading whitespaces from that line:...
After a "resource exhausted" error and selecting a different node, the original provisioner instance keeps getting updates and/or continues to work on a PVC that it should ignore: ``` I0902...
As the title says, there is a great possibility that the application-specific `Operator` would leverage `PVC`'s `Annotation` for storing custom data. The custom data will tell storage provisioner how CSI...
capacity.go currently uses `Update` to change the capacity value. It might be more efficient to use `Patch`: - write a benchmark - compare both approaches
When deploying external-provisioner alongside the CSI driver on each node, there is one problem: if the scheduler picks a node which has no driver instance, then the volume is stuck...