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
Signing Release Artifacts #3031
Comments
Is this also relevant to SIG Security? |
Yes I have my 👀 on this :) |
Waiting a bit more for alignment on #3051, then I'll push out the KEP PR. |
The KEP got merged, we will now define an MVP and integrate it into our release process. I'm following-up with a dedicated issue on that. |
Hello @saschagrunert 👋, 1.24 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022. For note, This enhancement is targeting for stage Here’s where this enhancement currently stands:
Looks like for this one, we would require updating the existing KEP proposal to reflect the following:
At the moment, the status of this enhancement is marked as |
With #3191 merged, I've updated the status to |
This patch outlines basic documentation about how container image signing works and which images are signed for official Kubernetes releases. Refers to kubernetes/enhancements#3031 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
This patch outlines basic documentation about how container image signing works and which images are signed for official Kubernetes releases. Refers to kubernetes/enhancements#3031 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
This patch outlines basic documentation about how container image signing works and which images are signed for official Kubernetes releases. Refers to kubernetes/enhancements#3031 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
This patch outlines basic documentation about how container image signing works and which images are signed for official Kubernetes releases. Refers to kubernetes/enhancements#3031 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
This patch outlines basic documentation about how container image signing works and which images are signed for official Kubernetes releases. Refers to kubernetes/enhancements#3031 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Hi @saschagrunert 👋 1.24 Docs shadow here. Thanks for getting the docs placeholder PR for this KEP created so early in the process! The next deadline for 1.24 is to have the PR ready for review by Tuesday April 5, 11:59 PM PDT. Thanks! |
Hi @saschagrunert 👋 Checking in as we approach 1.24 code freeze at 01:00 UTC Wednesday 30th March 2022. For this KEP, it looks like there aren't any K/K PRs. Are there any other PRs that you think we should be tracking that would be subject to the 1.24 code freeze? Thanks!! |
Hey @salaxander, no we do not require any k/k code changes for this enhancement. 👍 |
Hello @saschagrunert 👋, 1.26 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022. This enhancement is targeting for stage Here’s where this enhancement currently stands:
With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀 The status of this enhancement is marked as |
Feature blog post placeholder: kubernetes/website#37639 |
Hi @saschagrunert 👋, Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022. Please ensure the following items are completed:
For this enhancement, I could not locate any open k/k PRs. Please plan to get PRs out for all k/k code and the open PRs mentioned above in the issue, so it can be merged up by code freeze. If you do have k/k PRs open, please link them to this issue. Let me know if there aren't any further PRs that need to be created or merged for this enhancements, so that I can mark it as As always, we are here to help should questions come up. Thanks! |
@parul5sahoo thank you for the notice. Our code changes will live out of k/k so we should be already good to go for both tasks mentioned in your comment. |
@saschagrunert great then the enhancement is good to go for code freeze. |
Hello @saschagrunert 👋, 1.26 Release Docs Lead here. This enhancement is marked as ‘Needs Docs’ for 1.26 release. Please follow the steps detailed in the documentation to open a PR against Any doubt, reach us! Thank you! |
@Verolop do you wanna take care of this? 🙃 |
Hi @saschagrunert ! Thank you for the docs PR here |
Hello @saschagrunert 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before deadline Tuesday 15th November 2022. Thank you! |
/remove-label lead-opted-in |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Not planned for graduating in v1.28. |
Good |
Enhancement Description
cosign
release#2227k/enhancements
) update PR(s): KEP-3031: Add release artifact signing KEP #3061k/k
) update PR(s): Implement container image signing MVP (KEP-3031) release#2383k/website
) update PR(s):Add container image signing docs website#31610
Task Page for Verifying Signed Images website#32184
k/enhancements
) update PR(s):Graduate release artifact signing to beta #3323
KEP-3031: Update signing KEP to match new scope #3451
k/k
) update PR(s): Implement release artifact signing beta graduation (KEP-3031) release#2586k/website
) update(s): Document Kubernetes release artifact file signatures website#35341/area release-eng
/sig release
/cc @kubernetes/sig-release-leads @kubernetes/release-managers @kubernetes/release-engineering
refers to kubernetes/sig-release#1724
depends on #3027
The text was updated successfully, but these errors were encountered: