Difference between revisions of "Kubectl get pods -o wide"
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
cm-acme-http-solver-l9dgv 1/1 Running 0 13h 192.168.45.4 ip-192-168-45-192.eu-central-1.compute.internal <none> <none> | cm-acme-http-solver-l9dgv 1/1 Running 0 13h 192.168.45.4 ip-192-168-45-192.eu-central-1.compute.internal <none> <none> | ||
cm-acme-http-solver-r2lxh 1/1 Running 0 13h 192.168.38.163 ip-192-168-45-192.eu-central-1.compute.internal <none> <none> | cm-acme-http-solver-r2lxh 1/1 Running 0 13h 192.168.38.163 ip-192-168-45-192.eu-central-1.compute.internal <none> <none> | ||
+ | |||
+ | [[kubectl get pods -o wide --all-namespaces]] | ||
== See also == | == See also == |
Revision as of 15:13, 3 January 2023
kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES cm-acme-http-solver-bk2n6 1/1 Running 0 13h 192.168.56.1 ip-192-168-45-192.eu-central-1.compute.internal <none> <none> cm-acme-http-solver-l9dgv 1/1 Running 0 13h 192.168.45.4 ip-192-168-45-192.eu-central-1.compute.internal <none> <none> cm-acme-http-solver-r2lxh 1/1 Running 0 13h 192.168.38.163 ip-192-168-45-192.eu-central-1.compute.internal <none> <none>
kubectl get pods -o wide --all-namespaces
See also
Advertising: