Problems with full CRD

[static-moonlight]

When upgrading from Argo 3.7 to 4.0 my deployment now fails. After investigating, I found that this is due to the change in #15003. The combined size of my Argo deployment is now 10.6 MB instead of the previous 140 KB. So far I was using kubectl apply to deploy Argo to my cluster (using the cluster-install manifest). As far as I know, this command comes with a 3 MB limit. The Argo 4.0 deployment now easily exceeds that limit. kubectl create could be an alternative to deal with the new combined size of the Argo 4.0 deployment, but it will fail when an object/deployment already exists.

So the question is: How did you intent to get Argo deployed and upgraded with the full CRD active?

[static-moonlight]

now opened as issue #16050