docs: Pod Security Context: Volumes aren't required in >= v3.3 and ru…

…nAsNonRoot (argoproj#14072) Signed-off-by: Paul Watts <[email protected]> Co-authored-by: Mason Malone <[email protected]>
AKJUS · Jan 27, 2025 · 5ed3bf4 · 5ed3bf4
1 parent c92ac36
commit 5ed3bf4
Showing 1 changed file with 0 additions and 3 deletions.
diff --git a/docs/workflow-pod-security-context.md b/docs/workflow-pod-security-context.md
@@ -23,6 +23,3 @@ You can configure this globally using [workflow defaults](default-workflow-specs
 
 !!! Warning "It is easy to make a workflow need root unintentionally"
     You may find that user's workflows have been written to require root with seemingly innocuous code. E.g. `mkdir /my-dir` would require root.
-
-!!! Note "You must use volumes for output artifacts"
-    If you use `runAsNonRoot` - you cannot have output artifacts on base layer (e.g. `/tmp`). You must use a volume (e.g. [empty dir](empty-dir.md)).