Open neolit123 opened 5 years ago
i think the PRR process needs to be scoped more clearly and potentially be only mandatory for core functionality or opt-in for out-of-core.
This is already true; PRR is optional for out-of-tree components. We discussed this at the last PRR meeting.
Hello @neolit123 👋, 1.22 Docs release lead here.
This enhancement is marked as ‘Needs Docs’ for 1.22 release.
Can you confirm that https://github.com/kubernetes/website/pull/28010 is related to this KEP? If there are any other changes that need docs updates, please open a PR against k/website dev-1.22 branch before Fri July 9, 11:59 PM PDT (docs placeholder PR deadline). thank you
That PR is not related. We have enough time to sent the website PRs for this work. Thank you for the reminder.
Greetings @neolit123, Enhancement team shadow checking in with a few updates. Currently, we are tracking this PR for the 1.22 milestone. Are there any other PR's that are not linked that should be tracked?
A reminder about code freeze which is July 8th, 2021 11:59 PST. All implementation PR's must be code complete and merged before the deadline. Thanks for your partnership.
Hi, we merged a lot of PRs and some are still pending review. A detailed list can be seen here: https://github.com/kubernetes/kubeadm/issues/1796
Thanks for the reminder.
EDIT: corrected wrong sub comment on issue.
@jrsapi we consider the work for this "feature" in 1.22 completed (minus docs). the "feature" remains in "beta".
the full list of merged PRs is here: https://github.com/kubernetes/kubeadm/issues/1796
e2e tests are updated: https://k8s-testgrid.appspot.com/sig-cluster-lifecycle-kubeadm
docs PR is pending /lgtm
:
https://github.com/kubernetes/website/pull/28360
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
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
/milestone clear
v1beta4 candidate
Enhancement Description
Iterate on the kubeadm configuration (API) until it graduates to GA
1.15
for the 1.15 cycle we want to upgrade the config type from v1beta1 to v1beta2. Umbrella issue for tracking this work: https://github.com/kubernetes/kubeadm/issues/1439
1.22
for the 1.22 cycle we want to upgrade the config type from v1beta2 to v1beta3. Umbrella issue for tracking this work: https://github.com/kubernetes/kubeadm/issues/1796
KEP updates: