<p>I need advice for k3s architecture. I would like to create small cluster with one master and 3 agent nodes, but in my opinion master node should be in separate server so it have resources only for itself. But I can't see in k3s documentation <code>--disable-agent</code> anymore, and I read that it is buggy so they removed it, so I am wondering how can I have only server setup on one node and is it a good practice at all?</p>

Most31
<p>Having master node separated is a <a href="https://www.suse.com/c/kubernetes-cluster-vs-master-node/#:%7E:text=A%20master%20node%20is%20a,resembles%20a%20cluster%20in%20Kubernetes.&amp;text=All%20external%20communication%20to%20the,controllers%20for%20the%20running%20cluster." rel="nofollow noreferrer">typical</a> architecture that Kubernetes utilizes since it runs all the vital components (API Server, Controller manager, etcd and scheduler) necessary to manage your cluster.  So it a good idea to have it running on another node (In K8s it is the only way although it is possible to schedule pods on master node if you untaint it)</p>
<p>Here`s a good <a href="https://levelup.gitconnected.com/kubernetes-cluster-with-k3s-and-multipass-7532361affa3" rel="nofollow noreferrer">article</a> about having multinode k3 cluster that relates to your desire state.</p>
<p>Alternative way would be to a solution suggested in this <a href="https://github.com/rancher/k3s/issues/978" rel="nofollow noreferrer">github</a> issue related to <code>--disable-agent</code> and taint the master with <code>NoExecute</code> key.</p>
