Prevent workflow conflicts with mutex synchronization, semaphores for limited parallelism, and TTL strategies for automatic cleanup of completed workflows.
Prevent workflow conflicts on shared resources using mutexes for exclusive access or semaphores to limit parallelism. Use this when multiple workflows risk corrupting outputs or competing for resources like build directories or ConfigMaps.
/plugin marketplace add adaptive-enforcement-lab/claude-skills/plugin install patterns@ael-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
When multiple workflows operate on shared resources, conflicts are inevitable. Two builds writing to the same output directory corrupt each other. Two deployments running simultaneously leave the system in an undefined state. Two cache rebuilds compete for the same ConfigMap.
Concurrency control prevents these conflicts. Argo Workflows provides several mechanisms: mutexes for exclusive access, semaphores for limited parallelism, and TTL strategies for cleanup.
Start with Mutex
When in doubt, start with a mutex. It's simpler to configure and debug. Only switch to semaphores when you need controlled parallelism.
| Pattern | Description |
|---|---|
| Mutex Synchronization | Exclusive access to shared resources |
| Semaphores | Limited concurrent access |
| TTL Strategy | Automatic cleanup of completed workflows |
| Pattern | Description |
|---|---|
| Mutex Synchronization | Exclusive access to shared resources |
| Semaphores | Limited concurrent access |
| TTL Strategy | Automatic cleanup of completed workflows |