add UpgradeConfiguration/ResetConfiguration API types

[neolit123]

kubeadm currently has some matching configuration formats for its main commands.

join - JoinConfiguration
init - InitConfiguration
upgrade - none
reset - none

we should eventually provide API types for all main commands to avoid flags.
note this was not discussed as part of v1beta3, so it can happen in a future API version.

---

these are added in v1beta4

upgrade

upgrade does not have a config, forcing users to rely on flags only and forcing us as maintainers to have some flags unique to "upgrade" only.

we should add a scoped UpgradeConfiguration structure that can hold a number of relevant options to upgrade.
--config for upgrade should accept this configuration and not ClusterConfiguration | InitConfiguration...

maybe CC too:
#1681

• kubeadm: implementation of UpgradeConfiguration API types kubernetes#114062
• kubeadm: implementation of UpgradeConfiguration API types kubernetes#123068

---

reset

this makes sense for consistency with respect to skipPhases. one other option is --force.
overall the structure for reset would be very minimal since it does not have a lot of options.

• kubeadm: implementation of ResetConfiguration API types kubernetes#113583

[neolit123]

we discussed with @fabriziopandini during the kubeadm office hours today that we should delay the addition of these new structures until we have a better understanding of nodespecific configuration and the kubeadm roadmap as a whole.
#2367

[wangyysde]

/cc @wangyysde

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[chendave]

/remove-lifecycle stale

@neolit123 is the time to pick this up? I saw the KEP is closed with no progress yet.

[neolit123]

we should likely book another kubeadm office hours to discuss this. but if you'd like you can also draft a google doc proposal about it following the kep template on which we can comment.

[chendave]

sure, I am going to do more investigation on this and make sure I understand the whole pic before sending the google doc.

/assgin

[chendave]

/assign

[chendave]

sent the doc to the mailing list, paste the link here as well: https://docs.google.com/document/d/1R4zLtgDadNM8_N2VzS0DI2mADcYmkyJ3L7lJVpbyZsA

[chendave]

@neolit123 pls help to review at your convenience, thanks! :)

[neolit123]

thanks @chendave . i did an initial pass on the doc