kubectl top pod 只能获取master1节点pod信息，无法获取master2、node1节点pod信息

### What is version of KubeKey has the issue?

v3.0.2

### What is your os environment?

centos

### KubeKey config file

```yaml
apiVersion: kubekey.kubesphere.io/v1alpha2
kind: Cluster
metadata:
name: Rpa_K8s_Cluster
spec:
hosts:
- {name: master1, address: XXX, internalAddress: XXX, user: root, password: ""}
- {name: master2, address: XXX, internalAddress: XXX, user: root, password: ""}
- {name: node1, address: XXX, internalAddress: XXX, user: root, password: ""}
roleGroups:
etcd:
- master1
- master2
- node1
control-plane:
- master1
- master2
worker:
- master1
- master2
- node1
controlPlaneEndpoint:
## Internal loadbalancer for apiservers
# internalLoadbalancer: haproxy

domain: lb.kuberpa.local
address: ""
port: 6443
kubernetes:
version: 1.20.4
clusterName: cluster.local
autoRenewCerts: true
containerManager: docker
etcd:
type: kubekey
network:
plugin: flannel
kubePodsCIDR: 10.233.64.0/18
kubeServiceCIDR: 10.233.0.0/18
## multus support. https://github.com/k8snetworkplumbingwg/multus-cni
multusCNI:
enabled: false
registry:
privateRegistry: ""
namespaceOverride: ""
registryMirrors: []
insecureRegistries: []
addons: []
```

### A clear and concise description of what happend.

kubectl top pod 只能获取master1节点pod信息，无法获取master2、node1节点pod信息

### Relevant log output

_No response_

### Additional information

_No response_

No source file or test is identified in the issue. Reproduce the supplied KubeKey v3.0.2 cluster behavior by running kubectl top pod and comparing results across master1, master2, and node1, then trace the metrics-related cluster setup. Done means kubectl top reports pods from all listed nodes, with a regression test or documented verification.

Written by the indexing model from the issue text.