Anton Gilgur

Huh so this did partially [fail](https://github.com/argoproj/argo-workflows/actions/runs/9409633233/job/25920972244) on release on `main`: ``` Run echo $(jq -c '. + { "experimental": "enabled" }' ${DOCKER_CONFIG}/config.json) > ${DOCKER_CONFIG}/config.json jq: error: Could not open file...

> The default is `~/.docker/config.json` so this may be easily replaceable Added this as a default in #13155

I don't think Argo ever sets its own `tolerations`, only the ones that you specify. There's only [one place in the code](https://github.com/argoproj/argo-workflows/blob/4d8f97290d10305c4ba96e442286b64223515af7/workflow/controller/workflowpod.go#L783) that they're added too. Why do you think...

> perhaps docs should mention overwriting this Tolerations are only mentioned in the Fields Reference, where they directly inherit from k8s, so have no Argo specific behavior nor Argo specific...

Likely a duplicate of #11715, which should be resolved in 3.5.7, which I was hoping to release this weekend

[v3.5.7](https://github.com/argoproj/argo-workflows/releases/tag/v3.5.7) is released, which contains a backport of #12736 / #13021 that fixed #11715. Please try it out and let us know if it's fixed now.