Setup bootstrap-tokens configuration about kubernetes-in-kubernetes HOT 2 OPEN

In the original code they are generated not with manifests, but rather with programmatic way: https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/phases/bootstraptoken/node/tlsbootstrap.go

It will be very difficult to support updates to tokens as there are no source manifests. Probably it is wiser to leave it as is and use kubeadm. In any case you will need it for generating join tokens...
I'd like to discuss different approach, because we CAN do what you want, but I don't understand the rewrite benefits

from kubernetes-in-kubernetes.

Hi, bootstrap-token phase perform the two things:

• Applying cluster-info configmap and RBAC manifests into cluster
• Generating temporary token: eg executing kubeadm token create (this creates kube-system/bootstrap-token-xxxxxx secret and records a string .data.jws-kubeconfig-xxxxxx into kube-public/cluster-info configmap)

Actually we don't need to generate the token at this time, but the rest manifests are quite static and not changing during the time thus, we can simple template them using Helm. I wanted to replace this part cause we have to apply these manifests every time we update the release, and every time we have a new token generated. That's not a big problem as the temporary tokens are removing by controller-manager after 24 hours, but when you updating your release quite often they might be annoying.

The main reason why I wanted to get rid of any programmatic kubeadm logic is simplicity to inspecting of all applyable manifests.
Ideally the simple rendering of Helm chart using helm template command, should return self-sufficient set of YAML-manifests necessary to set up working Kubernetes control-plane. However, I want to leave support with kubeadm because many tools rely on it. This issue was created for that reason.

from kubernetes-in-kubernetes.