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

Implement release artifact signing beta graduation (KEP-3031) #2586

Closed
4 tasks done
saschagrunert opened this issue Jun 23, 2022 · 1 comment
Closed
4 tasks done

Implement release artifact signing beta graduation (KEP-3031) #2586

saschagrunert opened this issue Jun 23, 2022 · 1 comment
Assignees
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@saschagrunert
Copy link
Member

saschagrunert commented Jun 23, 2022

This issue tracks the implementation details of the Signing release artifacts KEP (kubernetes/enhancements#3031).

The main goal is to sign file artifacts in the same way we do it for container images right now.

Things to be done

Nice to have

@saschagrunert saschagrunert added kind/feature Categorizes issue or PR as related to a new feature. sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Jun 23, 2022
@saschagrunert saschagrunert added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-priority labels Jun 23, 2022
@saschagrunert saschagrunert added this to the v1.25 milestone Jun 23, 2022
@saschagrunert saschagrunert changed the title Implement release artifact signing beta graduation Implement release artifact signing beta graduation (KEP-3031) Jun 23, 2022
@saschagrunert saschagrunert self-assigned this Jul 25, 2022
@saschagrunert
Copy link
Member Author

Since we now have #2618 instead of #2600, I assume that we have to update the KEP and move the implementation to v1.26.

@kubernetes/release-managers thoughts on that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

2 participants