This is precisely what we do on our cluster as well for the node-level daemons - kubelet and kube-proxy. We use fleet to schedule the HA API server. You cannot

This is precisely what we do on our cluster as well for the node-level daemons - kubelet and kube-proxy. We use fleet to schedule the HA API server. You cannot use the Kubelet to schedule this, because you need an API server to schedule cluster-wide pods. The only solution I can see is to have a config that launches a special 'master' node that runs the API server, but this is uncompelling to me. I'd rather have every single node be identical, and get the API server to pop up somewhere in the cluster using a master election process - which is precisely what fleet does.