Glooctl delete should support route tables

[kevin-shelaga]

Is your feature request related to a problem? Please describe.

glooctl delete --help                                                        
Delete a Gloo resource

Usage:
  glooctl delete [flags]
  glooctl delete [command]

Aliases:
  delete, d

Available Commands:
  proxy          delete a proxy
  upstream       delete an upstream
  upstreamgroup  delete an upstream group
  virtualservice delete a virtualservice

Flags:
  -h, --help               help for delete
      --name string        name of the resource to read or write
  -n, --namespace string   namespace for reading or writing resources (default "gloo-system")

Global Flags:
  -c, --config string              set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml")
      --consul-address string      address of the Consul server. Use with --use-consul (default "127.0.0.1:8500")
      --consul-datacenter string   Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul
      --consul-root-key string     key prefix for for Consul key-value storage. (default "gloo")
      --consul-scheme string       URI scheme for the Consul server. Use with --use-consul (default "http")
      --consul-token string        Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul
  -i, --interactive                use interactive mode
      --kubeconfig string          kubeconfig to use, if not standard one
      --use-consul                 use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies)

Use "glooctl delete [command] --help" for more information about a command.

Describe the solution you'd like glooctl delete should support deleting route tables

Describe alternatives you've considered just use kubectl

Additional context glooctl v1.8.6

[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.