Aikawa

Hi @dlactin , It's reflected in https://github.com/argoproj/argo-helm/pull/2809 , so let us close. again thank you for your PR.

Hi @Paritosh-Anand , thank you for your investigation. Since we follow [upstream's manifest](https://github.com/argoproj/argo-workflows/tree/main/manifests), can you please make PR to upstream at first? When upstream is fixed and new version tag...

Hi @shraddhabang , >We will add this to our next minor release v2.9.0 Could you please share us when the v2.9.0 would release? We are looking forward to this feature.

Hi, @johngmyers @M00nF1sh @shraddhabang >We will add this to our next minor release v2.9.0. Does anyone know the release schedule for v2.9.0 ?

It's related https://github.com/argoproj/argo-cd/issues/6880 ?

Hi @atalakey4work , since it's about Argo CD itself, you can open issue in [upstream](https://github.com/argoproj/argo-cd).

Hi @bdrewery , we follow [upstream's manifest](https://github.com/argoproj/argo-cd/tree/master/manifests) and `ARGOCD_APPLICATION_CONTROLLER_COMMIT_SERVER` is not configured for now. Please add the env in upstream's manifest, so we will follow. 🙏 https://github.com/search?q=repo%3Aargoproj%2Fargo-cd%20ARGOCD_APPLICATION_CONTROLLER_COMMIT_SERVER&type=code

When upstream releases the diff as specific version, we will update manifest as following upstream. So please wait for it.

Hi @wangxin-trec , argo-helm is for supporting to install Argo CD but we don't take care of Argo CD itself. This issue seems to be related Argo CD's behavior, not...

Hi @sribiere-jellysmack , since argo-helm follows upstream and your PR ( https://github.com/argoproj-labs/argocd-image-updater/pull/831 ) is not merged yet in upstream, we put ` awaiting-upstream` label and waiting for it. When the...