Describe the enhancement:
#26056 introduced 3 methods to set orchestrator.cluster.name & orchestrator.cluster.url

1. kube_config file
2. kubeadm-config configmap
3. GKE Metadata

I would like to see a separate configmap for deployments that aren't managed by kubeadm or GKE. While one can create a simple kubeadm-config configmap, this may cause other services that key off of the existence of this configmap to not work as expected.

Describe a specific use case for the enhancement or feature:
I have an EKS Cluster with Managed Node Groups and utilize Fleet containers in Kubernetes for monitoring. I was able to get the cluster name to populate by creating the kubeadm-config config map, however when I went to deploy Calico it saw this configmap and it was missing required information, causing Calico to not deploy successfully.

This is the configmap I deployed:

apiVersion: v1
kind: ConfigMap
metadata:
  name: kubeadm-config
  namespace: kube-system
data:
  ClusterConfiguration: |
    clusterName: cluster-1
    controlPlaneEndpoint: https://abcd1234.gr7.us-west-2.eks.amazonaws.com