Upgrade from v2.12.x to v4.0.1 version

[nitinmalik00]

Hi,

We are currently running Argo workflow v2.12.x and planning to upgrade to latest v4.0.1.

Current instance has a few custom patches applied, that we need to account for:

1. Recursive zip handling; change in workflow/executor/pns/pns.go for fetching/uploads file contents.
2. S3 ACL Headers: change in s3/s3.go in PutFile function to set ACL headers in the minio client.
3. minio Client / Signer: We modified the minio package to force SignatureV2 instead of V4 in api.go.

---

Seeking help with the following:

1. Is there specific documentation covering such a major version jump?
2. Any major breaking changes we should look out for between v2.12.x and v4.0?
3. Does anyone know if these features (specifically the ACL headers or signer overrides) have been integrated into the core project in recent versions?

Also, would you recommend an incremental upgrade path (e.g., moving to an intermediate v3.x version first) or is a direct jump to v4.0.1 feasible?

[nitinmalik00]

@terrytangyuan @alexec your guidance is much appreciated.

[nitinmalik00]

@jswxstw @tczhao Any suggestions ? Guidance is much appreciated.

[jswxstw]

Sorry, v2.12 is too old for me. I don't have experience upgrading from that version. I only have experience with the v3.4 → v3.5 → v3.6 upgrade path.
I suggest you look up the upgrade notes for each starting version -- for example, https://github.com/argoproj/argo-workflows/blob/v3.2.0-rc1/docs/upgrading.md.