Skip to content
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

feat: report vulnerabilities as GH issues and scan images from registry #80

Merged
merged 4 commits into from
Oct 15, 2024

Conversation

DnPlas
Copy link
Contributor

@DnPlas DnPlas commented Oct 15, 2024

This PR brings all the changes from KF-6331-dev-branch into main.

This commit adds get-published-images-scan-and-report.yaml, a re-usable workflow
that enables repositories to scan images from a public registry (in the case
of the Analytics team it defaults to charmedkubeflow) and reports back
the security vulnerabilities as Github issues.
This workflow is intended to be used on demand (using a workflow dispatch)
and on schedule, as it will be used for continuous testing of the published
images a rock repository generates.

This re-usable workflow can be used for reporting security vulnerabilities
via Github issues. It takes the issue title, image-name, and issue-labels as
inputs, and in turn:

  • edits an existing issue with the same title and updates the vulnerability report
  • creates a new issue with the issue-title and adds the vulnerability report in the description

Please NOTE this workflow assumes the existence of vulnerability reports as artefacts
of a workflow run; that is, it expects artefacts named trivy-report- to
be present in the sabe workflow run.

Bump the version of this actions to be up to date with the latest.

All changes have been tested individually in their respective PRs.

#71)

* chore, ci: bump artifact download/upload and checkout actions v3 -> v4

Bump the version of this actions to be up to date with the latest.
* ci: add workflow to enable automatic vulnerability reports

This re-usable workflow can be used for reporting security vulnerabilities
via Github issues. It takes the issue title, image-name, and issue-labels as
inputs, and in turn:
* edits an existing issue with the same title and updates the vulnerability report
* creates a new issue with the issue-title and adds the vulnerability report in the description

Please NOTE this workflow assumes the existence of vulnerability reports as artefacts
of a workflow run; that is, it expects artefacts named trivy-report-<image-name> to
be present in the sabe workflow run.

Part of #69
#73)

* ci: add re-usable workflow for scans from published img and automatic reports

This commit adds get-published-images-scan-and-report.yaml, a re-usable workflow
that enables repositories to scan images from a public registry (in the case
of the Analytics team it defaults to charmedkubeflow) and reports back
the security vulnerabilities as Github issues.
This workflow is intended to be used on demand (using a workflow dispatch)
and on schedule, as it will be used for continuous testing of the published
images a rock repository generates.

Part of #69
@DnPlas DnPlas requested a review from a team as a code owner October 15, 2024 09:19
@DnPlas DnPlas merged commit 9b40143 into main Oct 15, 2024
@DnPlas DnPlas deleted the KF-6331-dev-branch branch October 15, 2024 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants