I guess they would say that you have to send the output of that to be inputs of another kubectl command like $ kubectl logs -n foo $(kubectl get pod -n foo |

I guess they would say that you have to send the output of that to be inputs of another kubectl command like $ kubectl logs -n foo $(kubectl get pod -n foo | awk '/Running/{print $1}') because one of their selling points is "no nested kubectl queries". I don't see how their queries can be more efficient than hitting the kube-apiserver multiple times, unless they have something that lives clusterside observing lifecycle events for all CRDs and answering queries with only one round-trip instead of multiple. Or maybe they're selling "no nested kubectl queries" as an experience feature, saying that a query language is more ergonomic than bash command redirection. My brain has been warped into the shape of the shell, for better or for worse, so it's not a selling point for me.