Get pod logs associated with a owner resource

[aslafy-z]

Is your feature request related to a problem? Please describe.
When I run a multi step argo workflow and want to see logs for each steps, I have to dig them from all pods, one after the other, following the dag flow.

Describe the solution you'd like
I'd love to see all pod logs from an argo-workflows workflow, like I can do with deployments for example, using the l command.

Describe alternatives you've considered
Use stern with the workflow label, but it makes me go out of k9s, which is not good ux.

Additional context
argo-workflows Workflow resource is the owner of the pods. Maybe there's a way to tail logs from a resource descendant pods so the implementation is not specific to argo-workflows but to any other tool with the same setup.

[KevinGimbel]

I feel like this is a very Argo specific request. stern definitely works as alternative, and you could use the stern-plugin for k9s.

Would this work for you? You could see all the logs together and start stern from within k9s, then go right back into k9s when you close the log view.

[aslafy-z]

I disagree that this is specific to argo workflows. There are other external pod controllers out there that could inherit from this functionality. Stern only tails from a pod name pattern / pod label selector afaik.

[KevinGimbel]

There are other external pod controllers out there that could inherit from this functionality

OK, so how does Argo connect Kubernetes objects to Workflows? I'd assume they have a label (like pods started by a replica set get a specific label).

I'm not against implementing something Argo specific; k9s already supports Helm natively so supporting Argo (which is a popular tool as well) seems OK to me.

[aslafy-z]

So yeah, what I meant by descendent pods are pods on which the owner reference is set to the tracked resource (in my case, the workflow).

[aslafy-z]

AFAIK, Kubernetes doesn't natively support automatically discovering owned resources, as discussed in these related issues:

kubernetes/kubernetes#54498

kubernetes/client-go#1085

kubernetes/kubectl#1292

The existing https://github.com/ahmetb/kubectl-tree plugin can serve as a reference, as it already implements this functionality. However, integrating it directly into the k9s code would need careful consideration, especially regarding performance.

Instead of a general implementation, focusing on an Argo Workflow-specific feature might simplify the integration and reduce complexity.