[argocd] update argocd to v2.5.10

[yanggangtony]

Signed-off-by: yanggang gang.yang@daocloud.io

What type of PR is this?
/kind feature

What this PR does / why we need it:
This PR update argocd to version 2.5.10

[argocd] update argocd to v2.5.10

[k8s-ci-robot]

Hi @yanggangtony. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[floryut]

@yanggangtony Thank you; So many version of argocd gets release though 😅
/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, yanggangtony

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [floryut]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[yanggangtony]

@floryut
😅 hhha

[yanggangtony]

@floryut
in recent days , i found kubespray is a very quick response and rapid develop projects.
so your suggestion is update the software's version at a lower frequency?

☺️☺️☺️
maybe i will deduce the frequency to follow the latest versions..

[oomichi]

haha, I had the same feeling about argocd as @floryut :-)

/lgtm

[yanggangtony]

Actuall ,Argo CD uses the semver versioning and ensures that following rules:
like :

The patch release does not introduce any breaking changes. So if you are upgrading from v1.5.1 to v1.5.3 there should be no special instructions to follow.

So it will no influence with current version to upgrade.
Maybe next time , i will reduce the frequency.😄
thanks for yours reviews.
@oomichi @floryut

[floryut]

@yanggangtony no worries, honnestly it doesn't bother me at all, at least you're keeping it up to date.

If you want to bump the minor at a lower frequency that's fine but you can keep the current pace if you want to, that's anyway appreciated! Thank you