Open cofyc opened 4 years ago
/sig storage /sig scheduling
/assign
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/lifecycle fronzen
/remove-lifecycle stale @cofyc do you plan to target an implementation in 1.20?
/remove-lifecycle stale
@cofyc do you plan to target an implementation in 1.20?
yes
Thanks!
@kubernetes/sig-release can we track this?
Thanks!
@kubernetes/sig-release can we track this?
Done!
Hi @msau42 @cofyc
Enhancements Lead here, there is no alpha graduation criteria, can you please add as it's not clear what will be delivered? Also can you please clarify in the test plans whether you intend to implement all of those for alpha? or will some come later?
The graduation criteria listed for all phases seems rather vague as well, if you could provide more detail please do.
Note : Enhancements Freeze is October 6th and by that time all KEPs must have test plans & graduation criteria.
Hi @cofyc @msau42
Thanks for the PR! It clearly updates the graduation criteria! As a reminder it will need to merge by October 6th
Thanks Kirsten
Update: it merged!!! yay!
Hey there Hi @cofyc @msau42 :wave:
Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates: Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline Thursday, Nov 12th: Week 9 - Code Freeze
As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.
Thanks! Kirsten
Hello @cofyc :wave:, 1.20 Docs shadow here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20
branch in the k/website
repo.
This PR can be just a placeholder at this time and must be created before Nov 6th
Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
Hello @cofyc 👋, 1.20 Docs shadow here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against
dev-1.20
branch in thek/website
repo.This PR can be just a placeholder at this time and must be created before Nov 6th
Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
Thanks!
Hey @cofyc :wave:
The docs placeholder deadline is almost here.
Please make sure to create a placeholder PR against the dev-1.20
branch in the k/website
before the deadline.
Also, please keep in mind the important upcoming dates:
As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.
Thanks !
@eagleusb PTAL https://github.com/kubernetes/website/pull/24858
@msau42 @xing-yang can you move this KEP to the 1.21 milestone? I've submitted a PR: https://github.com/kubernetes/kubernetes/pull/96347 but may not finish the tests before the code freeze.
Sure.
Greetings @cofyc, Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:
Greetings @cofyc, Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:
- Tuesday, March 9th: Week 9 - Code Freeze
Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline
- If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo. As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them. Thanks!
@jrsapi website draft PR for 1.21 milestone: https://github.com/kubernetes/website/pull/26712
Hey @cofyc just to confirm the Enhancements team is currently tracking https://github.com/kubernetes/kubernetes/pull/96347 as the sole k/k PR for inclusion in the 1.21 release. Code Freeze is March 9th as a quick reminder. Please let me know if there are any other in-flight PR(s) we should be tracking against.
Hey @cofyc just to confirm the Enhancements team is currently tracking kubernetes/kubernetes#96347 as the sole k/k PR for inclusion in the 1.21 release. Code Freeze is March 9th as a quick reminder. Please let me know if there are any other in-flight PR(s) we should be tracking against.
https://github.com/kubernetes/kubernetes/pull/99594 API changes PR is WIP.
Greetings @cofyc,
A friendly reminder that Code freeze is 5 days away, March 9th EOD PST Any enhancements that are NOT code complete by the freeze will be removed from the milestone will require an exception to be added back. Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST. Thanks!
Hey @cofyc just to confirm the Enhancements team is currently tracking kubernetes/kubernetes#96347 as the sole k/k PR for inclusion in the 1.21 release. Code Freeze is March 9th as a quick reminder. Please let me know if there are any other in-flight PR(s) we should be tracking against.
kubernetes/kubernetes#99594 API changes PR is WIP.
It's close to the deadline and we don't have time to review API changes. API PR (https://github.com/kubernetes/kubernetes/pull/99594) is delayed to the next release cycle.
hi, @annajung the main PR (https://github.com/kubernetes/kubernetes/pull/96347) was merged. The new API field is optional. Can you add this feature back to the track list and v1.21 milestone?
Hi @cofyc, ah sorry, I misunderstood. I thought you meant the enhancement is deferred to the next cycle. will add this back to the tracking sheet. sorry for the confusion!
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
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 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 rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
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
The Kubernetes project currently lacks enough active 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 rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
/lifecycle frozen
/milestone clear
I don't yet see any documentation (the feature gate is listed as being available). Is https://kubernetes.io/docs/concepts/storage/storage-capacity/ the right place to add it?
Enhancement Description
Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
ref: https://github.com/kubernetes/kubernetes/issues/83323 ref: volume topology scheduling design proposal