oc adm inspect pod should get pod logs

[kgibm]

oc adm inspect is a wonderful tool to gather resource YAMLs and the omc tool is a great way to explore those; however, I can't find a way to get pod logs besides using oc adm inspect namespace/$NS which gathers way too much other stuff. It would be nice if oc adm inspect pods gathered pod logs in addition to the YAMLs.

I understand I can get the logs directly with oc logs $POD, but the beauty of oc adm inspect is that it can get data on many resources at once and it's set up for use with omc. In addition, oc logs needs to be piped to a file for sharing with others, and this is hard to scale with many pods. oc adm inspect has the capability to get pod logs as it does it when getting the whole namespace, so I was hoping there was some way to tell it to get pod logs in a more narrow way.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.