Argo Workflows v2.10

With 24 bug fixes and7 new features from 20 contributors, this is one of the smallest releases in a while.

Releases

Validating Workflows

Users have reported it is hard to create syntactically valid workflows, so we made some enhancements.

Editors like VS Code and IntelliJ allow you to import resource specifications and validate your YAML manifests directly in your IDE.

Learn how to validate workflows in your IDE

If you want to validate workflows using the CLI, you can use this script.

We’ve enhanced the editor that is bundled with Argo Workflow user interface to add syntax highlighting and auto-completion:

Workflow Semaphore Support

Many workflows need exclusive access to some kind or shared resource. For example, a disk or specific file. Workflows semaphores allows a workflow to lock the resource:

# This example demonstrates the use of a Synchronization lock on workflow execution. Synchronization lock limits 
# the number of concurrent workflow execution in the namespace which has same Synchronization lock. Synchronization
# limit value can be configured in configmap.
# Eg.:
# apiVersion: v1
# kind: ConfigMap
# metadata:
#   name: my-config
# data:
#   workflow: "3"
#---
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: synchronization-wf-level-
spec:
  entrypoint: whalesay
  synchronization:
    semaphore:
      configMapKeyRef:
        name: my-config
        key: workflow
  templates:
  - name: whalesay
    container:
      image: docker/whalesay:latest
      command: [cowsay]
      args: ["hello world"]

User Interface Enhancements

You can now select workflows from the user interface and perform batch operations on them.

Easier Automation

To make it easier to develop applications that run workflows, we bundled the Swagger UI into to the user interface so you can experiment making API calls against a real system.

We’ll soon be producing training materials for automation.

Much More Meta-Data

To make it easier to know why a workflow was trigger we now label workflows automatically:

• The workflow template that triggered them.
• The user that created them.

metadata:
  name: sparkly-whale-s8nph
  namespace: argo
  labels:
    workflows.argoproj.io/completed: 'true'
    workflows.argoproj.io/creator: admin
    workflows.argoproj.io/phase: Succeeded
    workflows.argoproj.io/workflow-template: sparkly-whale