Verifying the Cluster

Verifying the Cluster and Its Contexts

kind 14,561 merges the cluster's credentials into your kubeconfig (~/.kube/config unless KUBECONFIG says otherwise) as a context named kind-l3-booknest, and makes it current. Check it, the nodes, and the server addresses:

Checking the context, the nodes and the two API server addressesShell

kubectl config get-contexts
COLS=NAME:.metadata.name,IP:.status.addresses[0].address
kubectl get nodes -o custom-columns=$COLS,KERNEL:.status.nodeInfo.kernelVersion
kind get kubeconfig --name l3-booknest | grep server:
kind get kubeconfig --name l3-booknest --internal | grep server:

Output

CURRENT   NAME               CLUSTER            AUTHINFO           NAMESPACE
*         kind-l3-booknest   kind-l3-booknest   kind-l3-booknest
NAME                        IP           KERNEL
l3-booknest-control-plane   172.18.0.2   6.18.33.2-microsoft-standard-WSL2
l3-booknest-worker          172.18.0.3   6.18.33.2-microsoft-standard-WSL2
    server: https://127.0.0.1:33443
    server: https://l3-booknest-control-plane:6443

Each node's IP is its container's address on the kind network, and the nodes share the WSL 6 kernel. 127.0.0.1:33443 works only from the host; inside another container, such as Jenkins 8,793 , 127.0.0.1 is that container. The --internal kubeconfig names the control-plane container instead, which the API server's certificate also lists. After a WSL restart the nodes normally return with Docker 514 (restart policy on-failure:1); if not, docker start them.

MENU