node-feature-discovery
node-feature-discovery copied to clipboard
Node feature discovery for Kubernetes
Move the previously-protobuf-only internal "feature api" over to the public "nfd api" package. This is in preparation for introducing a new CRD API for communicating features. This patch carries no...
These updates are based on kernel 5.19.4 and glibc 2.36. - cpu: update ARM CPU flags - cpu: update POWER CPU flags - cpu: update S390 CPU flags Related: #914...
This PR implements a new CRD-based communication mechanism between nfd-worker and nfd-master, serving as an API for 3rd party extensions and paving way for ditching gRPC in the future, among...
Avoid trying to create empty "cpu-cpuid." labels for cpuid flags that we don't have a description for.
This PR enables setting node taints defined on NodeFeatureRule CR. User can define a list of taints under spec.rule of the CR as in this example: ```yaml apiVersion: nfd.k8s-sigs.io/v1alpha1 kind:...
Fixes: https://github.com/kubernetes-sigs/node-feature-discovery/issues/778
**What happened**: Invalid feature name 'cpu-cpuid.' warning is shown in nfd-worker pod logs **What you expected to happen**: Invalid feature name 'cpu-cpuid.' warning should not be shown in nfd-worker pod...
Hi there, I'm trying to get NFD working in my k8s cluster. I have 3 nodes in my cluster; two workers and a control plane. Immediately after installing, the nfd-worker...
**What would you like to be added**: Run E2E tests on dedicated baremetal machines as a presubmit job for every future PR. **Why is this needed**: Current infra (an AWS...
**Why is this needed**: Currently the time interval NFD takes between feature checking / labeling could differ significantly from the interval specified by the user, because it's used as an...