New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Imagestream generator #427
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well based on the our Container catalog, we have e.g https://catalog.redhat.com/software/containers/rhel9/nodejs-18-minimal/62e8e8ffa9a2233d923f5f1c?q=nodejs&architecture=amd64&image=6601e09c5781451e968f8dd5&container-tabs=gti
as rhel9/nodejs-18-minimal
or ubi9/nodejs-18-minimal
I would prefer to have the same semantic as in Container Catalog, like
but this change has to be sent to OpenShift 4 team so that they properly use it. Only for sure.
Thanks. @fbm3307 Could you please take a look? |
@yselkowitz Sorry for bothering you again. What do you think about changing imagestreams names from |
Changing existing imagestreamtag names would break any existing use of that tag. If there was an actual need for a rename -- as there was when we moved from e.g. 14 to 14-ubiN -- then this could be accomplished by adding the new name and marking the old name as hidden, but the latter would have to be kept for the duration of the underlying image's lifetime. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep the old name so we do not break functional who uses our imagestreams.
91217d5
to
ae0b972
Compare
Thanks, @yselkowitz, for the information. |
The ci-script PR has been merged. [test-all] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks
Here the problem is, that we have the minimal tags created differently than in other containers:
vs
@phracek please keep this in mind when reviewing. This could be an issue.