local-path-provisioner
local-path-provisioner copied to clipboard
rancher
Dynamically provisioning persistent local storage with Kubernetes
It would be great if the provisioner could create a btrfs subvolume with quota for each PVC. This would also give us snapshot and backup functionality using btrfs tools.
os: ubuntu20.04 platform: v1.20.6+k3s1 provisioner version: v0.0.19 root@w:~/init/deploy# kubectl get po ... video-cbccb664-b2hmb 0/1 Pending 0 2m35s video-mqtt-6bb5884f57-wn6x8 0/1 ContainerCreating 0 2m35s root@w:~/init/deploy# kubectl get po -nkube-system ... helper-pod-create-pvc-b3ce46c6-8b3a-4d89-ae3b-39ef6f904d9e 0/1...
Hi, I currently start using lpp for sorting out mounts in optane disks as a cache, I was wondering if capacity limitations will be implemented. Currently lack of limitations might...
Use busybox:1.33.1 - which is currently the latest available. The use of specific image tag also changes `imagePullPolicy` default from `Always` to `IfNotPresent` - which, among other things, behaves better...
...because depending on the helper Pod a different timeout may be needed. My use case is [cache-provisioner](https://github.com/mgoltzsche/cache-provisioner) that requires the helper Pod to synchronize the volume contents with an image...
Hello ! i am following the example to enable quotas but everytime i got an error: xfs_quotas: cannot setup path for mount /data:no such device or address i am sure...
Now there are only 4 threads working by default and no parameters are provided.
Regarding the documentation [Uninstall](https://github.com/rancher/local-path-provisioner#uninstall). > Before uninstallation, make sure the PVs created by the provisioner has already been deleted. Use kubectl get pv and make sure no PV with StorageClass...
I'm planning to nuke my cluster and recreate it. With GKE we can easily do this by making the PV/PVC part of the Chart/Template. Unfortunatly this seems to be more...
Fixing Helm chart is easy: add HELPER_IMAGE with env var to point to the proper address of busybox. But additionally imagePullSecrets has to be added to the create-xxxx pods generated...
