Setting executor (wait) container resources in the WorkflowTemplate is counterintuitive/undocumented #12729
-
I want to configure the default I have tried these approaches, after reading the docs: apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
spec:
podSpecPatch: |-
{"containers": [{"name": "wait", "resources": {"requests": {"cpu": "51m", "memory": "128Mi"}, "limits": {"cpu": "51m", "memory": "128Mi"}}}]}
---
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
spec:
podSpecPatch: |-
containers:
- name: wait
resources:
requests:
cpu: "51m"
memory: "128Mi"
limits:
cpu: "51m"
memory: "128Mi" but the apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
spec:
templates:
- name: image
podSpecPatch: |
initContainers:
- name: init
resources:
requests:
cpu: "53m"
memory: "128Mi"
limits:
cpu: "54m"
memory: "128Mi"
containers:
- name: wait
resources:
requests:
cpu: "55m"
memory: "129Mi"
limits:
cpu: "56m"
memory: "129Mi"
container:
image: moby/buildkit:v0.11.6-rootless
# the rest of the template even though according to the documentation, the correct place is |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
argo-workflows/workflow/controller/workflowpod.go Lines 362 to 383 in 7286d49 Unfortunately, workflow-level podSpecPatch in WorkflowTemplate can not take effect.
|
Beta Was this translation helpful? Give feedback.
-
It seems like a bug when using |
Beta Was this translation helpful? Give feedback.
It will be fixed with this PR: #12476