self hosted k8s

k8s in k8s, k8s apiserver, control manager, schduler are running as pods in k8s. Apiserver are runing as deamonsets in masternode only; kubelet and kubeproxy are daemonset in everynode. control manager and schduler are deployment in namespace kube-system

 (DaemonSets manage groups of replicated Pods. However, DaemonSets attempt to adhere to a one-Pod-per-node model, either across the entire cluster or a subset of nodes. Daemonset will not run more than one replica per node. Another advantage of using Daemonset is, If you add a node to the cluster then Daemonset will automatically spawn pod on that node, which deployment will not do.

DaemonSets are useful for deploying ongoing background tasks that you need to run on all or certain nodes, and which do not require user intervention. Examples of such tasks include storage daemons like ceph, log collection daemons like fluentd, and node monitoring daemons like collectd
) 

For the very first time to setup k8s , use bootkube , it give temporar control panel which enable inject kube apiserver, control manger etc as k8s node. 

 reason: k8s can manage itself ; easy debug; easy secret roration;  easy the process of upgrading.