Merge pull request #38157 from codyhoag/winc-pv-note

OSDOCS-2711 PV note for Windows

Author: codyhoag

modules/nodes-containers-projected-volumes-about.adoc

@@ -12,6 +12,13 @@ so that I can synthesize a single directory with various sources of information;
 * populate a single volume with the keys from multiple secrets, config maps, and with downward API information,
 explicitly specifying paths for each item, so that I can have full control over the contents of that volume.
 
+[IMPORTANT]
+====
+When the `RunAsUser` permission is set in the security context of a Linux-based pod, the projected files have the correct permissions set, including container user ownership. However, when the Windows equivalent `RunAsUsername` permission is set in a Windows pod, the kubelet is unable to correctly set ownership on the files in the projected volume.
+
+Therefore, the `RunAsUsername` permission set in the security context of a Windows pod is not honored for Windows projected volumes running in {product-title}.
+====
+
 The following general scenarios show how you can use projected volumes.
 
 *Config map, secrets, Downward API.*::
@@ -94,7 +101,6 @@ spec:
 If there are multiple containers in the pod, each container needs a `volumeMounts` section, but only one `volumes` section is needed.
 ====
 
-
 .Pod with multiple secrets with a non-default permission mode set
 
 [source,yaml]