Open saschagrunert opened 2 years ago
Is this also relevant to SIG Security?
Yes I have my 👀 on this :) /sig security
Waiting a bit more for alignment on https://github.com/kubernetes/enhancements/pull/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 alpha
for 1.24 (correct me, if otherwise)
Here’s where this enhancement currently stands:
implementable
for this releaseLooks like for this one, we would require updating the existing KEP proposal to reflect the following:
kep.yaml
to have an implementable
status.README.md
file to add a Test plan section.alpha
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! 🙂
With #3191 merged, I've updated the status to tracked
for enhancement freeze. Thanks!
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!!
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:
Docs PR got merged, we’re good to go.
/milestone clear
Also relevant to https://github.com/kubernetes/release/issues/913
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:
implementable
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. 🙂
@Priyankasaggu11929 the KEP update merged, I hope we're now good to go. :slightly_smiling_face:
Thanks @saschagrunert, the KEP was marked as tracked
before Enhancements Freeze. We’re all good on this one.
Thank you so much! 🙂
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
.
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!
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.
Thanks for the prompt update, @saschagrunert. 🙂
/milestone clear
/label tracked/yes /remove-label tracked/no /milestone v1.26
@rhockenbury: Those labels are not set on the issue: tracked/no
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:
implementable
for latest-milestone: 1.26
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!
Feature blog post placeholder: https://github.com/kubernetes/website/pull/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 tracked
for code freeze.
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 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!
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 thek/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:
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 /remove-label tracked/yes /label tracked/no /milestone clear
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Not planned for graduating in v1.28.
Good
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Enhancement Description
k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/3061k/k
) update PR(s): https://github.com/kubernetes/release/issues/2383k/website
) update PR(s): https://github.com/kubernetes/website/pull/31610 https://github.com/kubernetes/website/pull/32184k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/3323 https://github.com/kubernetes/enhancements/pull/3451k/k
) update PR(s): https://github.com/kubernetes/release/issues/2586k/website
) update(s): https://github.com/kubernetes/website/issues/35341/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