Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

@brendandburns Thanks for reviewing my code. I correct all mistakes except for the third_party code problem. Actually, for the third_party code, I write 30% of them and the rest are copied from golang project.

I rewrite parser so the parser code do't need to be put in third party directory.

This is failing Shippable, I think we need to rebase the gsoc branch to HEAD (and in general, Shippable doesn't seem to handle testing PRs to branches other than master very well)

@daizuozhuo Please ping any open PRs and/or issues with current status at least once a week to ensure they don't drop off our radar.

@brendandburns I have finished all features. Could you review it?

yes, will look by the end of the week. Thanks!
--brendan

@brendandburns I just added doc.go. Can you take a look at it?

Thanks.

More examples:

Getting info about last termination(s):

kubectl get pods/pod-w-message -o template -t "{{range .status.containerStatuses}}{{.lastState.terminated.message}}{{end}}"

Getting external IP of a service of type LoadBalancer, which I found easier to do with grep than with a template:

kubectl get svc my-nginx -o json | grep \"ip\"

While awaiting another review on this, you could write another PR that adds this as a new output format to kubectl, such as -o jsonpath.

I would like to eventually use this to specify field references in the downward API.

Few small comments and a request for parser tests for ill-formed input.

@bgrant0607 To get external IP of a service of type LoadBalancer, we can use "{..ip}" to find the key ip recursively in JSONPath.

Ok, since we're now in post 1.0, can you rebase this on master, and we can merge it in.

Thanks!
--brendan

@brendandburns Do you mean reopen this pull request on master? If not, can you tell me how to do this?