kubectl get pods

From wikieduonline
Jump to navigation Jump to search

kubectl get pods
No resources found in default namespace.
kubectl get pods 
No resources found.
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 -o wide
kubectl get pods -n kube-system
kubectl get pods --all-namespaces 
NAMESPACE                NAME                                                           READY   STATUS                       RESTARTS   AGE
.../...

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


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


kubectl get pods -n kube-system


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

EKS examples

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

Related commands

See also

Advertising: