`glooctl check` tries to check proxies in all watch namespaces

[jenshu]

Gloo Edge Product

Open Source

Gloo Edge Version

1.17

Kubernetes Version

1.29

Describe the bug

When running glooctl check, we currently iterate through each of the watch namespaces and list the proxies in each namespace. However, proxies are only stored in the write namespace, so it's sufficient to just check just one namespace instead of doing all that extra work (we try to open a port-fwd for each namespace we check, and in the case where watch namespaces are not explicitly defined, it defaults to all namespaces on the cluster).

To fix this we can use similar logic as we are in glooctl get proxy to get the proxy namespace

Expected Behavior

We should only check proxies in the proxy write namespace

Steps to reproduce the bug

Install GG and run glooctl check

Additional Environment Detail

No response

Additional Context

No response

┆Issue is synchronized with this Asana task by Unito