Gloo Fed rejects wildcard for CRDs that are not RBAC

[willowmck]

Describe the bug When creating a federated resource, the wildcard '' annotation for clusters results in the following error: "Cluster is not registered"

To Reproduce Steps to reproduce the behavior: Apply a resource like the following:

apiVersion: fed.gateway.solo.io/v1
kind: FederatedVirtualService
metadata:
  name: http-127.0.0.1.nip.io
  namespace: gloo-system
spec:
  placement:
    clusters:
    - '*'
    namespaces:
    - gloo-system
  template:
    metadata:
      name: http-127.0.0.1.nip.io
    spec:
      virtualHost:
        domains:
        - 127.0.0.1.nip.io:*
        routes:
        - delegateAction:
            ref:
              name: http-127.0.0.1.nip.io-a
              namespace: tenant1
          matchers:
          - prefix: /a

Expected behavior Gloo should accept this wildcard as referring to all registered clusters.

Additional context Gloo Edge 1.8.13

[soloio-bot]

Zendesk ticket #598 has been linked to this issue.

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