Use client-go to access multi-cluster pods , but throws some errors

[wuyingjun-lucky]

[wuyingjun-lucky]

[wuyingjun-lucky]

`var err error
var config *rest.Config
var kubeconfig *string

if home := homedir.HomeDir(); home != "" {
	kubeconfig = flag.String("kubeconfig", filepath.Join(home, ".kube", "config"), "相对路径")
} else {
	kubeconfig = flag.String("kubeconfig", "", "相对路径")
}

if config, err = rest.InClusterConfig(); err!= nil {
	if config, err = clientcmd.BuildConfigFromFlags("", *kubeconfig); err != nil {
		err.Error()
	}
}

clientSet, err := kubernetes.NewForConfig(config)
if err != nil {
	panic(err.Error())
}

factory := informers.NewSharedInformerFactory(clientSet, 0)
deployPods := factory.Core().V1().Pods()
deployLister := deployPods.Lister()

stopChan := make(chan struct{})
defer close(stopChan)

factory.Start(stopChan)
factory.WaitForCacheSync(stopChan)


pods, err := deployLister.Pods("test0608").List(labels.Everything())
if err != nil {
	panic(err.Error())
}
for idx, pod := range pods {
	fmt.Printf("%d ---- %s\n ", idx +1, pod.Name)
	fmt.Printf("%d ---- %v\n ", idx +1, pod.Status.ContainerStatuses)
	fmt.Printf("%d ---- %v\n ", idx +1, pod.Status.String())
}

<- stopChan`

[wuyingjun-lucky]

@Iceber When I change to cluster30 kubeconfig It works fine .
Can you help me ?

[Iceber]

@wuyingjun-lucky Do you want to use clusterpedia to watch multiple cluster resources?

clusterpedia currently only supports retrieval of resources, i.e. get and list operations, not watch operations

[wuyingjun-lucky]

We have many applications ，It seems there will be watch operations exist. I will check these days.

[Iceber]

If you need to watch a single cluster, I think it is better to connect to the cluster directly. Of course, in the future clusterpedia will support more operations for a single cluster, such as watch, exec, logs, but this will also bring additional proxy loss.

If you need to watch multiple cluster resources, this is a very complex feature, because it involves the apiserver to be aware of resource changes in the case of multiple replicas, we can discuss the implementation further.

[wuyingjun-lucky]

Yeah
Our final goal is to ignore member clusters.