Closed alculquicondor closed 2 years ago
We are graduating to beta for 1.20. I'll prepare a KEP update soon.
Thanks @alculquicondor !
When you update the KEP can you also please fix the target and KEP link in the description?
/milestone v1.20
/retitle Add a configurable default constraint to PodTopologySpread
Hey @alculquicondor -- 1.20 Enhancements Shadow here 👋
I see that a PR with changes to a KEP is still in flight. Just a friendly reminder that the Enhancements Freeze deadline is October 6th. Otherwise, an exception will need to be submitted.
Appreciate the work!
Regards, Jeremy
Hey @alculquicondor 👋
Just a reminder that the changes to this KEP will need to be in by the October 6th Enhancements freeze deadline if we want to graduate to beta in 1.20.
Regards, Jeremy
graduation to Beta was just approved, thanks :)
Hi @alculquicondor ,
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.
Best, Jeremy
Hello @alculquicondor , 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 the 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!
Hi @alculquicondor
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.
All tasks for 1.20 are completed
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
/lifecycle frozen
Enhancement issues opened in kubernetes/enhancements
should never be marked as frozen.
Enhancement Owners can ensure that enhancements stay fresh by consistently updating their states across release cycles.
/remove-lifecycle frozen
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
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
/help for graduation to GA.
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:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
/reopen
I'm gonna graduate this feature to GA in 1.24
@alculquicondor: Reopened this issue.
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:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
/reopen
/help
@alculquicondor: Reopened this issue.
/remove-lifecycle rotten
/assign @gavinfish
/remove help
/remove-help
DefaultPodTopologySpread
is GA in https://github.com/kubernetes/kubernetes/pull/108278 already. Should we updated the description and whether any works remaining? @alculquicondor
You need to update the state of the feature in the website https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#internal-default-constraints
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
Thanks @kerthcet for graduating this feature!
/close
@alculquicondor: Closing this issue.
Enhancement Description