Open knight42 opened 2 years ago
/sig node /sig api-machinery /sig cli
/milestone v1.25
@knight42: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.
/milestone v1.25
Hello @knight42 π, 1.25 Enhancements team here.
Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.
For note, This enhancement is targeting for stage alpha
for 1.25 (correct me, if otherwise)
Here's where this enhancement currently stands:
implementable
Looks like for this one, we would need to get the open KEP PR https://github.com/kubernetes/enhancements/pull/3289 merged by Enhancements Freeze:
For note, the status of this enhancement is marked as at risk
. Thanks for keeping the issue description up-to-date!
With KEP PR #3289 merged, this enhancement is ready for the upcoming enhancements freeze.
For note, the status is not marked as tracked
in the enhancements tracking sheet. Thank you!
@Priyankasaggu11929 I think the following could be marked as done now:
Hi @knight42, Enhancements team here again π
Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022.
Please ensure that the following items are completed before the code-freeze:
Currently, the status of the enhancement is marked as at-risk
Thanks :)
Hey @knight42 reaching out again as we approach Code Freeze at 01:00 UTC on this Wednesday i.e 3rd August 2022.
Try to get this PR https://github.com/kubernetes/kubernetes/pull/110794 merged before the code-freeze :)
The status of the enhancement is still marked as at-risk
@Atharva-Shinde Hi, I think we need to move it to next release v1.26. Thanks!
Thanks for the update @knight42.
/milestone clear
/milestone v1.26 /label lead-opted-in (I'm doing this on behalf of @ruiwen-zhao / SIG-node)
/stage alpha /label tracked/yes /remove-label tracked/no
Hey @knight42 π, 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 alpha
for 1.26
Here's where this enhancement currently stands:
implementable
For this KEP, we would need to:
The status of this enhancement is marked as at risk
. Please keep the issue description up-to-date with appropriate stages as well.
Thank you :)
/milestone v1.26 /label lead-opted-in
(this is a carry over from prior release)
Hello @knight42 π, just a quick check-in again, as we approach the 1.26 Enhancements freeze.
Please plan to get the action items mentioned in my comment above done before Enhancements freeze on 18:00 PDT on Thursday 6th October 2022 i.e tomorrow
For note, the current status of the enhancement is marked at-risk
:)
Hello π, 1.26 Enhancements Lead here.
Unfortunately, this enhancement did not meet requirements for enhancements freeze.
If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!
/milestone clear /label tracked/no /remove-label tracked/yes /remove-label lead-opted-in
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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
/lifecycle rotten
/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
I am available now and will pick it up recently.
@knight42 are you still available? Should we track this KEP for 1.28?
@knight42 are you still available? Should we track this KEP for 1.28?
Yes please, I think I could make it.
/milestone v1.28
@knight42 can you please send update to kep.yaml to include this in 1.28?
@knight42 can you please send update to kep.yaml to include this in 1.29?
@knight42 can you please send update to kep.yaml to include this in 1.29?
Hi @SergeyKanzhelev, I have filed https://github.com/kubernetes/enhancements/pull/4221 to update milestones.
Hi @knight42, is this targeting 1.29? If it is, can you please make sure the lead-opted-in
label is set on this issue so that it is tracked in the 1.29 enhancement project board? Thanks!
Hi @knight42, is this targeting 1.29?
Yeah I hope so, thanks for reminding!
/label lead-opted-in
@knight42: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads]
Hi @knight42 π, 1.29 Enhancements Lead here.
Unfortunately, this enhancement did not meet requirements for v1.29 enhancements freeze. Feel free to file an exception to add this back to the release tracking process. Thanks!
Hello π 1.30 Enhancements Lead here,
I'm closing milestone 1.28 now,
If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in
label is set so it can get added to the tracking board and finally add /milestone v1.30
. Thanks!
/milestone clear
hi @knight42 , are you still working on this? or finding a new owner of this KEP?
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
/remove-lifecycle rotten
/milestone v1.32
/label lead-opted-in
Moving this to approved for release after approval from @mrunalp
I'm the sig-node KEP wrangler for this. From this, I see that the KEP has merged and @knight42 has resurrected the implementation PR.
Please let us know if you will not be able to get this implementation in. And also do not forget about documentation for this feature.
Hello @knight42 π, Enhancements team here.
Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.
This enhancement is targeting for stage alpha
for v1.32 (correct me, if otherwise)
Hereβs where this enhancement currently stands:
implementable
for latest-milestone: v1.32
. KEPs targeting stable
will need to be marked as implemented
after code PRs are merged and the feature gates are removed.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 for enhancement freeze
. Please keep the issue description up-to-date with appropriate stages as well. Thank you!
@jenshu Thanks, I have updated the issue description.
Hello @knight42 , ππΌ this is Edith from the v1.32 Communications Team!
Weβd love for you to consider writing a feature blog about your enhancement! β Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.
To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog, see the blog contribution guidelines.
Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.
Hi @knight42 :wave:, I'm James Spurin, a 1.32 Docs Shadow. Great to meet you.
Does this enhancement work planned for 1.32 require any new docs or modifications to the existing docs?
If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.
Also, take a look at Documenting for a release to familiarise with the docs requirement for the release.
Thank you!
Hi @knight42,
Thanks for tagging me in the PR and referencing the WIP documentation. Appreciated.
I see that this is in progress under PR #48405 and that there are some pending actions based on feedback from @sftim.
Could you please take a look?
At the moment I've marked the documentation as in Draft for the time being on the overall enhancements tracking board.
Hey again @knight42 π, v1.32 Enhancements team here.
Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024.
Here's where this enhancement currently stands:
approved
and lgtm
labels applied) by the code freeze deadline. This includes tests.For this enhancement, it looks like the following PRs need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):
If you anticipate missing code freeze, you can file an exception request in advance.
Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!
Hello, @knight42 ! π π
This is a reminder to author your feature blog post!
To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines.
Please feel free to reach out if you have any questions!
Thank you very much! Edith from the v1.32 Shadow Communications Team
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.