Remove all driver related files #2124
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey @Molter73 - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2124 +/- ##
=======================================
Coverage 28.83% 28.83%
=======================================
Files 96 96
Lines 5799 5799
Branches 2551 2551
=======================================
Hits 1672 1672
Misses 3408 3408
Partials 719 719
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Molter73
changed the title
This was referenced Jun 11, 2025
These files are used to correlate collector versions to stackrox versions, main use for it was to create the index directory for support-packages. Since support-packages have been deprecated since 4.4, there's not much point in keeping these files updated anymore and the only purpose it seems to serve is taking up release engineers time ping-ponging a PR that gets a rubber-stamped "approved" and merge from the collector team. Hence, we are removing the files from the collector repo altogether. Correlating versions between stackrox and collector can be achieved using the following command in the main repo: `git show <tag>:COLLECTOR_VERSION` I will add that command to our documentation as part of a larger cleanup.
And by extension all scripts, files and actions related to drivers.
Molter73
force-pushed
the
mauro/remove-released-versions
branch
from
79e36b7 to
fdeac2b
Compare
Stringy
approved these changes
Sep 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Kernel modules and eBPF probes (collectively known as "drivers"), have been deprecated for quite some time and the last versions that still supported them have reached EOL. As such, we shouldn't have to update them anymore.
This PR gets rid of all the leftover scripts that downloaded drivers, uploaded them to GCP, packaged them as support-packages, uploaded those to GCP, created the index for the CDN page, etc.
We also remove the
RELEASED_VERSIONS,RELEASED_VERSIONS.unsupportedandKERNEL_VERSIONSfiles, these were only used for driver and support-package related tasks and are now pointless. Correlating versions between stackrox and collector can be achieved using the following command in the main repo:git show <tag>:COLLECTOR_VERSIONI will add that command to our documentation as part of a separate doc cleanup PR (I think this one is large enough as is).
Checklist
Automated testing
If any of these don't apply, please comment below.
Testing Performed
CI should be enough.