Interact with Nodes¶
After the services are deployed, you can interact with the target cluster using the kubeconfig exported by the Edge Conductor tool.
Get Nodes
To check the available nodes, run the following command:
kubectl get nodes
You will see an output similar to:
NAME STATUS ROLES AGE VERSION
kind-control-plane Ready control-plane,master 2m49s v1.21.1
kind-control-plane2 Ready control-plane,master 2m21s v1.21.1
kind-control-plane3 Ready control-plane,master 86s v1.21.1
kind-worker Ready <none> 68s v1.21.1
kind-worker2 Ready <none> 68s v1.21.1
kind-worker3 Ready <none> 68s v1.21.1
Get Services
To check the services deployed to the KIND cluster, run the following command:
kubectl get services,pods -A
You will see an output similar to:
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 8m51s
ingress-nginx service/ingress-nginx-controller NodePort 10.96.184.207 <none> 80:32672/TCP,443:31014/TCP 8m36s
ingress-nginx service/ingress-nginx-controller-admission ClusterIP 10.96.255.153 <none> 443/TCP 8m36s
kube-system service/kube-dns ClusterIP 10.96.0.10 <none> 53/UDP,53/TCP,9153/TCP 8m49s
portainer service/portainer LoadBalancer 10.96.163.134 <pending> 9000:31121/TCP,8000:30837/TCP 8m36s
prometheus service/prometheus-alertmanager ClusterIP 10.96.8.136 <none> 80/TCP 8m34s
prometheus service/prometheus-blackbox-exporter ClusterIP 10.96.233.20 <none> 9115/TCP 8m33s
prometheus service/prometheus-kube-state-metrics ClusterIP 10.96.146.195 <none> 8080/TCP 8m34s
prometheus service/prometheus-node-exporter ClusterIP None <none> 9100/TCP 8m34s
prometheus service/prometheus-pushgateway ClusterIP 10.96.241.40 <none> 9091/TCP 8m34s
prometheus service/prometheus-server ClusterIP 10.96.111.23 <none> 80/TCP 8m34s
NAMESPACE NAME READY STATUS RESTARTS AGE
ingress-nginx pod/ingress-nginx-admission-create-7lxjr 0/1 Completed 0 8m34s
ingress-nginx pod/ingress-nginx-admission-patch-t867v 0/1 Completed 0 8m34s
ingress-nginx pod/ingress-nginx-controller-6c85cb7b5d-qj9wn 1/1 Running 0 8m34s
kube-system pod/coredns-558bd4d5db-68kbq 1/1 Running 0 8m34s
kube-system pod/coredns-558bd4d5db-t5jwg 1/1 Running 0 8m34s
kube-system pod/etcd-kind-control-plane 1/1 Running 0 8m37s
kube-system pod/kindnet-7r42x 1/1 Running 0 8m34s
kube-system pod/kube-apiserver-kind-control-plane 1/1 Running 0 8m37s
kube-system pod/kube-controller-manager-kind-control-plane 1/1 Running 0 8m37s
kube-system pod/kube-multus-ds-amd64-rstfb 1/1 Running 0 8m34s
kube-system pod/kube-proxy-4gcth 1/1 Running 0 8m34s
kube-system pod/kube-scheduler-kind-control-plane 1/1 Running 0 8m37s
local-path-storage pod/local-path-provisioner-547f784dff-xh4wq 1/1 Running 0 8m34s
portainer pod/portainer-fc654c454-nnls8 1/1 Running 0 8m34s
prometheus pod/prometheus-alertmanager-84f4ccb57d-gqpt5 2/2 Running 0 8m34s
prometheus pod/prometheus-blackbox-exporter-5fcfbd67b6-m9rmm 1/1 Running 0 8m33s
prometheus pod/prometheus-kube-state-metrics-bc6c8c864-z729b 1/1 Running 0 8m34s
prometheus pod/prometheus-node-exporter-m4dxx 1/1 Running 0 8m17s
prometheus pod/prometheus-pushgateway-685556f875-nxt9j 1/1 Running 0 8m34s
prometheus pod/prometheus-server-c8f78b8d6-kgphw 2/2 Running 0 8m34s