kubectl get pods

From wikieduonline
(Redirected from Your-pod-name)
Jump to navigation Jump to search

kubectl get pods -A
kubectl get pods
kubectl get pods -n kube-system
kubectl get pods -l
kubectl get pods --show-labels
kubectl get pods -o json
kubectl get pods -o wide
kubectl get pods --selector=app=your_app

kubectl get --no-headers pods -o custom-columns="metadata.name" 
kubectl get --no-headers pods -o custom-columns=":metadata.namespace,metadata.name" 
kubectl get pods
No resources found in default namespace.
ContainerCreating
Running
ImagePullBackOff
Init:ImagePullBackOff
Init:ErrImagePull
Init:CrashLoopBackOff
Terminating
ErrImagePull
Completed
Evicted
kubectl get pods 
No resources found.


kubectl get pods --all-namespaces 
NAMESPACE                NAME                                                           READY   STATUS                       RESTARTS   AGE
.../...

List all containers and images by pod:

kubectl get pods -o jsonpath='{range .items[*]}{"pod: "}{.metadata.name}{"\n"}{range .spec.containers[*]}{"\tname: "}{.name}{"\n\timage: "}{.image}{"\n"}{end}'

List containers on a POD:

kubectl get pods YourPOD -o jsonpath='{.spec.containers[*].name}'
kubectl get pods
NAME                                               READY   STATUS    RESTARTS   AGE
grafana-97d4b5896-ksvz5                            1/1     Running   0          7m22s
metrics-server-679944f8f6-mbfns                    1/1     Running   0          2m9s
my-release-kubernetes-dashboard-77db8d9694-s47rs   1/1     Running   0          21m
kubectl get pods --all-namespaces 
NAMESPACE                NAME                                                           READY   STATUS                       RESTARTS   AGE
.../...
monitoring    fluentd-68gzh                                                     0/1     CrashLoopBackOff   31         84m
monitoring    fluentd-74t7v                                                     0/1     CrashLoopBackOff   31         83m
monitoring    fluentd-dcr87                                                     0/1     CrashLoopBackOff   31         83m
.../...
kubectl get pods --all-namespaces
NAMESPACE     NAME                                               READY   STATUS    RESTARTS   AGE
default       grafana-97d4b5896-x324                            0/1     Pending   0          41h
default       metrics-server-679944f8f6-45ttt                    0/1     Pending   0          41h
default       my-release-kubernetes-dashboard-77db8d9694-4p7cg   0/1     Pending   0          41h
kube-system   aws-node-4zxyz                                     1/1     Running   0          4d18h
kube-system   aws-node-hxyz8                                     1/1     Running   0          4d18h
kube-system   aws-node-w59tt                                     1/1     Running   0          4d18h
kube-system   coredns-5c778788f4-2x4vq                           0/1     Pending   0          41h
kube-system   coredns-5c778788f4-dlhx5                           0/1     Pending   0          41h
kube-system   kube-proxy-xdr4                                   1/1     Running   0          4d18h
kube-system   kube-proxy-vtx4                                   1/1     Running   0          4d18h
kube-system   kube-proxy-w8xyz                                   1/1     Running   0          4d18h


kubectl get pods 
NAME                                         READY   STATUS      RESTARTS   AGE
your_pod_name_1                            1/1     Running              1          11d
your_pod_name_2                            1/1     Running              1          11d
your_pod_name_3                            0/1     Completed          0          7h44m
kubectl get pods
NAME                                              READY   STATUS    RESTARTS   AGE
metrics-server-6467f65c76-kfkkl                   1/1     Running   0          7h32m
my-release-kubernetes-dashboard-5bf6f9f78-phkvz   1/1     Running   0          7h19m



kubectl get pods -n kube-system


kubectl get pods -l app=nginx -L YOUR_LABEL
-L or --label-columns


kubectl get pods -n kube-system

Minikube[edit]

kubectl get pods -A

minikube

kubectl get pods
NAME                              READY   STATUS    RESTARTS   AGE
hello-minikube-64b64df8c9-bxt7g   1/1     Running   0          20m

minikube

kubectl get pods
No resources found in default namespace.


After installing Istio on a minikube cluters

kubectl get pods
NAME                                                   READY   STATUS    RESTARTS   AGE
details-v1-6fc55d65c9-9ct4x                            2/2     Running   0          13m
hello-minikube-64b64df8c9-bxt7g                        1/1     Running   3          11d 
my-release-ingress-nginx-controller-7859896977-dh96p   1/1     Running   4          10d
productpage-v1-7f44c4d57c-crd2n                        2/2     Running   0          13m
ratings-v1-6f855c5fff-trdsv                            2/2     Running   0          13m
reviews-v1-54b8794ddf-x76ms                            2/2     Running   0          13m
reviews-v2-c4d6568f9-6m9kw                             2/2     Running   0          13m
reviews-v3-7f66977689-6cl9m                            2/2     Running   0          13m

Killer[edit]

 kubectl -n kube-system get pod
NAME                                       READY   STATUS    RESTARTS   AGE
coredns-66bff467f8-k8f48                   1/1     Running   0          26h
coredns-66bff467f8-rn8tr                   1/1     Running   0          26h
etcd-cluster2-master1                      1/1     Running   0          26h
kube-apiserver-cluster2-master1            1/1     Running   0          26h
kube-controller-manager-cluster2-master1   1/1     Running   0          26h
kube-proxy-qthfg                           1/1     Running   0          25h
kube-proxy-z55lp                           1/1     Running   0          26h
kube-scheduler-cluster2-master1            1/1     Running   1          26h
weave-net-cqdvt                            2/2     Running   0          26h
weave-net-dxzgh                            2/2     Running   1          25h

Errors[edit]

kubectl get pods
The connection to the server localhost:8080 was refused - did you specify the right host or port?

Review: ~/.kube/config

EKS examples[edit]

Not working

kubectl get pods
NAME                       READY   STATUS    RESTARTS   AGE
grafana-6d966d974b-7cc5f   0/1     Evicted   0          74m
grafana-6d966d974b-8hpw6   0/1     Pending   0          74m
grafana-6d966d974b-8s29j   0/1     Evicted   0          74m
grafana-6d966d974b-9pn6p   0/1     Evicted   0          176m
grafana-6d966d974b-k8rz5   0/1     Evicted   0          74m
grafana-6d966d974b-q8j9w   0/1     Evicted   0          132m
grafana-6d966d974b-scgkn   0/1     Evicted   0          74m
grafana-6d966d974b-wmvcg   0/1     Evicted   0          74m
grafana-6d966d974b-xjw86   0/1     Evicted   0          74m
grafana-6d966d974b-xsvv4   0/1     Evicted   0          74m
kubectl -n kube-system -l=k8s-app=kube-dns get pods
NAME                      READY   STATUS    RESTARTS   AGE
coredns-f47955f89-7ntw4   0/1     Pending   0          3h37m
coredns-f47955f89-sl79r   0/1     Pending   0          3h37m

Working:

kubectl get pods
NAME                       READY   STATUS    RESTARTS   AGE
grafana-65b996b88c-dxg4l   1/1     Running   0          97s
kubectl -n kube-system -l=k8s-app=kube-dns get pods
NAME                      READY   STATUS    RESTARTS   AGE
coredns-f47955f89-dshkm   1/1     Running   0          14h
coredns-f47955f89-z59pt   1/1     Running   0          14h

NoCredentialProviders

kubectl get pods
could not get token: NoCredentialProviders: no valid providers in chain. Deprecated. 
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
could not get token: NoCredentialProviders: no valid providers in chain. Deprecated. 
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
could not get token: NoCredentialProviders: no valid providers in chain. Deprecated. 
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
could not get token: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
could not get token: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
Unable to connect to the server: getting credentials: exec: executable aws-iam-authenticator failed with exit code 1


kubectl get pods
NAME                                              READY   STATUS             RESTARTS   AGE
your-pod1               0/5     Terminating        3682       13d
your-pod2               0/1     Terminating        0          7d6h

Related[edit]

See also[edit]

Advertising: