-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set wf.spec.affinity.nodeAffinity, but agent pod has no nodeAffinity #9704
Comments
Currently, the agent pod spec is hard-coded and you won't be able to customize it. |
Any plans for customizing the agent pod? |
We could consider treating it similarly to other pods and allowing customization. Do you want to look into that? |
ok |
argoproj#9704 Signed-off-by: yangxue.chen <[email protected]>
argoproj#9704 Signed-off-by: yangxue.chen <[email protected]>
#9704 (#9771) Signed-off-by: yangxue.chen <[email protected]> Signed-off-by: yangxue.chen <[email protected]> Co-authored-by: yangxue.chen <[email protected]>
argoproj#9704 (argoproj#9771) Signed-off-by: yangxue.chen <[email protected]> Signed-off-by: yangxue.chen <[email protected]> Co-authored-by: yangxue.chen <[email protected]> Signed-off-by: juchao <[email protected]>
Pre-requisites
:latest
What happened/what you expected to happen?
Set wf.spec.affinity.nodeAffinity, but agent pod has no nodeAffinity. I expect to agent pod has the same affinity
Version
v3.3.9
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}
Logs from in your workflow's wait container
kubectl logs -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded
The text was updated successfully, but these errors were encountered: