# Specify fault domain

**URL:** <https://discuss.kubernetes.io/t/specify-fault-domain/16315>\
**Category:** microk8s\
**Created:** [June 10, 2021, 7:33pm UTC](https://discuss.kubernetes.io/t/specify-fault-domain/16315 "2021-06-10T19:33:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mashbrno](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mashbrno/32/7900_2.png) [@mashbrno](https://discuss.kubernetes.io/u/mashbrno)\
**Post date:** [June 10, 2021, 7:33pm UTC](https://discuss.kubernetes.io/t/specify-fault-domain/16315/1 "2021-06-10T19:33:23Z")

</div>

As there is a hard limit of 110 pods per node, I need to run multiple cluster nodes on the same vSphere host. Is there an option to define a fault domain that especially active datastores should not be located on the same bare metal?

Other option would be to separate master and worker nodes which is best practice in other distributions anyway.

---

<div class="post-metadata">

**Author:** ![protosam](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/protosam/32/7732_2.png) [@protosam](https://discuss.kubernetes.io/u/protosam)\
**Post date:** [June 10, 2021, 7:48pm UTC](https://discuss.kubernetes.io/t/specify-fault-domain/16315/2 "2021-06-10T19:48:03Z")

</div>

The max pods is controlled by the kubelet. Why not just update the max pods per node?

Looking at microk8s documentation, the `snap.microk8s.daemon-kubelet` section in [this](https://microk8s.io/docs/configuring-services) doc explains where the arguments need to be.

It refers you to the [kubelet documentation](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/). There is a `max-pods` flag mentioned on the page.