kubectl get pods ESP

Description

ESP call for cloud topology:  "kubectl get pods -o json"

Conclusion

Cloud Topology and Post-mortem debugging

Attachments

1

Activity

Show:

Gordon Smith February 22, 2022 at 11:50 AM

I think we should include the whole JSON response for now

Kanghua Wang February 8, 2022 at 4:23 PM

 I just dropped a file which has a sample output for 'kubectl get pods --output=json'. I am not sure how to filter out the non-hpcc pods (if we want to). ESP may send back the whole json object as a string. Or, if you want, ESP can parse some items inside the json object.

Kanghua Wang February 2, 2022 at 8:42 PM
Edited

The third choice will be: I call the "kubectl get pods -o json".  I parse the name, phase ("Pending", "Running", ...), (any other item inside the result?,) and startTime. Then, I give you a list of objects (NAME, PHASE, ...). 

Kanghua Wang February 2, 2022 at 7:25 PM

 I may call the "kubectl get pods -o json" and give you the result as a string. Then, you have to parse it. Or,  I call the "kubectl get pods" and parse the result (assuming that the result format will never change). Then, I give you a list of objects (NAME, READY, STATUS, RESTARTS, and AGE). Which one do you want?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Roadmap

2021q2

Created February 2, 2022 at 3:52 PM
Updated August 16, 2022 at 2:55 PM
Resolved March 9, 2022 at 11:46 AM

Flag notifications