docs: add note about storage class defaults

content/docs/1.6.0/nodes-and-volumes/volumes/create-volumes.md

@@ -50,7 +50,8 @@ When the Pod is deployed, the Kubernetes master will check the PersistentVolumeC
     #  ]'
     ```
 
-    In particular, starting with v1.4.0, the parameter `mkfsParams` can be used to specify filesystem format options for each StorageClass.
+    In particular, starting with v1.4.0, the parameter `mkfsParams` can be used to specify filesystem format options for each StorageClass.  
+    Parameters may be omitted from the StorageClass specification.  When the storage class is used to create a PV and a volume, parameters that are not specified will generally be set using a default value taken from the global settings.  See [here](../../../references/storage-class-parameters) for the list of storage class parameters, and [here](../../../references/settings) for the full list of global settings.
 
 2. Create a Pod that uses Longhorn volumes by running this command:
 
@@ -114,7 +115,7 @@ If the PVC names a StorageClass, Kubernetes will:
 
 ### Creating Longhorn Volumes with the Longhorn UI
 
-Since the Longhorn volume already exists while creating PV/PVC, a StorageClass is not needed for dynamically provisioning Longhorn volume. However, the field `storageClassName` should be set in PVC/PV, to be used for PVC bounding purpose. And it's unnecessary for users to create the related StorageClass object.
+Since the Longhorn volume already exists while creating PV/PVC, a StorageClass is not needed for dynamically provisioning Longhorn volume. However, the field `storageClassName` should be set in PVC/PV, to be used for PVC binding purpose. It's unnecessary for users to create the related StorageClass object.
 
 By default the StorageClass for Longhorn created PV/PVC is `longhorn-static`. Users can modify it in `Setting - General - Default Longhorn Static StorageClass Name` as they need.
 
@@ -162,4 +163,4 @@ Annotations:     longhorn.io/volume-scheduling-error: insufficient storage
 
 ...
 
-```
+```

content/docs/1.6.0/references/examples.md

@@ -17,7 +17,7 @@ For reference, this page provides examples of Kubernetes resources that use Long
 
 ### Block Volume
 
-
+```yaml
     apiVersion: v1
     kind: PersistentVolumeClaim
     metadata:
@@ -50,11 +50,11 @@ For reference, this page provides examples of Kubernetes resources that use Long
         - name: block-vol
           persistentVolumeClaim:
             claimName: longhorn-block-vol
-
-
+```
 
 ### CSI Persistent Volume
 
+```yaml
     apiVersion: v1
     kind: PersistentVolume
     metadata:
@@ -115,11 +115,11 @@ For reference, this page provides examples of Kubernetes resources that use Long
       - name: vol
         persistentVolumeClaim:
           claimName: longhorn-vol-pvc
-
+```
 
 ### Deployment
 
-
+```yaml
     apiVersion: v1
     kind: Service
     metadata:
@@ -186,11 +186,11 @@ For reference, this page provides examples of Kubernetes resources that use Long
           - name: mysql-volume
             persistentVolumeClaim:
               claimName: mysql-pvc
-
+```
 
 ### Pod with PersistentVolumeClaim
 
-
+```yaml
     apiVersion: v1
     kind: PersistentVolumeClaim
     metadata:
@@ -230,11 +230,13 @@ For reference, this page provides examples of Kubernetes resources that use Long
       - name: volv
         persistentVolumeClaim:
           claimName: longhorn-volv-pvc
+```
 
 ### Restore to File
 
 For more information about restoring to file, refer to [this section.](../../advanced-resources/data-recovery/recover-without-system)
 
+```yaml
     apiVersion: v1
     kind: Pod
     metadata:
@@ -283,11 +285,11 @@ For more information about restoring to file, refer to [this section.](../../adv
           hostPath:
             path: /tmp/restore
       restartPolicy: Never
-
+```
 
 ### Simple Pod
 
-
+```yaml
     apiVersion: v1
     kind: Pod
     metadata:
@@ -315,12 +317,11 @@ For more information about restoring to file, refer to [this section.](../../adv
         - name: volv
           persistentVolumeClaim:
             claimName: longhorn-simple-pvc
-
-
+```
 
 ### Simple PersistentVolumeClaim
 
-
+```yaml
     apiVersion: v1
     kind: PersistentVolumeClaim
     metadata:
@@ -332,12 +333,11 @@ For more information about restoring to file, refer to [this section.](../../adv
       resources:
         requests:
           storage: 1Gi
-
-
+```
 
 ### StatefulSet
 
-
+```yaml
     apiVersion: v1
     kind: Service
     metadata:
@@ -394,9 +394,11 @@ For more information about restoring to file, refer to [this section.](../../adv
           resources:
             requests:
               storage: 1Gi
+```
 
 ### StorageClass
 
+```yaml
     kind: StorageClass
     apiVersion: storage.k8s.io/v1
     metadata:
@@ -428,5 +430,7 @@ For more information about restoring to file, refer to [this section.](../../adv
       #   }
       #  ]'
 
+```
+
 Note that Longhorn supports automatic remount only for the workload pod that is managed by a controller (e.g. deployment, statefulset, daemonset, etc...).
 See [here](../../high-availability/recover-volume/) for details.

content/docs/1.6.1/nodes-and-volumes/volumes/create-volumes.md

@@ -50,7 +50,8 @@ When the Pod is deployed, the Kubernetes master will check the PersistentVolumeC
     #  ]'
     ```
 
-    In particular, starting with v1.4.0, the parameter `mkfsParams` can be used to specify filesystem format options for each StorageClass.
+    In particular, starting with v1.4.0, the parameter `mkfsParams` can be used to specify filesystem format options for each StorageClass.  
+    Parameters may be omitted from the StorageClass specification.  When the storage class is used to create a PV and a volume, parameters that are not specified will generally be set using a default value taken from the global settings.  See [here](../../../references/storage-class-parameters) for the list of storage class parameters, and [here](../../../references/settings) for the full list of global settings.
 
 2. Create a Pod that uses Longhorn volumes by running this command:
 
@@ -114,7 +115,7 @@ If the PVC names a StorageClass, Kubernetes will:
 
 ### Creating Longhorn Volumes with the Longhorn UI
 
-Since the Longhorn volume already exists while creating PV/PVC, a StorageClass is not needed for dynamically provisioning Longhorn volume. However, the field `storageClassName` should be set in PVC/PV, to be used for PVC bounding purpose. And it's unnecessary for users to create the related StorageClass object.
+Since the Longhorn volume already exists while creating PV/PVC, a StorageClass is not needed for dynamically provisioning Longhorn volume. However, the field `storageClassName` should be set in PVC/PV, to be used for PVC binding purpose. It's unnecessary for users to create the related StorageClass object.
 
 By default the StorageClass for Longhorn created PV/PVC is `longhorn-static`. Users can modify it in `Setting - General - Default Longhorn Static StorageClass Name` as they need.
 
@@ -162,4 +163,4 @@ Annotations:     longhorn.io/volume-scheduling-error: insufficient storage
 
 ...
 
-```
+```

content/docs/1.6.1/references/examples.md

@@ -18,6 +18,7 @@ For reference, this page provides examples of Kubernetes resources that use Long
 
 ### Block Volume
 
+```yaml
     apiVersion: v1
     kind: PersistentVolumeClaim
     metadata:
@@ -50,9 +51,11 @@ For reference, this page provides examples of Kubernetes resources that use Long
         - name: block-vol
           persistentVolumeClaim:
             claimName: longhorn-block-vol
+```
 
 ### CSI Persistent Volume
 
+```yaml
     apiVersion: v1
     kind: PersistentVolume
     metadata:
@@ -113,9 +116,11 @@ For reference, this page provides examples of Kubernetes resources that use Long
       - name: vol
         persistentVolumeClaim:
           claimName: longhorn-vol-pvc
+```
 
 ### Deployment
 
+```yaml
     apiVersion: v1
     kind: Service
     metadata:
@@ -182,9 +187,11 @@ For reference, this page provides examples of Kubernetes resources that use Long
           - name: mysql-volume
             persistentVolumeClaim:
               claimName: mysql-pvc
+```
 
 ### Pod with PersistentVolumeClaim
 
+```yaml
     apiVersion: v1
     kind: PersistentVolumeClaim
     metadata:
@@ -224,12 +231,14 @@ For reference, this page provides examples of Kubernetes resources that use Long
       - name: volv
         persistentVolumeClaim:
           claimName: longhorn-volv-pvc
+```
 
 ### Pod with Generic Ephemeral Volume
 
 For more information about generic ephemeral volumes, refer to the
 [Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes).
 
+```yaml
   apiVersion: v1
   kind: Pod
   metadata:
@@ -264,11 +273,13 @@ For more information about generic ephemeral volumes, refer to the
             resources:
               requests:
                 storage: 2Gi
+```
 
 ### Restore to File
 
 For more information about restoring to file, refer to [this section.](../../advanced-resources/data-recovery/recover-without-system)
 
+```yaml
     apiVersion: v1
     kind: Pod
     metadata:
@@ -317,9 +328,11 @@ For more information about restoring to file, refer to [this section.](../../adv
           hostPath:
             path: /tmp/restore
       restartPolicy: Never
+```
 
 ### Simple Pod
 
+```yaml
     apiVersion: v1
     kind: Pod
     metadata:
@@ -347,9 +360,11 @@ For more information about restoring to file, refer to [this section.](../../adv
         - name: volv
           persistentVolumeClaim:
             claimName: longhorn-simple-pvc
+```
 
 ### Simple PersistentVolumeClaim
 
+```yaml
     apiVersion: v1
     kind: PersistentVolumeClaim
     metadata:
@@ -361,9 +376,11 @@ For more information about restoring to file, refer to [this section.](../../adv
       resources:
         requests:
           storage: 1Gi
+```
 
 ### StatefulSet
 
+```yaml
     apiVersion: v1
     kind: Service
     metadata:
@@ -420,9 +437,11 @@ For more information about restoring to file, refer to [this section.](../../adv
           resources:
             requests:
               storage: 1Gi
+```
 
 ### StorageClass
 
+```yaml
     kind: StorageClass
     apiVersion: storage.k8s.io/v1
     metadata:
@@ -454,5 +473,7 @@ For more information about restoring to file, refer to [this section.](../../adv
       #   }
       #  ]'
 
+```
+
 Note that Longhorn supports automatic remount only for the workload pod that is managed by a controller (e.g. deployment, statefulset, daemonset, etc...).
 See [here](../../high-availability/recover-volume/) for details.

content/docs/1.6.2/nodes-and-volumes/volumes/create-volumes.md

@@ -50,7 +50,8 @@ When the Pod is deployed, the Kubernetes master will check the PersistentVolumeC
     #  ]'
     ```
 
-    In particular, starting with v1.4.0, the parameter `mkfsParams` can be used to specify filesystem format options for each StorageClass.
+    In particular, starting with v1.4.0, the parameter `mkfsParams` can be used to specify filesystem format options for each StorageClass.  
+    Parameters may be omitted from the StorageClass specification.  When the storage class is used to create a PV and a volume, parameters that are not specified will generally be set using a default value taken from the global settings.  See [here](../../../references/storage-class-parameters) for the list of storage class parameters, and [here](../../../references/settings) for the full list of global settings.
 
 2. Create a Pod that uses Longhorn volumes by running this command:
 
@@ -114,7 +115,7 @@ If the PVC names a StorageClass, Kubernetes will:
 
 ### Creating Longhorn Volumes with the Longhorn UI
 
-Since the Longhorn volume already exists while creating PV/PVC, a StorageClass is not needed for dynamically provisioning Longhorn volume. However, the field `storageClassName` should be set in PVC/PV, to be used for PVC bounding purpose. And it's unnecessary for users to create the related StorageClass object.
+Since the Longhorn volume already exists while creating PV/PVC, a StorageClass is not needed for dynamically provisioning Longhorn volume. However, the field `storageClassName` should be set in PVC/PV, to be used for PVC binding purpose. It's unnecessary for users to create the related StorageClass object.
 
 By default the StorageClass for Longhorn created PV/PVC is `longhorn-static`. Users can modify it in `Setting - General - Default Longhorn Static StorageClass Name` as they need.
 
@@ -162,4 +163,4 @@ Annotations:     longhorn.io/volume-scheduling-error: insufficient storage
 
 ...
 
-```
+```