node-feature-discovery
node-feature-discovery copied to clipboard
kubernetes-sigs
Node feature discovery for Kubernetes
**What would you like to be added**: It would be nice if NFD could be configured with options to set node taints as well as labels, based on certain features...
**What would you like to be added**: Better document the purpose of different deployment options. Spun off of https://github.com/kubernetes-sigs/node-feature-discovery/pull/640#issuecomment-968687743 > I mean that we should probably accept the different deployment...
**What would you like to be added**: End-to-end tests to cover usage of NodeFeatureRule objects. **Why is this needed**: Better test coverage
**What would you like to be added**: I'd like to move to a shorter label namespace (e.g. `nfd.k8s.io/` or `feature.node.k8s.io/`) before nfd v1.0. I'm not sure what would be the...
**What would you like to be added**: Replace gRPC with a CRD. Introduce a new `NodeFeature` CRD for nfd-worker to expose all underlying "raw" features. This would be per-node, i.e....
Move existing security/trusted-execution related features (i.e. SGX and SE) under the same `security` feature, deprecating the old features. The motivation for the change is to keep the source code and...
Set `cpu.tdx-enable` to `true` when TDX is avialable and has been enabled. `/sys/module/kvm_intel/parameters/tdx` presence and content is used to detect whether a CPU is Intel TDX capable. Signed-off-by: Fabiano Fidêncio
This issue is a tracker of needed tasks to migrate the default branch of the repo from `master` to `main`. Following https://www.kubernetes.dev/resources/rename/ guidance ### Anytime These changes are **non-disruptive** and...
**What happened**: After a node(as a NFD worker) was deleted through "kubectl" command and rejoin to the cluster, the NFD worker failed to communicate with NFD master. And there are...
Partially fixes: https://github.com/kubernetes-sigs/node-feature-discovery/issues/902
