# Has anyone tried creating one node cluster where master node and worker node remains in the same node

**URL:** https://discuss.kubernetes.io/t/has-anyone-tried-creating-one-node-cluster-where-master-node-and-worker-node-remains-in-the-same-node/13411
**Category:** General Discussions
**Created:** [October 23, 2020, 5:31pm UTC](https://discuss.kubernetes.io/t/has-anyone-tried-creating-one-node-cluster-where-master-node-and-worker-node-remains-in-the-same-node/13411 "2020-10-23T17:31:57Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![tharasavio](https://avatars.discourse-cdn.com/v4/letter/t/898d66/32.png) [@tharasavio](https://discuss.kubernetes.io/u/tharasavio)
#### Post date: [October 23, 2020, 5:31pm UTC](https://discuss.kubernetes.io/t/has-anyone-tried-creating-one-node-cluster-where-master-node-and-worker-node-remains-in-the-same-node/13411/1 "2020-10-23T17:31:57Z")

</div>

[root@kubernetes manifests]# kubeadm join 10.128.0.17:6443 --token xobxxxxxh56.loyr72nys4cf0l2e --discovery-token-ca-cert-hash sha256:6646e90ef97575b65f162cd5b044efa1ce6c96f3a8e079f2bdc5055603e8ebd3  
[preflight] Running pre-flight checks  
error execution phase preflight: [preflight] Some fatal errors occurred:  
[ERROR Port-10250]: Port 10250 is in use  
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`  
To see the stack trace of this error execute with --v=5 or higher  
[root@kubernetes manifests]#

---

<div class="post-metadata">

### Author: ![ambig](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/ambig/32/6102_2.png) [@ambig](https://discuss.kubernetes.io/u/ambig)
#### Post date: [October 24, 2020, 9:20pm UTC](https://discuss.kubernetes.io/t/has-anyone-tried-creating-one-node-cluster-where-master-node-and-worker-node-remains-in-the-same-node/13411/2 "2020-10-24T21:20:53Z")

</div>

With rancher rke tool you can create a one node cluster with no issues.

---

<div class="post-metadata">

### Author: ![mrbobbytables](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mrbobbytables/32/7_2.png) [@mrbobbytables](https://discuss.kubernetes.io/u/mrbobbytables)
#### Post date: [October 25, 2020, 12:25am UTC](https://discuss.kubernetes.io/t/has-anyone-tried-creating-one-node-cluster-where-master-node-and-worker-node-remains-in-the-same-node/13411/3 "2020-10-25T00:25:30Z")

</div>

A control plane node is already essentially a worker node. It just has a [taint](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) on it that prevents scheduling of workloads by default. Remove the `NoSchedule` taint and workloads should be schedulable.