-
Notifications
You must be signed in to change notification settings - Fork 24
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
ROX-20232: Remove all but single collector pipeline #1687
ROX-20232: Remove all but single collector pipeline #1687
Conversation
so that the image is pushed to both expected locations.
240dd82
to
f630740
Compare
value: $(tasks.build-container.results.IMAGE_URL) | ||
- name: ADDITIONAL_TAGS | ||
value: | ||
- $(tasks.determine-image-tag.results.image-tag)-latest |
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.
When (if at all) will the -latest
and -slim
tags be removed? Can we link a Jira issue here?
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.
So far, it's a distant plan for which I created the epic ROX-24402.
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.
Thanks for updating the comment.
It won't build anymore, but will cause trouble in the enterprise contract runs (outdated task definitions), because it is part of every snapshot. I suggest to remove it now. |
Ok, will remove after I merge this and after I back up components. |
Before deleting collector-slim. See stackrox/collector#1687 (comment)
Description
This follows up on #1676 applying the approach from stackrox/scanner#1526.
Also follows up on #1684 cleaning slim stage in Dockerfile and removing slim pipelines.
I use apply-tags task to ensure both
-latest
and-slim
suffixes are provided. I use it to resolve ROX-24116 too.The only thing I worry here is that we'll have a dangling
collector-slim
Konflux component and I wonder if it will cause any trouble. At some point, we'll just kill it.I suggest to review this PR by commits because I tried splitting changes and provided brief messages.
Checklist
These aren't relevant and won't be done:
Testing Performed
All these exist and point to the same image:
quay.io/rhacs-eng/collector:3.18.x-264-ga99ac1e8c3-fast
quay.io/rhacs-eng/collector:3.18.x-264-ga99ac1e8c3-fast-slim
quay.io/rhacs-eng/collector:3.18.x-264-ga99ac1e8c3-fast-latest
quay.io/rhacs-eng/collector:konflux-a99ac1e8c3cc2e19d2714aac0ee4dd5523be2dc4