local-path-provisioner
local-path-provisioner copied to clipboard
rancher
Dynamically provisioning persistent local storage with Kubernetes
pvc indefinately stays pending tried following commands with v0.0.21,v0.0.23,v0.0.24 kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/v0.0.24/deploy/local-path-storage.yaml kubectl create -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/examples/pvc/pvc.yaml
Hello local-path-provisioner community! Security scanners in our org complain about excessive RBAC permissions granted to `local-path-provisioner` through the [`local-path-provisioner-role` `ClusterRole`](https://github.com/rancher/local-path-provisioner/blob/master/deploy/chart/local-path-provisioner/templates/clusterrole.yaml), specifically [`*` granted for `["endpoints", "persistentvolumes", "pods"]`](https://github.com/rancher/local-path-provisioner/blob/master/deploy/chart/local-path-provisioner/templates/clusterrole.yaml#L12-L14). I wonder, does...
I'm not sure how the various deployment elements are created, but it would be nice if the `rancher/local-path-provisioner` bits where explicit about `docker.io` (ie . `docker.io/rancher/local-path-provisioner`)
It would be nice if there was a network policy for the `local-path-provisioner` pod that only permitted the required traffic. I don't think any `ingress` is required. If I understand...
To specify (at global level) the type of volume you want the provisioner to create, you can add the following annotation to the StorageClass: ```yaml annotations: defaultVolumeType: ``` I would...
do this provisioner support pvc autoscale ? eg: edit xx-pvc used by this local-path-provisioner via sc this can VolumeExpansion large ? thx. i used rancher/local-path-provisioner:v0.0.23, but some question: Ignoring the...
In my config everything seems fine but for some reason the volume is created in the default folder. I thought maybe it was related to the permissions, but when I...
Moved from https://github.com/k3s-io/k3s/issues/6660. I have no idea who to report this bug to, so I'm going to duplicate the report a few places. kubernetes: https://github.com/kubernetes/kubernetes/issues/114583 core-dump-handler: https://github.com/IBM/core-dump-handler/issues/119 **Environmental Info:** K3s...
Looks like the proper way to ensure single-pod access to volume is using a new `ReadWriteOncePod` [access mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) introduced [here](https://kubernetes.io/blog/2021/09/13/read-write-once-pod-access-mode-alpha/) in Kubernetes 1.22 It would be nice to have this...
