K9s: Expand to see containers in pods

[lfundaro]

Hi !

I would like to propose an enhancement, unless this is already implemented 🙈.

When browsing pods, I would like to be able to hit and expand the containers within that pod.

For example:

| Namespace | Name | Read.... |
| ------------- |:-------------:| -----:|
| foo | bar | 2/2 |
| | -> container_A |
| | -> container_B |

what do you think ?

If you like this idea i might be able to help !

[derailed]

Thanks for the report @lfundaro! I think it could be useful but what else would you show? Isn't it a functionality we currently have by just viewing or describing the pod?

[mrballcb]

I too feel this would be useful if can get the same type of behavior as kubectl top pods --containers. For example:

(⎈ |ren:default) $ kubectl get pods -n dev -l app=kibana
NAME                     READY     STATUS    RESTARTS   AGE
kibana-6897c4859-2rdmz   2/2       Running   0          6d
kibana-6897c4859-4fqdw   2/2       Running   0          6d
kibana-6897c4859-ckkvs   2/2       Running   0          6d
(⎈ |ren:default) $ kubectl top pods -n dev -l app=kibana --containers
POD                      NAME      CPU(cores)   MEMORY(bytes)
kibana-6897c4859-2rdmz   nginx     1m           3Mi
kibana-6897c4859-2rdmz   kibana    5m           219Mi
kibana-6897c4859-4fqdw   nginx     1m           3Mi
kibana-6897c4859-4fqdw   kibana    6m           210Mi
kibana-6897c4859-ckkvs   kibana    5m           297Mi
kibana-6897c4859-ckkvs   nginx     1m           3Mi

It becomes very clear in multi container pods which container is actually consuming memory or cpu. However, I'll note that there doesn't appear to be an easy way to get this info directly from kubectl get pods either (at least in kubectl 1.10.x), so it's probably a pretty large ask.

[derailed]

@mrballcb @lfundaro Fixed 0.5.0!

[lfundaro]

nice ! thanks a lot ! 🎊