1
0

Compare commits

...

8 Commits

Author SHA1 Message Date
Kubernetes Prow Robot
4f955d1a21 Merge pull request #130 from crookedstorm/master
helm chart: allow persistentVolumeClaim in psp or pod never launches
2021-08-04 08:27:24 -07:00
Kubernetes Prow Robot
5f97c83a65 Merge pull request #111 from koivunen/patch-1
Describe NFS limitations
2021-08-01 12:13:21 -07:00
Brooke Storm
1271831fbd bump chart version 2021-07-31 20:42:33 -07:00
Brooke Storm
b74a204cda helm chart: allow persistentVolumeClaim in psp or pod never launches
Simple fix, but if you have podsecuritypolicy in your cluster, this
chart doesn't work without this change.
2021-07-30 16:35:33 -07:00
Koivunen
7b9f0e8db2 Update README.md 2021-06-30 15:38:57 +03:00
Kubernetes Prow Robot
e289a21201 Merge pull request #108 from larisoncarvalho/larisoncarvalho-patch-1
Update sed command for OpenShift in README.md
2021-06-28 20:54:40 -07:00
Koivunen
c848d9c7ce Describe NFS limitations 2021-06-03 19:46:29 +03:00
Larison Carvalho
f552bc6a79 Update README.md
Replace namespace in `./deploy/deployment.yaml` as well for OpenShift deployments
2021-06-02 12:31:02 +05:30
3 changed files with 7 additions and 3 deletions

View File

@@ -58,7 +58,7 @@ On OpenShift the service account used to bind volumes does not have the necessar
```sh ```sh
# Set the subject of the RBAC objects to the current namespace where the provisioner is being deployed # Set the subject of the RBAC objects to the current namespace where the provisioner is being deployed
$ NAMESPACE=`oc project -q` $ NAMESPACE=`oc project -q`
$ sed -i'' "s/namespace:.*/namespace: $NAMESPACE/g" ./deploy/rbac.yaml $ sed -i'' "s/namespace:.*/namespace: $NAMESPACE/g" ./deploy/rbac.yaml ./deploy/deployment.yaml
$ oc create -f deploy/rbac.yaml $ oc create -f deploy/rbac.yaml
$ oc adm policy add-scc-to-user hostmount-anyuid system:serviceaccount:$NAMESPACE:nfs-client-provisioner $ oc adm policy add-scc-to-user hostmount-anyuid system:serviceaccount:$NAMESPACE:nfs-client-provisioner
``` ```
@@ -206,4 +206,7 @@ The pipeline adds several labels:
* You also need to provide the `DOCKER_IMAGE` secret specifying your Docker image name, e.g., `quay.io/[username]/nfs-subdir-external-provisioner`. * You also need to provide the `DOCKER_IMAGE` secret specifying your Docker image name, e.g., `quay.io/[username]/nfs-subdir-external-provisioner`.
## NFS provisioner limitations/pitfalls
* The provisioned storage is not guaranteed. You may allocate more than the NFS share's total size. The share may also not have enough storage space left to actually accommodate the request.
* The provisioned storage limit is not enforced. The application can expand to use all the available storage regardless of the provisioned size.
* Storage resize/expansion operations are not presently supported in any form. You will end up in an error state: `Ignoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an external controller to process this PVC.`

View File

@@ -3,7 +3,7 @@ appVersion: 4.0.2
description: nfs-subdir-external-provisioner is an automatic provisioner that used your *already configured* NFS server, automatically creating Persistent Volumes. description: nfs-subdir-external-provisioner is an automatic provisioner that used your *already configured* NFS server, automatically creating Persistent Volumes.
name: nfs-subdir-external-provisioner name: nfs-subdir-external-provisioner
home: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner home: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner
version: 4.0.12 version: 4.0.13
kubeVersion: ">=1.9.0-0" kubeVersion: ">=1.9.0-0"
sources: sources:
- https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner - https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner

View File

@@ -13,6 +13,7 @@ spec:
volumes: volumes:
- 'secret' - 'secret'
- 'nfs' - 'nfs'
- 'persistentVolumeClaim'
hostNetwork: false hostNetwork: false
hostIPC: false hostIPC: false
hostPID: false hostPID: false