You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can submit a workflow using a WorkflowTemplate and I can ensure my workflow has the correct annotations / labels using spec.workflowMetadata. Upon submitting, the Workflow resource is initially created WITHOUT my required metadata. The controller then updates my workflow's metadata to include what was specified in my template in workflowMetadata.
I propose using the SubmitOpts, or some new configuration to set any static workflow metadata at creation time.
Optionally, it might also be a good idea to show in the UI (SubmitWorkflowPanel), what labels are set in the spec.workflowMetadata field.
Use Cases
We are currently using gatekeeper to enforce labels for all workflows to get more precise metrics. This uses an admission webhook to stop users from creating workflows which don't have required labels. As the required labels are NOT PRESENT at creation time, we cannot enforce any labels.
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
I can submit a workflow using a WorkflowTemplate and I can ensure my workflow has the correct annotations / labels using
spec.workflowMetadata
. Upon submitting, the Workflow resource is initially created WITHOUT my required metadata. The controller then updates my workflow's metadata to include what was specified in my template inworkflowMetadata
.I propose using the
SubmitOpts
, or some new configuration to set any static workflow metadata at creation time.Optionally, it might also be a good idea to show in the UI (SubmitWorkflowPanel), what labels are set in the
spec.workflowMetadata
field.Use Cases
We are currently using gatekeeper to enforce labels for all workflows to get more precise metrics. This uses an admission webhook to stop users from creating workflows which don't have required labels. As the required labels are NOT PRESENT at creation time, we cannot enforce any labels.
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: