Open pacoxu opened 3 years ago
/sig auth /sig node /kind feature /area kubelet-api /priority important-longterm
See also:
@pacoxu: The label(s) area/kubelet-api
cannot be applied, because the repository doesn't have them.
/assign I will start to work on the KEP.
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 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 still have no enough time to work on this.
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
/lifecycle frozen
/assign @vinayakankugoyal
@tallclair - I started a KEP for this one. Would you be able to take a look? https://github.com/kubernetes/enhancements/pull/4760
In a sense this is the KEP; #4760 is a PR to add the details.
Ok thanks 🙏
/milestone v1.32 /label lead-opted-in
/stage alpha
Hello @vinayakankugoyal @pacoxu 👋, v1.32 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
.For this KEP, we would need to update the following:
The status of this enhancement is marked as at risk for enhancement freeze
. Please keep the issue description up-to-date with appropriate stages as well. Thank you!
If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!
@dipesh-rawat
Here's where this enhancement currently stands:
implementable
for latest-milestone: v1.32
.Please let me know if I missed something. Thanks!
Hello @vinayakankugoyal 👋, v1.32 Enhancements team here,
Now that PR https://github.com/kubernetes/enhancements/pull/4760 has been merged, all the KEP requirements are in place and merged into k/enhancements.
Before the enhancement freeze, it would be appreciated if following nits could be addressed:
Update issue description to add direct link to KEP README.md.
Aside from the minor nit mentioned above, this enhancement is all good for the upcoming enhancements freeze. 🚀
The status of this enhancement is now marked as tracked for enhancement freeze
. Please keep the issue description up-to-date with appropriate stages as well. Thank you!
@dipesh-rawat I don't seem to have permissions to edit the issue description. @pacoxu could you do it?
@dipesh-rawat I don't seem to have permissions to edit the issue description. @pacoxu could you do it?
Updated.
Enhancement Description
k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/4760k/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.