Design a cluster registry

[joekelley]

We need to develop our cluster registration story. Today in skv2, a registered cluster is represented by a secret of type solo.io/kubeconfig, and a cluster name is the metadata.name on that secret. This simplistic approach introduces issues such as cluster name duplication across namespaces. Let's review KubeFed, Service Mesh Hub, Fleet, and other multicluster projects and determine how we want to represent clusters at the solo-kit level of our products.

[jenshu]

we should store namespace.name but make it opt-in - going in a different direction, won't modify how the cluster name is stored, for now