-
Notifications
You must be signed in to change notification settings - Fork 715
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
tracking issue for kubeadm init phases #1163
Comments
fyi
|
This looks good, but I think we might want to change some of the names, and obviously move selfhosting into it's own space. |
@neolit123 could you kindly change this issues into a tracking issue /help-wanted that we can use to assign part of this effort to volunteers... I think that @ereslibre, @RA489, @Klaven can help on this effort once the PR with the first phase implementation merges; ideally who takes in charge a phase should implement related subphases as well |
@fabriziopandini |
are we going to discuss the list of phases this weeks kubeadm office hour? we need a solid list... |
I won't be able to join tomorrows kubeadm office hours :(, but count me in for any ongoing effort! |
now that we have the list of phases i will update this tracking issue tomorrow. |
@neolit123 thanks for this write-up. It is great starting point |
a couple of requests for volunteers :)
thanks. |
For starting I can take the |
@fabriziopandini |
@neolit123 I'm confident we can sync via slack/this issue BTW, I'm taking phase kubelet-start |
@fabriziopandini ok, sounds good. kubelet-start has a bit of a blocker in terms of the "stop" part as per @chuckha 's PR here: |
taking kubeconfig |
taking control-plane but really want the PR that removes placeholder docs merged... |
|
I can take this: "app/phases/upgrade needs to be moved to generic kubeadm utils (not a phase)" |
@bart0sh this was done on kubernetes/kubernetes#70346 |
@yagonobre thanks for pointing it out. won't take it then. I thought it's not assigned:
|
sorry, just updated it. |
What is the expected subphases on |
taking |
as commented there, the listed sub-phases should be just collapsed in a single phase.
|
ok, taking |
PSA, the phases need to be merged in the above order as we don't want to break e2e tests. |
@neolit123 annotateCRI IMO doesn't deserve a first level phase because it ideally should go away as soon as possible.. What about having annotateCRI as part of the upload kubelet config subphases? (Run Upload kubelet config writes the config map and annotates CRI) |
@fabriziopandini |
@RA489 hi, do you have a PR in the works for mark-control-plane? |
@neolit123 WIP |
the work here is done! the only remaining items are these, but we can track then individually: we did a pretty nice organization here and managed to tackle the list of tasks pretty well!! i will also send a shoutout to everyone for the community meeting on Thursday. |
this tracking issue goes outside of the scope for 1.13 AKA we have items for post 1.13.
this post will summarize the work that has to be done to graduate the kubeadm phases to beta (ga?).
the issue will track PRs, assignees, but also have extra actions that have to be handled.
if you wish to work on a certain item please add a comment about it.
discussion happened around this gdoc in the 17oct/2018 kubeadm office hours meeting:
https://docs.google.com/document/d/10ZQ5erWhab3GJH-CjCBT6NgvLJQygyqPkQUsx_y5snQ/edit?usp=sharing
notes:
kubeadm alpha
command for now, but moving all viable phases in the bellow list tokubeadm init phase
list of phases (ordered)
preflight
assigned: @fabriziopandini
PR: Kubeadm graduate preflight phase kubernetes#69666
NOTE: this PR also serves as an example of how a new phases should be graduated.
kubelet-start
assigned: @fabriziopandini
PR: kubeadm - graduate kubelet-start phase kubernetes#70049
currently this phase has sub-phases, the idea is to collapse them into a single phase. shuffle folders around etc. this however removes the control if the user wants to write a kubelet config, modify it and then start. so we might want to expose it eventually based on user feedback.
should be a straight forward one, move all cert sub commands as sub phases.
renew
needs to not be a sub-phase of certs, extra item bellow.same as certs,
user
however should be kept as an utility underkubeadm alpha kubeconfig user
and not being a phase.contains sub-phases for the control plane components. under api-server we also need to handle audit-policy (currently feature gated as a separate phase). there are plans to add aliases for certs here and eventually also have sub-sub-commands under each control plane component to 1) write config 2) write cert
similar to control-plane, optionally enable 1) write config 2) write cert as sub phases here eventually too.
hidden phase!
this should including uploading the kubelet config (currently under kubelet phase) and the kubeadm config. both should be exposed as sub-phases.
annotate-cri-socket should be part of
uploading the kubelet config
renamed from mark-master.
should contain all of these, but collapsed and not exposed as sub-phases.
should contain dns and proxy as subphases exposed in that order.
other action items:
this needs to handle the case where the creation of a token was skipped.
alpha phase certs renew
should be moved toalpha certs renew
(not a phase)assigned: @fabriziopandini
PR: Kubeadm alpha cmd kubernetes#70333
app/phases/upgrade needs to be moved to generic kubeadm utils (not a phase)
assigned: @yuexiao-wang
PR: kubeadm: move app/phases/upgrade to generic kubeadm utils kubernetes#70346
certs/pkiutil needs to be moved to generic kubeadm utils (not a phase)
assigned: @yuexiao-wang
PR: kubeadm: move certs/pkiutil to generic kubeadm utils kubernetes#70336
bootstraptoken/node/token.go the utils in here need to be moved outside of k/k
assigned: @neolit123
PR: kubeadm: remove TODO about moving token utils to client-go kubernetes#69979
enable-dynamic-kubelet-config should be moved outside of phases
assigned: @yagonobre
PR: Remove DynamicKubeletConfig from init and join workflow kubernetes#70849
it's feature gated.
to be decided....
the new home for this should be "k8s.io/cluster-bootstrap/token/util"
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/cluster-bootstrap/token/util/helpers.go
The text was updated successfully, but these errors were encountered: