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
Copy file name to clipboardExpand all lines: documentation/site/content/managing-domains/domain-on-pv/usage.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,6 +142,13 @@ for you.
142
142
The specifications of `PersistentVolume` and `PersistentVolumeClaim` are environment specific and often require information
143
143
from your Kubernetes cluster administrator. See [Persistent Storage](#references) in different environments.
144
144
145
+
##### PV and PVC requirements
146
+
- The Domain on PV requires that the PV and PVC are created with `Filesystem` volume mode, and `Block` volume mode is **not** supported.
147
+
- If you request the operator to create the PV and PVC, then it by default uses the `Filesystem` volume mode.
148
+
- If you plan to use an existing PV and PVC, then ensure that it was created with `Filesystem` volume mode.
149
+
- You must use a storage provider that supports the `ReadWriteMany` option.
150
+
- This operator will automatically set the owner of all files in the domain home on the persistent volume to `uid 1000` with `gid 0`. If you want to use a different user and group, then configure the desired `runAsUser` and `runAsGroup` in the security context under the `spec.serverPod.podSecurityContext` section of the Domain YAML file. The operator will use these values when setting the owner for files in the domain home directory.
151
+
145
152
For example, if you specify the specification of the `Persistent Volume` and `Persistent Volume Claim` in the domain resource YAML file,
146
153
then the operator will create the `PV` and `PVC`, and mount the persistent volume to the `/share` directory.
0 commit comments