Skip to content

Latest commit

 

History

History
29 lines (20 loc) · 1.35 KB

workflow-restrictions.md

File metadata and controls

29 lines (20 loc) · 1.35 KB
Raw

Workflow Restrictions

v2.9 and after

Introduction

As the administrator of the controller, you may want to limit which types of Workflows your users can run. Setting workflow restrictions allows you to ensure that Workflows comply with certain requirements.

Available Restrictions

  • templateReferencing: 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.
  • templateReferencing: Secure: Only Workflows using workflowTemplateRef will be processed and the controller will enforce that the workflow template 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.

Setting Workflow Restrictions

Workflow Restrictions can be specified by adding them under the workflowRestrictions key in the workflow-controller-configmap.

For example, to specify that Workflows may only run with workflowTemplateRef

# This file describes the config settings available in the workflow controller configmap
apiVersion: v1
kind: ConfigMap
metadata:
  name: workflow-controller-configmap
data:
  workflowRestrictions: |
    templateReferencing: Secure