This message was deleted.

Hi, I think you can scale the new node to the cluster and configure it like tags and default disk as per here.

ok so these labels are on the nodes correct? - I see no longhorn labels on my current nodes?

You have to add the labels, otherwise Longhorn will use all available nodes, at least during initial deployment.

yes but I would exspect labels to be there on current installation - installed by HELM and I see it is running - so just don’t understand no labels are present now?

The helm install is not supposed to add any labels. In its default configuration, helm will create a default disk on all nodes in the root file system. If that is not the behavior you want, you can create nodes with labels that instruct helm to do something different as described in the document @narrow-egg-98197 linked. Additionally, the Longhorn DaemonSets do not deploy to Kubernetes master nodes by default, as they can't tolerate the

<http://node-role.kubernetes.io/master|node-role.kubernetes.io/master>: NoSchedule

taint. To change this behavior, see https://longhorn.io/docs/1.4.2/advanced-resources/deploy/taint-toleration/#setting-up-taints-and-tolerations-during-installing-longhorn.

Thank you, I will dig more into it 🙂