Standardise CPU and Memory Resources for Argo Workflows#1322
Merged
Conversation
davehadley
requested changes
May 19, 2026
fix: bump workflows chart version fix: update workflow controller cpu and memory resources fix: update workflow controller cpu and memory resources
hazdl
force-pushed
the
haz/cpu-memory-limits
branch
from
c4bc8d0 to
37ddd8f
Compare
davehadley
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR standardises CPU and memory requests/limits across the Argo Workflows Helm chart to ensure consistent resource allocation for controller, server, and workflow execution pods.
-Updated controller resources to: requests: 500m CPU / 2Gi memory
limits: 1 CPU / 4Gi memory
-Updated server resources to: requests: 1 CPU / 1Gi memory
limits: 2 CPU / 2Gi memory
-Added/updated workflowDefaults.spec.podSpecPatch to enforce workflow pod resources:
requests: 500m CPU / 2Gi memory
limits: 1 CPU / 4Gi memory
-Applies to: new workflow executions only
No changes required to existing workflows
Verification:
Verified via helm template rendering that workflowDefaults.spec.podSpecPatch applies CPU and memory requests/limits to the workflow main container. Confirmed in rendered output:
workflowDefaults.spec.podSpecPatch → containers.main.resources
Confirmed using Helm-rendered manifests and grep validation.
grep -n "podSpecPatch" rendered.yaml
grep -n "2Gi" rendered.yaml
grep -n "500m" rendered.yaml