kubeadm-phases

kubeadm-phases

potential list and order of phases for init:
- preflight
- kubelet-write-config (kubelet)
- kubelet-start (kubelet)
- certs
- kubeconfig
- controlplane
- etcd
- upload-config
- kubelet-config-map (kubelet)
- mark-master
- patch-node
- kubelet-enable-dynamic-config
- node-bootstrap-token (bootstraptoken)
- cluster-info (bootstraptoken)
- addon-dns (addons)
- addon-proxy (addons)
- self-hosting (needs to be removed from here?)
- print-join-command

notes:
- kubelet-write-config: do we want this as a separate phase or part of kubelet-start?
- kubelet-start and kubelet-config-map need to be separate phases.
- kubelet-enable-dynamic-config: this one is a bit of a stretch and it's gated already?
- potential split: addon-dns and addon-proxy from addons.
- potential split: node-tls-bootstrap and cluster-info from bootstraptoken.

possibly best to split the kubelet-sub-phases in separate packages under phases/kubelet.

packages/files that belong to management and not in phases:
- bootstraptoken/node/token.go (this was planned to be moved for a while)
- certs/pkiutil
- certs/renewal
- certs/upgrade (not a phase)

at first sight in order to give the same UX today existing in alpha phases the list of phases needs to be exploded into sub phases
e.g. certs --> certs/ca, certs/apiserver ....

viceversa, some phases should be grouped:
e.g. addons (parent phase) should group dns and proxy

self hosting should go out of the way

+1 on the points.

moved to a tracking issue + google doc:
kubernetes/kubeadm#1163