kubeadm: graduate the kubeadm configuration

[neolit123]

Enhancement Description

• One-line enhancement description (can be used as a release note):

Iterate on the kubeadm configuration (API) until it graduates to GA

• Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR) https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/kubeadm/970-kubeadm-config
• Primary contact (assignee): @neolit123
• Responsible SIGs: Cluster-Lifecycle
• Enhancement target (which target equals to which milestone):
  • Alpha release target PAST
  • Beta release target 1.22 (v1beta3)
  • Stable release target TODO

---

1.15

for the 1.15 cycle we want to upgrade the config type from v1beta1 to v1beta2.
Umbrella issue for tracking this work:
kubernetes/kubeadm#1439

---

1.22

for the 1.22 cycle we want to upgrade the config type from v1beta2 to v1beta3.
Umbrella issue for tracking this work:
kubernetes/kubeadm#1796

KEP updates:

• sig-cluster-lifecycle: update the kubeadm config KEP for 1.22 #2627

[k8s-ci-robot]

@neolit123: There are no sig labels on this issue. Please add a sig label.

A sig label can be added by either:

1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
   e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

2. specifying the label manually: /sig <group-name>
   e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

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.

[rosti]

/assign

[rosti]

Thanks for creating the issue @neolit123 !