Open htech7x opened 2 weeks ago
Internal slack thread: https://solo-io-corp.slack.com/archives/CEDCS8TAP/p1724785852085279 Potentially relevant PR: https://github.com/solo-io/gloo/pull/9310#discussion_r1562623909
Zendesk ticket #4392 has been linked to this issue.
This is another instance of https://github.com/solo-io/gloo/issues/6406. I think in part we got bit by this because we do not recommend using persistProxySpec=true
and migrated all of our tests to use the recommended setting. We need a single test that verifies that when proxies are persisted, you can upgrade without error (and Gloo continues to process resources)
Zendesk ticket #4499 has been linked to this issue.
I documented reproduction steps here as well: https://github.com/solo-io/gloo-gateway-shared-resources/tree/main/issues/gloo/9968
Work around is to delete the proxy resource and then gloo will self heal
Gloo Edge Product
Enterprise
Gloo Edge Version
1.17.1
Kubernetes Version
1.28.5
Describe the bug
After upgrading Gloo EE from 1.16.9 to 1.17.1 when "gloo.gateway.persistProxySpec=true": Newly created "virtual services" no longer have a "status". "Proxy" object stops updating its configuration.
Expected Behavior
"Proxy" updates its config when a new VS is created
Steps to reproduce the bug
Check status of VS(newly created VS has no status):
Check "proxy" config(there is nothing about the recently created VS "web"):