The following changes are made in v1alpha2 design:
Remove secretSpecs field, the secret configs can be handled by user directly by mounting to workflow agent or workload resources through the API.
Add workflowAgent field, that lets user explicitly configure the workflow agent specifications. This can be backed by a default config that is fed into the operator separately, so that if the field is omitted by the user the default values will be taken.
Turn volume configs into 2 fields: managedVolumes and volumes, where managedVolumes are the special volumes shared between workflow agents and user's workload resources and directory structure managed by the workflow, and volumes are the general volumes that can be mounted by user to workflow agents and workload resources.
Replace the "pre-job", "main-job", "post-job" concepts with DAG styled "tasks". The "tasks" look similar as Argo's DAG tasks, but come with a set of customized behaviors, such like autoWatch, etc. as well as special manifest references for arbitrary resources.
The following changes are made in v1alpha2 design:
secretSpecs
field, the secret configs can be handled by user directly by mounting to workflow agent or workload resources through the API.workflowAgent
field, that lets user explicitly configure the workflow agent specifications. This can be backed by a default config that is fed into the operator separately, so that if the field is omitted by the user the default values will be taken.managedVolumes
andvolumes
, wheremanagedVolumes
are the special volumes shared between workflow agents and user's workload resources and directory structure managed by the workflow, andvolumes
are the general volumes that can be mounted by user to workflow agents and workload resources.autoWatch
, etc. as well as special manifest references for arbitrary resources.reports
field.Example yaml manifest: