carolkao

Hi @sarabala1979, I've read your comment in @9166, would you please help to take a look on this issue? Thank you.

Hi @terrytangyuan , thanks for your reply. I believe the connection between our cluster and OSS address is stable since the error rarely happens. (But feel inconvenience for us) Our...

Hi @terrytangyuan and @isubasinghe, I'd like to expedite the progress of this PR. It's crucial for supporting proxy settings in OSS client for us. Currently, we rely on Argo v3.4.8...

Hi @jingkkkkai , please help to solve the error for this PR.

Hi @isubasinghe, All checks have passed now, can you help to move this PR forward?

Hi @terrytangyuan , Do you think Argo's development team could help cherry-pick this fix into the 3.4 branch? We're struggling with the build environment, and I believe it would be...

> @carolkao See [#11851 (comment)](https://github.com/argoproj/argo-workflows/issues/11851#issuecomment-2339509093) Cool, thank you @terrytangyuan . Looking forward to the next 3.4 release.

We also encounter this issue in our production environment with v3.6.2. Lots of workflows encounter `unable to resolve outputs from scope: xxx` error, and after some investigation, we found it's...

Hi @shuangkun Thank you for acknowledging that this issue is important. I noticed in the screenshot you shared that there were around 20,000 workflows running simultaneously. May I ask what...

Hi @shuangkun Thanks for sharing this information. In our environment, we’ve observed that the bottleneck appears to come from the Kubernetes API server. When the number of concurrent workflows reaches...