Difference between revisions of "Kubectl get nodes"
Jump to navigation
Jump to search
(→Errors) |
(→Errors) |
||
| Line 68: | Line 68: | ||
Unable to connect to the server: EOF | Unable to connect to the server: EOF | ||
| − | kubectl get nodes | + | [[kubectl get]] nodes |
error: exec plugin: [[invalid apiVersion]] "[[client.authentication.k8s.io]]/[[v1alpha1]]" | error: exec plugin: [[invalid apiVersion]] "[[client.authentication.k8s.io]]/[[v1alpha1]]" | ||
Revision as of 17:03, 17 July 2022
kubectl get nodes kubectl get nodes -w kubectl get nodes --watch kubectl get -h
Contents
Examples
kubectl get nodes NAME STATUS ROLES AGE VERSION node2 Ready <none> 23h v1.14.3-docker-2 ubuntu1804-1 Ready master 23h v1.14.3-docker-2
kubectl get nodes NAME STATUS ROLES AGE VERSION 172.17.255.254 Ready master 11d v1.14.8
kubectl get nodes NAME STATUS ROLES AGE VERSION master Ready master 67m v1.14.0 node01 Ready <none> 67m v1.14.0
Official doc:
kubectl get nodes NAME STATUS ROLES AGE VERSION kube-worker-1 NotReady <none> 1h v1.23.3 kubernetes-node-bols Ready <none> 1h v1.23.3 kubernetes-node-st6x Ready <none> 1h v1.23.3 kubernetes-node-unaj Ready <none> 1h v1.23.3
EKS
kubectl get nodes NAME STATUS ROLES AGE VERSION ip-192-168-72-109.us-east-2.compute.internal Ready <none> 9m38s v1.21.5-eks-bc4871b ip-192-168-8-185.us-east-2.compute.internal Ready <none> 9m34s v1.21.5-eks-bc4871b
Terraform example:
kubectl get nodes NAME STATUS ROLES AGE VERSION ip-10-0-1-48.us-east-2.compute.internal Ready <none> 32m v1.20.11-eks-f17b81 ip-10-0-1-85.us-east-2.compute.internal Ready <none> 33m v1.20.11-eks-f17b81 ip-10-0-3-153.us-east-2.compute.internal Ready <none> 32m v1.20.11-eks-f17b81
kubectl get nodes NAME STATUS ROLES AGE VERSION ip-10-0-1-149.us-east-2.compute.internal Ready <none> 5h40m v1.20.11-eks-f17b81 ip-10-0-2-121.us-east-2.compute.internal Ready <none> 5h40m v1.20.11-eks-f17b81
GKE
kubectl get nodes NAME STATUS ROLES AGE VERSION gke-your-pool-1-040c69dc-gq56 Ready <none> 30h v1.21.11-gke.1900 gke-your-pool-2-040c69dc-ncj5 Ready <none> 30h v1.21.11-gke.1900 gke-your-pool-2-040c69dc-rkj2 Ready <none> 30h v1.21.11-gke.1900 gke-your-pool-3-737b2f5f-tbu5 Ready,SchedulingDisabled <none> 28h v1.21.11-gke.1900
Errors
kubectl get nodes
Unable to connect to the server: dial tcp: lookup 00A50xxxx.gr7.us-east-2.eks.amazonaws.com: no such host
Solution: review ~/.kube/config
kubectl get nodes The connection to the server localhost:8080 was refused - did you specify the right host or port?
kubectl get nodes Unable to connect to the server: EOF
kubectl get nodes error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"
Minikube
kubectl get nodes NAME STATUS ROLES AGE VERSION minikube Ready control-plane,master 3d21h v1.21.2
kubectl get nodes NAME STATUS ROLES AGE VERSION minikube Ready master 12m v1.18.0
kind
kubectl get nodes NAME STATUS ROLES AGE VERSION kind-control-plane Ready control-plane,master 10m v1.20.2
kubectl get nodes --show-labels (See also: Kubectl label)
kubectl get nodes The connection to the server localhost:8080 was refused - did you specify the right host or port?
kubectl get nodes -w
kubectl get nodes error: You must be logged in to the server (Unauthorized)
Related
kubectl get podskubectl get svckubectl describe nodeskubectl label~/.kube/configkubectl drainkubectl uncordon
See also
kubectl get: [all|componentstatus | pods | apiservices | events|event|nodes|replicaset|services|svc|namespaces|hpa|secret | deployments | serviceaccounts | endpoints | daemonset | networkpolicy],kubectl get -h- Kubectl information commands:
cluster-info|view|pods|nodes|services|version|describe | logs kubectl: [cp | config | create|delete|edit | explain |apply|exec|get|set|drain | uncordon | rolling-update|rollout|logs|run|auth|label | annotate|version|top|diff|debug|replace|describe|port-forward | proxy|scale|rollout|api-resources| expose deployment | expose | patch | attach | get endpoints | ~/.kube/config | kubectl logs --help | kubectl --help, kubectl-convert, kubectl autoscale, kubectl.kubernetes.io
Advertising:
