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

[Feature]: Implementation of OCI image signature and SBOM attestation #924

Open
2 tasks done
R3DRUN3 opened this issue Feb 7, 2024 · 0 comments
Open
2 tasks done

Comments

@R3DRUN3
Copy link
Contributor

R3DRUN3 commented Feb 7, 2024

Checklist

  • I've searched for similar issues and couldn't find anything matching
  • I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?

No

Problem Description

At its current state, the project exhibits suboptimal supply chain management.
The generated OCI images for k8sgpt are neither signed nor attested.

Solution Description

The proposed solution suggests minimal adherence to these best practices, by signing and attesting the images using their SBOM as a predicate.

Benefits

Main benefits are:

  1. Certify both image and SBOM provenance.
  2. Have the SBOM available in the same registry as the image, enabling effortless downloading for all users.
  3. Implementing specific admission policies with tools such as Kyverno and Sigstore Policy Controller.

Potential Drawbacks

No response

Additional Information

For an implementation reference on GitHub Actions, please refer to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Proposed
Development

No branches or pull requests

1 participant