Difference between revisions of "Kubectl get nodes"

From wikieduonline
Jump to navigation Jump to search
Line 17: Line 17:
 
  master  Ready    master  67m  v1.14.0
 
  master  Ready    master  67m  v1.14.0
 
  node01  Ready    <none>  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]] ==
 
== [[EKS]] ==

Revision as of 19:09, 23 May 2022

kubectl get nodes
kubectl get nodes -w
kubectl get -h
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
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

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 commands

See also

Advertising: