mirror of
https://github.com/kubernetes-sigs/node-feature-discovery.git
synced 2025-03-18 22:33:09 +00:00
30 lines
1 KiB
Markdown
30 lines
1 KiB
Markdown
|
---
|
||
|
|
title: "NFD-Master"
|
||
|
|
layout: default
|
||
|
|
sort: 3
|
||
|
|
---
|
||
|
|
|
||
|
|
# NFD-Master
|
||
|
|
{: .no_toc}
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
NFD-Master runs as a deployment (with a replica count of 1), by default
|
||
|
|
it prefers running on the cluster's master nodes but will run on worker
|
||
|
|
nodes if no master nodes are found.
|
||
|
|
|
||
|
|
For High Availability, you should simply increase the replica count of
|
||
|
|
the deployment object. You should also look into adding
|
||
|
|
[inter-pod](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity)
|
||
|
|
affinity to prevent masters from running on the same node.
|
||
|
|
However note that inter-pod affinity is costly and is not recommended
|
||
|
|
in bigger clusters.
|
||
|
|
|
||
|
|
NFD-Master listens for connections from nfd-worker(s) and connects to the
|
||
|
|
Kubernetes API server to add node labels advertised by them.
|
||
|
|
|
||
|
|
If you have RBAC authorization enabled (as is the default e.g. with clusters
|
||
|
|
initialized with kubeadm) you need to configure the appropriate ClusterRoles,
|
||
|
|
ClusterRoleBindings and a ServiceAccount in order for NFD to create node
|
||
|
|
labels. The provided template will configure these for you.
|