add support signing container images by using cosign project
- Dominant language
- Go
- Stars
- 329
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the problem/challenge you have**
I would like to sign container images while building them through carvel-kbld.
**Describe the solution you'd like**
[cosign](https://github.com/sigstore/cosign) maintained by [sigstore](https://sigstore.dev/) community is a new standard that allows the signature and verification of container images and OCI artifacts.
we (w/@dentrax @erkanzileli) thought that we can add this support for signing images right after built them.
**Anything else you would like to add:**
[Additional information that will assist in solving the issue.]
---
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
Contributor guide
Research direction
No source files or tests are named. Start by locating kbld's image-building and pushing entry points, then read the linked cosign project documentation; done means container images built through kbld can be signed immediately after they are built.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100