feat: Cluster discovery

[lukasmrtvy]

Briefly describe the feature

• Cluster Discovery via Kubernetes Secrets ( Kubeconfig )

What problem does this feature solve? Please link any relevant documentation or Issues

• Cluster Discovery can be useful for CAPI ( https://github.com/kubernetes-sigs/cluster-api ) managed clusters

(optional) What is your current workaround?

none

[akshay196]

@lukasmrtvy Thanks for creating issue. Can you please add more information such as use cases of cluster discovery, different user stories if any, why/when do we need this feature, benefits of this feature? Also I am wondering how cluster discovery can be helpful for CAPI managed clusters.

[akshay196]

@lukasmrtvy Hey, we would like to know more about your use cases and requirement. How organization, community would get benefited by having this feature?

[lukasmrtvy]

Hi,
In organizations where workload clusters are created/managed in the central managed cluster via Cluster-API, Rancher, Gardener ( each workload cluster has its admin kubeconfig generated there also in form of K8s secret ), etc, makes sense to run also Paralus as a central access manager, thus Paralus would benefit from discovering workload clusters via Kubernetes Secret ( Kubeconfig ) automatically.

This could be probably done with https://github.com/flant/shell-operator and API endpoint for adding workload clusters ( https://www.paralus.io/blog/kind-quickstart#importing-an-existing-cluster ).

Also with https://github.com/external-secrets/external-secrets where the kubeconfig could be pushed to the external secret store and pulled/synced in the Paralus cluster.