node-feature-discovery
node-feature-discovery copied to clipboard
kubernetes-sigs
Node feature discovery for Kubernetes
**What would you like to be added**: Re-organize the *Get started* major section of documentation. Probably spitting it into multiple separate major sections. E.g. something like - get-started/ - introduction...
**What would you like to be added**: Spun out from https://github.com/kubernetes-sigs/node-feature-discovery/pull/640#issuecomment-968687743: > Other Helm apps may also want to add NFD as a dependency. Actually, custom/local NFD sources look like...
So pods can request a pci device or other hardware (similar to device plugin api)
Fixes #805 by updating `utils.FsWatcher` to only return events to the caller if the file actually changed, according to the modification time of the file. We still use `fsnotify` so...
Part of #562 Signed-off-by: Carlos Eduardo Arango Gutierrez
**What would you like to be added**: We start to have a lot of somewhat cluttered features/labels related to security and trusted-execution-environments (e.g. #647, #790, #830) and expecting more to...
Now `nfd-topology-updater` tries to retrieve `topologyManagerPolicy` of a node by reading kubelet config file. However, sometimes we use command line to start Kubelet instead of the config file, or sometimes...
Hi NFD Team, I try today to deploy NFD in Kind Cluster. But I noticed that there are differences between what NFD and cpuid discover. There are fewer characteristics discovered...
Currently Node feature Discovery consists of nfd-master and nfd-worker. The former is responsible for labeling Kubernetes node objects and the latter is responsible for detecting features and communicating them to...
**What would you like to be added**: Now that nfd-worker has quite extensive support for dynamic run-time configurability through its config file, I started to think would it be good...