-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubeadm: graduate the kubeadm configuration #970
Comments
@neolit123: There are no sig labels on this issue. Please add a sig label. A sig label can be added by either:
Note: Method 1 will trigger an email to the group. See the group list. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
Thanks for creating the issue @neolit123 ! |
@rosti |
@fabriziopandini and @luxas, Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be in an "Implementable" state with proper test plans and graduation criteria. Please submit any PRs needed to make this KEP adhere to inclusion criteria. If this will slip from the 1.15 milestone, please let us know so we can make appropriate tracking changes. |
Hey @neolit123 and @rosti I'm the v1.15 docs shadow. Does this enhancement require any new docs (or modifications)? Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Friday, May 31st. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions! |
hi @christianh814 thanks for the heads up. |
Hi @rosti. Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open. Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone. If you know this will slip, please reply back and let us know. Thanks! |
Hi, @neolit123 I am docs Lead. |
Thanks for the reminder @makoscafee and @craiglpeters ! |
Greetings @neolit123!
Thanks! |
@jrsapi hello, 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. |
Thanks for the link to the comment. I'll move the to "Tracked" in the Enhancement spreadsheet. |
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 kubernetes/website#28010 is related to this KEP? |
That PR is not related. We have enough time to sent the website PRs for
this work. Thank you for the reminder.
|
Greetings @neolit123, 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:
kubernetes/kubeadm#1796
Thanks for the reminder.
EDIT: corrected wrong sub comment on issue.
|
@jrsapi the full list of merged PRs is here: e2e tests are updated: docs PR is pending |
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:
You can:
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:
You can:
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/milestone clear |
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:
kubernetes/kubeadm#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:
kubernetes/kubeadm#1796
KEP updates:
The text was updated successfully, but these errors were encountered: