-
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: Update the config KEP #969
Conversation
As per discussion in the kubeadm office hours meeting from yesterday, this KEP is going to be merged with the v1beta1 KEP into a single kubeadm config KEP. |
5c35866
to
07b417c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updates on some structure, but looking better.
@@ -1,6 +1,6 @@ | |||
--- | |||
kep-number: 23 | |||
title: Kubeadm config file graduation to v1beta1 | |||
title: Kubeadm config file graduation to v1beta2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would just say Kubeadm config file format (v1beta2)
|
||
## Proposal | ||
|
||
### Decoupling the kubeadm types from other ComponentConfig types | ||
|
||
The `v1alpha2` kubeadm config types currently embeds the ComponentConfig for | ||
The `v1alpha2` kubeadm config types embeds the ComponentConfig for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should move around the subheadings so they are grouped by version
e.g.
- v1beta1
- Decoupling the kubeadm types from other ComponentConfig
- v1beta2
- (Details ...)
This way as you read it you get the order of when the changes happened.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rosti
Looks great!
Only few minors, but nothing blocking
+1 on grouping changes by version as suggested by Tim
@@ -179,7 +181,7 @@ be adapted as described by following schemas: | |||
- [kubeadm upgrade node](0023-kubeadm-upgrade-node.png) | |||
- [kubeadm reset](0023-kubeadm-reset.png) | |||
|
|||
### Use substructures instead of the current "single flat object" | |||
### Use substructures instead of the "single flat object" in v1alpha2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can remove in v1alpha2 from the title, it is detailed in the next sentence
format. One notable such feature, that was introduced after the release of `v1beta1` is the | ||
[Certificates copy for join --control-plane KEP](./20190122-Certificates-copy-for-kubeadm-join--control-plane.md). | ||
|
||
In addition to that, some existing kubeadm feature may not be exposing some settings through the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will simplify into
" In addition to that, some new settings are added to the config format for existing features, improving the original design and addressing user feedbacks.
These includes..."
@@ -240,5 +268,4 @@ the SIG. This comes with a real opportunity cost. | |||
|
|||
## Alternatives | |||
|
|||
Graduate kubeadm GA with the current kubeadm config and eventually change afterward | |||
(respecting GA contract rules). | |||
TBD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can remove the paragraph
07b417c
to
cc90a5f
Compare
Thanks for the feedback @timothysc and @fabriziopandini ! |
Signed-off-by: Rostislav M. Georgiev <[email protected]>
cc90a5f
to
8581a9b
Compare
/approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, rosti, timothysc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Rename and update a bit the KEP for kubeadm config. Most importantly:
/assign @fabriziopandini @timothysc @neolit123 @luxas
/cc @kad @detiber @yagonobre @ereslibre