Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access full details of STATUS column from "kubectl get pod" #130

Open
brobichaud opened this issue Oct 26, 2020 · 1 comment
Open

Access full details of STATUS column from "kubectl get pod" #130

brobichaud opened this issue Oct 26, 2020 · 1 comment

Comments

@brobichaud
Copy link
Collaborator

I'm building a UI that shows some of the details you see in the "kubectl get pod -o wide" command. I'm having trouble finding the data seen in the STATUS field. Currently I'm reading K8sPod.Status.Phase but it is not showing me all the states that a pod goes through. Below is a snippet showing 3 different states a pod might be in (there are others). I can't seem to find these anywhere in the object model. Am I missing something?

NAME                                      READY   STATUS              RESTARTS   AGE
labs-burns-portal-567859f4fd-gchvw        1/1     Running             0          3d21h
labs-burns-portal-567859f4fd-mnnpp        0/1     Terminating         0          2d18h
labs-burns-portal-6fbd9d444b-jwwcg        0/1     ContainerCreating   0          17s
labs-burns-portal-6fbd9d444b-qschr        1/1     Running             0          116s
@brobichaud brobichaud changed the title Access full details of "kubectl get pod -o wide" Access full details of STATUS column from "kubectl get pod" Oct 26, 2020
@tintoy
Copy link
Owner

tintoy commented Oct 26, 2020

From memory there is a kubectl switch that will dump out the response from the API which should allow you to see where that value appears in the JSON.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants