Skip to content
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

Open
neolit123 opened this issue Apr 17, 2019 · 15 comments

Comments

@neolit123
Copy link
Member

commented Apr 17, 2019

Enhancement Description

  • One-line enhancement description (can be used as a release note):

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


cc @fabriziopandini

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

commented Apr 17, 2019

@neolit123: There are no sig labels on this issue. Please add a sig label.

A sig label can be added by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

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.

@neolit123 neolit123 added this to the v1.15 milestone Apr 17, 2019

@rosti rosti referenced this issue Apr 17, 2019
4 of 4 tasks complete
@rosti

This comment has been minimized.

Copy link
Member

commented Apr 17, 2019

/assign

@rosti

This comment has been minimized.

Copy link
Member

commented Apr 17, 2019

Thanks for creating the issue @neolit123 !

@kacole2 kacole2 added the tracked/yes label Apr 17, 2019

@neolit123 neolit123 changed the title kubeadm: upgrade the configuration to v1beta2 kubeadm: graduate the kubeadm configuration to GA Apr 18, 2019

@neolit123 neolit123 changed the title kubeadm: graduate the kubeadm configuration to GA kubeadm: graduate the kubeadm configuration Apr 18, 2019

@neolit123

This comment has been minimized.

Copy link
Member Author

commented Apr 18, 2019

@rosti
updated the description and title.

@craiglpeters

This comment has been minimized.

Copy link
Contributor

commented Apr 29, 2019

@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.

@neolit123

This comment has been minimized.

@christianh814

This comment has been minimized.

Copy link

commented May 13, 2019

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!

@neolit123

This comment has been minimized.

Copy link
Member Author

commented May 13, 2019

hi @christianh814
this work will require minor updates on already existing links to the godocs documentation of the kubeadm API. we are going to have the PRs up before the 31st.

thanks for the heads up.

@craiglpeters

This comment has been minimized.

Copy link
Contributor

commented May 29, 2019

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!

@makoscafee

This comment has been minimized.

Copy link
Member

commented May 29, 2019

Hi, @neolit123 I am docs Lead.
Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must have placeholder docs PRs open.
Just friendly following up on this. Thanks

@rosti

This comment has been minimized.

Copy link
Member

commented May 29, 2019

Thanks for the reminder @makoscafee and @craiglpeters !

@rosti

This comment has been minimized.

@craiglpeters

This comment has been minimized.

Copy link
Contributor

commented May 30, 2019

@rosti great to see the PRs have merged :)

@kacole2

This comment has been minimized.

Copy link
Member

commented Jul 8, 2019

Hi @rosti @neolit123 , I'm the 1.16 Enhancement Lead. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.6 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

@neolit123

This comment has been minimized.

Copy link
Member Author

commented Jul 8, 2019

hi @kacole2. we decided that this feature will not see any changes with the release of 1.16.
but we may still file a number of related WIP/POC KEPs.

@neolit123 neolit123 removed the tracked/yes label Jul 8, 2019

@kacole2 kacole2 removed this from the v1.15 milestone Jul 9, 2019

@kacole2 kacole2 added the tracked/no label Jul 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.