search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.39k stars 1.45k forks source link

Signing Release Artifacts #3031

Open saschagrunert opened 2 years ago

saschagrunert commented 2 years ago

Enhancement Description

/area release-eng /sig release /cc @kubernetes/sig-release-leads @kubernetes/release-managers @kubernetes/release-engineering refers to https://github.com/kubernetes/sig-release/issues/1724 depends on https://github.com/kubernetes/enhancements/issues/3027

sftim commented 2 years ago

Is this also relevant to SIG Security?

PushkarJ commented 2 years ago

Yes I have my 👀 on this :) /sig security

saschagrunert commented 2 years ago

Waiting a bit more for alignment on https://github.com/kubernetes/enhancements/pull/3051, then I'll push out the KEP PR.

saschagrunert commented 2 years ago

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.

Priyankasaggu11929 commented 2 years ago

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 alpha for 1.24 (correct me, if otherwise)

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 at-risk. Please keep the issue description up-to-date with appropriate stages, for release team tracking purpose. Thank you so much! 🙂

rhockenbury commented 2 years ago

With #3191 merged, I've updated the status to tracked for enhancement freeze. Thanks!

chrisnegus commented 2 years ago

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!

salaxander commented 2 years ago

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!!

saschagrunert commented 2 years ago

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?

Hey @salaxander, no we do not require any k/k code changes for this enhancement. :+1:

saschagrunert commented 2 years ago

Docs PR got merged, we’re good to go.

Priyankasaggu11929 commented 2 years ago

/milestone clear

sftim commented 2 years ago

Also relevant to https://github.com/kubernetes/release/issues/913

Priyankasaggu11929 commented 2 years ago

Hello @saschagrunert 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PT on Thursday June 23, 2022, which is just over 2 days from now.

For note, This enhancement is targeting for stage beta for 1.25

Here's where this enhancement currently stands:

Looks like for this one, we would just require updating the following:

For note, the status of this enhancement is marked as at risk. Thanks for keeping the issue-description up-to-date. 🙂

saschagrunert commented 2 years ago

@Priyankasaggu11929 the KEP update merged, I hope we're now good to go. :slightly_smiling_face:

Priyankasaggu11929 commented 2 years ago

Thanks @saschagrunert, the KEP was marked as tracked before Enhancements Freeze. We’re all good on this one.

Thank you so much! 🙂

parul5sahoo commented 2 years ago

Hi @saschagrunert 👋

Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure the following items are completed:

I was unable to find any recent k/k PRs related to this enhancement. Could you point me to them if there're any or if you plan to open any PRs, kindly please link them in the issue. Thank you so much.

The status of the enhancement is currently marked at at-risk.

Priyankasaggu11929 commented 2 years ago

Hello @saschagrunert, could you please confirm that there will be no k/k code PRs for the implementation of this enhancement?

And all code will be merged either in the k/release & k-sigs/release-sdk & other release engineering repos?

If that would be the case, the enhancement team will mark this enhancement as tracked for the 1.25 code freeze. Thank you!

saschagrunert commented 2 years ago

Hey @Priyankasaggu11929, there will be no k/k PRs. Nevertheless the scope of the KEP has changed a bit and would require an update. Therefore I tend to move the enhancement to v1.26 to release the pressure especially from the docs perspective.

Priyankasaggu11929 commented 2 years ago

Thanks for the prompt update, @saschagrunert. 🙂

/milestone clear

rhockenbury commented 1 year ago

/label tracked/yes /remove-label tracked/no /milestone v1.26

k8s-ci-robot commented 1 year ago

@rhockenbury: Those labels are not set on the issue: tracked/no

In response to [this](https://github.com/kubernetes/enhancements/issues/3031#issuecomment-1255233609): >/label tracked/yes >/remove-label tracked/no >/milestone v1.26 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
parul5sahoo commented 1 year ago

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 beta for 1.26 (correct me, if otherwise)

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 tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

saschagrunert commented 1 year ago

Feature blog post placeholder: https://github.com/kubernetes/website/pull/37639

parul5sahoo commented 1 year ago

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 tracked for code freeze.

As always, we are here to help should questions come up. Thanks!

saschagrunert commented 1 year ago

@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.

parul5sahoo commented 1 year ago

@saschagrunert great then the enhancement is good to go for code freeze.

krol3 commented 1 year ago

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 dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Any doubt, reach us! Thank you!

saschagrunert commented 1 year ago

Hello @saschagrunert wave, 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 dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Any doubt, reach us! Thank you!

@Verolop do you wanna take care of this? :upside_down_face:

krol3 commented 1 year ago

Hi @saschagrunert ! Thank you for the docs PR here

krol3 commented 1 year ago

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!

marosset commented 1 year ago

/remove-label lead-opted-in /remove-label tracked/yes /label tracked/no /milestone clear

k8s-triage-robot commented 1 year ago

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

saschagrunert commented 1 year ago

/remove-lifecycle stale

saschagrunert commented 1 year ago

Not planned for graduating in v1.28.

Csanderoan commented 1 year ago

Good

k8s-triage-robot commented 7 months ago

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

puerco commented 7 months ago

/remove-lifecycle stale

k8s-triage-robot commented 4 months ago

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

saschagrunert commented 4 months ago

/remove-lifecycle stale

k8s-triage-robot commented 1 month ago

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

k8s-triage-robot commented 2 weeks ago

The Kubernetes project currently lacks enough active 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 rotten