Narrow down the usage of InitConfiguration throughout the code base

[rosti]

With the push towards v1beta1 config, a lot of the internal structures got split and narrowed in scope.
However, the InitConfiguration is still the most widely spread type in the entire kubeadm code base. This was fine with the old MasterConfiguration since it was stored as is in a config map, but currently it's inadequate for a number of reasons:

• InitConfiguration is no longer stored in the cluster as a config map.
• It's designed as kubeadm init config file structure (in order to pass parameters for the initial init process).
• It has members which are of no meaning and can be invalid if used outside of the scope of kubeadm init, thus allowing for bugs and even security vulnerabilities to plague the code base (Currently only BootstrapTokens).

The initial intent, when v1alpha3 was began, was that almost all usages of InitConfiguration outside of kubeadm init code, could be easily replaced with ClusterConfiguration. However, later in the development process of v1.12, it became obvious that ClusterConfiguration is not sufficient. This is because the structure does not contain any information about API endpoints and node specific options.

Thus, we need to define a new primarily runtime only structure, that will have the following fields and allow all kubeadm sub command independent code to operate on it:

• ClusterConfiguration
• NodeRegistrationOptions
• API endpoint(s)

/kind design
/kind cleanup

[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

[rosti]

/remove-lifecycle stale
/assign

[luxas]

@rosti I'll target this for v1.14 for you

[rosti]

/lifecycle active

[neolit123]

this seems resolved to me, please /reopen if needed.
/close

[k8s-ci-robot]

@neolit123: Closing this issue.

In response to this:

this seems resolved to me, please /reopen if needed.
/close

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.