should kubeadm have an assets abstraction?

[mikedanese]

From @errordeveloper on October 3, 2016 12:0

It'd help to implement dry-run mode, tarball export or other things.

Copied from original issue: kubernetes/kubernetes#33926

[mikedanese]

From @errordeveloper on October 3, 2016 12:21

We currently write files from every other function, and it's not exactly consistent how it happens and what helper funcs are used for doing it. However, in some cases this provides us with an ability to have more user-friendly error message, which is something we will need to ensure assets abstraction would be capable of. We shouldn't have to document files we write, if we have dry-run mode, or good logging etc. We could permit some files, e.g. PKI assets or static pods to exists on disk before kubeadm init, which would be convenient way of not having to implement too many extra flags...

[mikedanese]

From @errordeveloper on October 3, 2016 12:23

We could add validation of existing files could also come into this, and even warn about deprecated files.

[mikedanese]

From @luxas on October 25, 2016 20:35

@errordeveloper Can I close this?
It doesn't seem like we're going that way...

[luxas]

Closing, @errordeveloper comment if you strongly disagree...