You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -36,7 +36,7 @@ This chart requires the following in order to function:
36
36
* If `sharedStorage.create` is set, a PVC that relies on the default storage class will be created to generate the PersistentVolume.
37
37
Most Kubernetes environments do not have a default storage class that you can use with `ReadWriteMany` access mode out-of-the-box.
38
38
In this case, we recommend you disable `sharedStorage.create` and create your own `PersistentVolume` and `PersistentVolumeClaim`, then
39
-
mount them into the container by specifying the `pod.volumes` and `pod.volumeMounts` parameters.
39
+
mount them into the container by specifying the `pod.volumes` and `pod.volumeMounts` parameters, or by specifying your `PersistentVolumeClaim` using `sharedStorage.name` and `sharedStorage.mount`.
40
40
* If you cannot use a `PersistentVolume` to properly mount your data directory, you'll need to mount your data in the container
41
41
by using a regular [Kubernetes Volume](https://kubernetes.io/docs/concepts/storage/volumes), specified in `pod.volumes` and `pod.volumeMounts`.
Copy file name to clipboardExpand all lines: charts/rstudio-connect/README.md.gotmpl
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ This chart requires the following in order to function:
16
16
* If `sharedStorage.create` is set, a PVC that relies on the default storage class will be created to generate the PersistentVolume.
17
17
Most Kubernetes environments do not have a default storage class that you can use with `ReadWriteMany` access mode out-of-the-box.
18
18
In this case, we recommend you disable `sharedStorage.create` and create your own `PersistentVolume` and `PersistentVolumeClaim`, then
19
-
mount them into the container by specifying the `pod.volumes` and `pod.volumeMounts` parameters.
19
+
mount them into the container by specifying the `pod.volumes` and `pod.volumeMounts` parameters, or by specifying your `PersistentVolumeClaim` using `sharedStorage.name` and `sharedStorage.mount`.
20
20
* If you cannot use a `PersistentVolume` to properly mount your data directory, you'll need to mount your data in the container
21
21
by using a regular [Kubernetes Volume](https://kubernetes.io/docs/concepts/storage/volumes), specified in `pod.volumes` and `pod.volumeMounts`.
@@ -36,7 +36,7 @@ This chart requires the following in order to function:
36
36
* If `sharedStorage.create` is set, a PVC that relies on the default storage class will be created to generate the PersistentVolume.
37
37
Most Kubernetes environments do not have a default storage class that you can use with `ReadWriteMany` access mode out-of-the-box.
38
38
In this case, we recommend you disable `sharedStorage.create` and create your own `PersistentVolume` and `PersistentVolumeClaim`, then
39
-
mount them into the container by specifying the `pod.volumes` and `pod.volumeMounts` parameters.
39
+
mount them into the container by specifying the `pod.volumes` and `pod.volumeMounts` parameters, or by specifying your `PersistentVolumeClaim` using `sharedStorage.name` and `sharedStorage.mount`.
40
40
* If you cannot use a `PersistentVolume` to properly mount your data directory, you'll need to mount your data in the container
41
41
by using a regular [Kubernetes Volume](https://kubernetes.io/docs/concepts/storage/volumes), specified in `pod.volumes` and `pod.volumeMounts`.
42
42
* Alternatively, S3 storage can be used. See the next section for details.
@@ -118,6 +118,8 @@ The values are converted into configuration files in the necessary format via go
118
118
| service.type | string |`"NodePort"`| The service type (NodePort, LoadBalancer, etc.) |
119
119
| sharedStorage.accessModes | list |`["ReadWriteMany"]`| accessModes defined for the storage PVC (represented as YAML) |
120
120
| sharedStorage.create | bool |`false`| whether to create the persistentVolumeClaim for shared storage |
121
+
| sharedStorage.mount | bool |`false`| Whether the persistentVolumeClaim should be mounted (even if not created) |
122
+
| sharedStorage.name | string |`""`| The name of the pvc. By default, computes a value from the release name |
121
123
| sharedStorage.path | string |`"/var/lib/rstudio-pm"`| the path to mount the sharedStorage claim within the pod |
122
124
| sharedStorage.requests.storage | string |`"10Gi"`| the volume of storage to request for this persistent volume claim |
123
125
| sharedStorage.storageClassName | bool |`false`| storageClassName - the type of storage to use. Must allow ReadWriteMany |
Copy file name to clipboardExpand all lines: charts/rstudio-pm/README.md.gotmpl
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ This chart requires the following in order to function:
16
16
* If `sharedStorage.create` is set, a PVC that relies on the default storage class will be created to generate the PersistentVolume.
17
17
Most Kubernetes environments do not have a default storage class that you can use with `ReadWriteMany` access mode out-of-the-box.
18
18
In this case, we recommend you disable `sharedStorage.create` and create your own `PersistentVolume` and `PersistentVolumeClaim`, then
19
-
mount them into the container by specifying the `pod.volumes` and `pod.volumeMounts` parameters.
19
+
mount them into the container by specifying the `pod.volumes` and `pod.volumeMounts` parameters, or by specifying your `PersistentVolumeClaim` using `sharedStorage.name` and `sharedStorage.mount`.
20
20
* If you cannot use a `PersistentVolume` to properly mount your data directory, you'll need to mount your data in the container
21
21
by using a regular [Kubernetes Volume](https://kubernetes.io/docs/concepts/storage/volumes), specified in `pod.volumes` and `pod.volumeMounts`.
22
22
* Alternatively, S3 storage can be used. See the next section for details.
0 commit comments