docs: Update workflow-controller-configmap workflowRestrictions examp…

…le doc (#5109)

Signed-off-by: krrrr38 <k.kaizu38@gmail.com>

USERS.md

@@ -47,6 +47,7 @@ Currently, the following organizations are **officially** using Argo Workflows:
 1. [EBSCO Information Services](https://www.ebsco.com/)
 1. [Equinor](https://www.equinor.com/)
 1. [Fairwinds](https://fairwinds.com/)
+1. [FOLIO](http://corp.folio-sec.com/)
 1. [Fynd Trak](https://trak.fynd.com/)
 1. [Gardener](https://gardener.cloud/)
 1. [GitHub](https://github.com/)

docs/workflow-controller-configmap.yaml

@@ -260,12 +260,12 @@ data:
       # RBAC Config. >= v2.12
       rbac:
         enabled: false
-    # workflowRequirements restricts the Workflows that the controller will process.
+    # workflowRestrictions restricts the Workflows that the controller will process.
     # Current options:
-    #   referenceOnly: Only Workflows using "workflowTemplateRef" will be processed. This allows the administrator of the controller
+    #   Strict: Only Workflows using "workflowTemplateRef" will be processed. This allows the administrator of the controller
     #     to set a "library" of templates that may be run by its operator, limiting arbitrary Workflow execution.
-    #   strictReferenceOnly: Only Workflows using "workflowTemplateRef" will be processed and the controller will enforce
+    #   Secure: Only Workflows using "workflowTemplateRef" will be processed and the controller will enforce
     #     that the WorkflowTemplate that is referenced hasn't changed between operations. If you want to make sure the operator of the
     #     Workflow cannot run an arbitrary Workflow, use this option.
-    workflowRequirements:
-      referenceOnly: true
+    workflowRestrictions:
+      templateReferencing: Strict