Argo Controller Config Quick Fix - Workflow Controller Setup

Argo Workflows controller configuration in workflow-controller-configmap controls cluster-wide behavior. Misconfigured settings cause workflow submission failures or performance issues. This guide covers the fix.

Quick Fix

Wrong

apiVersion: v1
kind: ConfigMap
metadata:
  name: workflow-controller-configmap
data:
  config: |
    executorImage: argoproj/argoexec:latest

Using latest tag for executor image causes instability from uncontrolled updates. Missing artifact Repository and default metadata settings cause primitive workflow behavior.

Right

apiVersion: v1
kind: ConfigMap
metadata:
  name: workflow-controller-configmap
  namespace: argo
data:
  config: |
    executorImage: argoproj/argoexec:v3.5.0
    artifactRepository:
      s3:
        bucket: my-argo-artifacts
        keyPrefix: artifacts/
        endpoint: s3.amazonaws.com
    workflowDefaults:
      metadata:
        annotations:
          workflows.argoproj.io/description: "Default workflow"

# Expected output after applying the fix
# Controller uses pinned executor version
# Artifact repository configured for S3
# New workflows inherit default metadata
# System performance stabilized

Prevention

• Pin executor image version to a specific release
• Configure artifact Repository for production workloads
• Set workflowDefaults for metadata inheritance
• Configure RBAC for the controller service account
• Validate config changes in staging before production

DodaTech Tools

Doda Browser's controller config editor provides schema validation for ConfigMap changes. DodaZIP archives configuration versions for rollback. Durga Antivirus Pro validates controller settings against security baselines.

FAQ