Unable to look up dockerImageLayers information for all ImageStreamTag objects at once

[bsquizz]

Is there a more efficient way to obtain the dockerImageLayers for all images? Currently with oc get istag --all the dockerImageLayers info is omitted. I get the same result when listing all ImageStreamTags via the REST API as well. Is there a flag I can pass to have the imageLayer data returned in a v1.ImageStreamTagList?

$ oc version
oc v3.11.43
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server <snip>
openshift v3.11.43
kubernetes v1.11.0+d4cacc0

Steps To Reproduce

oc get istag --all -o yaml

Current Result

Output contains no dockerImageLayers info, it is set to 'null':

apiVersion: v1
items:
- apiVersion: image.openshift.io/v1
  generation: 20
  image:
    dockerImageLayers: null

Expected Result

I'd like to have a way to get the dockerImageLayers for all tags at once. Currently what I have to do is:

1. get the list of istags
2. get data for each one individually to then look up the image layer info

This is really time consuming because we have ~300 images

[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

[bsquizz]

/remove-lifecycle stale

…

On Wed, Dec 25, 2019, 5:27 PM OpenShift Bot ***@***.***> wrote: 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 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23869?email_source=notifications&email_token=AIOU3RR7BOHLTOVOCXV75I3Q2PM5JA5CNFSM4I25CEZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHUUHPQ#issuecomment-568935358>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOU3RR3M77ZLSM2QSLO6NLQ2PM5JANCNFSM4I25CEZA> .

[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

[bsquizz]

/remove-lifecycle stale

…

On Sat, Mar 28, 2020, 2:14 PM OpenShift Bot ***@***.***> wrote: 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 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23869 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOU3RTIMIMAHUXMX6PKEGTRJY5BBANCNFSM4I25CEZA> .

[bsquizz]

/lifecycle frozen