[Bug] kind Settings of Gloo Edge got stuck in new ArgoCD version

[vietwow]

Gloo Edge Product

Open Source

Gloo Edge Version

v1.180 and v1.19.0-beta9

Kubernetes Version

1.31

Describe the bug

Hi,

I'm using gloo edge, deploy using helm chart "gloo" , version "1.19.0-beta9", from helm repo https://storage.googleapis.com/solo-public-helm. This works perfect in argocd chart version "7.7.22", but if I deploy new versions of argocd chart such as "7.8.2" or latest "7.8.7", the we got stuck with "kind: Settings" of Gloo

I have give a very detailed info (including screenshot and logs) in ticket argoproj/argo-cd#22102

This problem can be reproducible.

Best Regards,
VietNC

Expected Behavior

"Settings" object is not in "Processing"

Steps to reproduce the bug

Just deploy Gloo v1.19.0-beta9 (or v1.18.0 same problem) and ArgoCD with chart version "7.8.7"

Additional Environment Detail

No response

Additional Context

No response

[vietwow]

FYI I have just tested with the latest Gloo v1.19.0-beta12 and still got the same issue

[jurgenweber]

I am experiencing the same on the lastest ArgoCD using Gloo 1.8 chart. Please follow the issue link for further details. The short of it is, the Settings resources do not return a status.

argoproj/argo-cd#22102 (comment)

[jurgenweber]

Ok, so I went into my ArgoCD config-cm and went

             resource.customizations.health.gloo.solo.io_Settings: |
                hs = {}
                hs.status = "Healthy"
                hs.message = "we are good"
                return hs

This at least gets me out of trouble in the short term but isn't great beyond that.