bug: Error: failed to list GroupVersion cluster

[milanahrae]

Describe the bug

Steps To Reproduce

Create and register two workload execution cluster(s) on Kubestellar Getting Started documentation.

Expected Behavior

Execute the following commands to create two kind clusters, named cluster1 and cluster2, and register them with the OCM hub. These clusters will serve as workload clusters. If you have previously executed these commands, you might already have contexts named cluster1 and cluster2. If so, you can remove these contexts using the commands kubectl config delete-context cluster1 and kubectl config delete-context cluster2.

: set flags to "" if you have installed KubeStellar on an OpenShift cluster flags="--force-internal-endpoint-lookup" clusters=(cluster1 cluster2); for cluster in "${clusters[@]}"; do kind create cluster --name ${cluster} kubectl config rename-context kind-${cluster} ${cluster} clusteradm --context its1 get token | grep '^clusteradm join' | sed "s//${cluster}/" | awk '{print $0 " --context '${cluster}' --singleton '${flags}'"}' | sh done The clusteradm command grabs a token from the hub (its1 context), and constructs the command to apply the new cluster to be registered as a managed cluster on the OCM hub.

Additional Context

No response

[pdettori]

@milanahrae could you pls. show the result of the following command:

$ kubectl --context kind-kubeflex get pods -A

also, I suggest using the triple backticks (```) to enclose the text output from your console rather than a screenshot, it's easier to read.

[MikeSpreitzer]

A little more broadly, please see https://docs.kubestellar.io/release-0.25.0-rc.2/direct/troubleshooting/ . Particularly the "Things to look at" and "Making a good trouble report" sections.

[MikeSpreitzer]

Also, why was this opened in the kubeflex repo rather than the kubestellar repo?