Unable to look up dockerImageLayers information for all ImageStreamTag objects at once
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
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:
- get the list of istags
- get data for each one individually to then look up the image layer info
This is really time consuming because we have ~300 images
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names oc get istag --all -o yaml, the REST API, and v1.ImageStreamTagList; start by comparing list responses with the per-tag responses described in the reproduction. Done means determining and documenting or implementing a supported way for one list request to return dockerImageLayers for all tags, and verifying it against the roughly 300-image case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100