glooctl check isn't looking at route tables

[rickducott]

It looks like glooctl check doesn't look at route tables, just detects problems from warnings on the proxy / virtual service:

➜ glooctl check
Checking deployments... OK
Checking pods... OK
Checking upstreams... OK
Checking upstream groups... OK
Checking auth configs... OK
Checking secrets... OK
Checking virtual services... Found virtual service with warnings: gloo-system app
Reason: warning:
  Route Warning: InvalidDestinationWarning. Reason: *v1.Upstream {echo-typo gloo-system} not found
Route Warning: InvalidDestinationWarning. Reason: *v1.Upstream {echo-typo gloo-system} not found
Problems detected!

In this case, I had referenced an invalid upstream on the route table CRD. I had expected the route table to be considered invalid, and noticed the CLI didn't say it checked route tables at all. This may be by design, but figured it was worth filing because it looks like the CLI is missing a check.

[rickducott]

Marking as a bug in case we are missing the check.

[github-actions[bot]]

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.