attest SBOM to staging images as well

Open
#118 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, kubernetes
Domain
devops, release, security

Research direction

Start by locating the release pipeline that builds staging images and the existing SBOM attestation flow for released images. Trace how staging images are published and identify where the same attestation step would apply; done means staging images receive SBOM attestations and the pipeline verifies them.

Written by the indexing model from the issue text.

Description

Container

/kind feature

While releasing alpha.4 version, we found a bug in the release pipeline, we could have avoided the same if we used same pipeline for attesting SBOM staging images. This issue tracks attesting SBOMs to staging images as well.

Environment:

  • cluster-stack-operator version:
  • Kubernetes version: (use kubectl version)
  • OS (e.g. from /etc/os-release):
Dominant language
Go
Stars
18
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SovereignCloudStack/cluster-stack-operator

All issues in SovereignCloudStack/cluster-stack-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.