Jonas Reineke

The problem still exists in ArgoCD: v2.9.2

I think this problem still exists. Even with the latest ArgoCD (`v2.10.8`) I can't see the correct shards assigned to my clusters: ``` argocd admin cluster stats SERVER SHARD CONNECTION...

@viceice are there any updates to the version splitting?

Sorry for the late reply, with the latest version 2.12.1 I don't see the problem anymore. I think this problem is fixed.

> On a private App with 3 sources, the diff is even stranger: as if it completely removed the resources for the first source (it's a helm release with value.yaml...

Unfortunately, the problem still exists with the latest ArgoCD v2.11.1. I also tested it with the guestbook single source application above and found the following: It seems that the `--revisions`...

I just updated to the newest version which was released today `v2.11.3` the problem is fixed for me. From the changelog I think https://github.com/argoproj/argo-cd/pull/18395 has fixed the problem.

This is also happening to us: Thanos: v0.32.5 (deployed through bitnami helm chart) Prometheus: v2.45.1 The problem only occurs on queries which are a little bit older and only rely...

This is our config: ``` - store - '--log.level=info' - '--log.format=logfmt' - '--grpc-address=0.0.0.0:10901' - '--http-address=0.0.0.0:10902' - '--data-dir=/data' - '--objstore.config-file=/conf/objstore.yml' - | --tracing.config=type: OTLP config: client_type: grpc service_name: "thanos-storegateway" endpoint: 127.0.0.1:4317...

We are in the process of upgrading our clusters to the latest version and have encountered this problem. For each cluster we have about 50 ingress resources that have grpc_read_timeout...