Review kubeadm package layout

[fabriziopandini]

as per comment kubernetes/kubernetes#70346 (comment) and kubernetes/kubernetes#70333 (comment)

If there is consensus, kubeadm package layout should be aligned with other Kubernetes commands.

• cmd/kubeadm should be used only for the UX
• pkg/kubeadm should be introduces and host apis and all the other kubeadm packages

Additionally IMO:

1. phases (an UX concept) should not be reflected in the pkg/kubeadm sub tree
2. existing weirdness should be fixed (e.g. update inside /phases and vice-versa preflight outside /phases)
3. Everything code for UX should be removed from pkg/kubeadm (e.g. printf/kubeadm output)
4. util is abused/too crowded. it should be simplified.
5. documentation about what is the scope of each package should be added
6. expose the kubeadm backend as vendorable API (xref)

[yuexiao-wang]

Do it have a decision ?

[yuexiao-wang]

It is a similar issue about test utilites. #1257

[fabriziopandini]

Not yet.
I think that this will be discussed in v1.14 planning (this week or the week after kubeconfig)

It is a similar issue about test utilites. #1257

Similar, but not overlapping

[yuexiao-wang]

Got it. kubernetes/kubernetes#71702, which fixes for #1257, will be hold and wait for v1.14 planning.

[MalloZup]

@fabriziopandini I would like to help on this. We might split this issue in small actionables issues. If you want we can talk about it in irc or here as you wish.

[fabriziopandini]

@luxas considering that this cycle seems there are people willing to help, it will be great to hear what do you think about this idea...

Cleaning up some tech debt and getting in better shape for enabling kubeadm vendoring in future are the main reason behind this.
What about trying to combine a meeting for a quick brainstorming on this topic?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[astrieanna]

/remove-help

because it isn't clear from the comments here if there is consensus or exactly what that consensus is.

[fabriziopandini]

/close
in favor of #2316; before talking about implementation detail, we should discuss the use cases we want to address with the new package layout

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

/close
in favor of #2316

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.