Anton Gilgur

See #13415. Per https://github.com/argoproj/argo-workflows/issues/13415#issuecomment-2258599237, the error isn't from the code of this PR per se, it's actually with the order in which PRs got cherry-picked, which `git` did not detect...

> * Allow the user to specify in the `workflow-controller-configmap.yaml` whether they want ISO timestamps or the existing format That would make it controller-wide as opposed to user preference. I...

> There isn't good standardization across the codebase. Mm there are plenty of util functions, although yes there's many cases they're not always used in all places (e.g. #12970, #12973...

> I think is caused here > Code permalink: > https://github.com/argoproj/argo-workflows/blob/v3.4.3/ui/src/app/workflows/components/workflow-logs-viewer/workflow-logs-viewer.tsx#L87 Yea that sounds like an accurate analysis, this probably should use `getTemplateNameFromNode` instead of `node.templateName` to properly handle `templateRef`s

We might want to add an `agent:` block to the Workflow spec to handle this and other things like #7972

Superseded by ~#13016~. **EDIT**: Split to #13294

#10233 is closely related. That being said, while containers can have separate `securityContext`s, they all share the same SA -- SAs are Pod-level. Currently the Emissary Executor init and wait...

> Currently the Emissary Executor init and wait containers are part of the same Pod as the main container of the workflow step/task, so it is not possible to split...

Discussed in [today's Contributor Meeting](https://docs.google.com/document/d/1tznN5LB-KrNkC6dmeIzpKfuyvZWgCJpRuS-E84zseC8/edit#heading=h.shpizyln62nu) and the consensus was that we would add a note to the 3.4 upgrading guide about this unintentional bug / breaking change to SSO RBAC...

> I can't seem to get namespace delegation Yes, namespace delegation specifically still works correctly. But if you turn it off and have a managed namespace in 3.4 or 3.5,...