Features are advertised as labels in the Kubernetes Node object.
Label creation in nfd-worker is performed by a set of separate modules called label sources. The
core.labelSources configuration option (or
-label-sources flag) of nfd-worker controls which sources to enable for label generation.
All built-in labels use the
feature.node.kubernetes.io label namespace and have the following format.
feature.node.kubernetes.io/<feature> = <value>
Note: Consecutive runs of nfd-worker will update the labels on a given node. If features are not discovered on a consecutive run, the corresponding label will be removed. This includes any restrictions placed on the consecutive run, such as restricting discovered features with the -label-whitelist option.
| ||true||CPU capability is supported. NOTE: the capability might be supported but not enabled.|
| ||true||Hardware multithreading, such as Intel HTT, enabled (number of logical CPUs is greater than physical CPUs)|
| ||true||Intel SST-BF (Intel Speed Select Technology - Base frequency) enabled|
| ||string||The status of the Intel pstate driver when in use and enabled, either ‘active' or ‘passive'.|
| ||bool||Set to ‘true' if turbo frequencies are enabled in Intel pstate driver, set to ‘false' if they have been disabled.|
| ||string||The value of the Intel pstate scaling_governor when in use, either ‘powersave' or ‘performance'.|
| ||bool||Set to ‘true' if cstates are set in the intel_idle driver, otherwise set to ‘false'. Unset if intel_idle cpuidle driver is not active.|
| ||true||Intel RDT capability is supported. See RDT flags for details.|
| ||true||Set to ‘true' if Intel SGX is enabled in BIOS (based a non-zero sum value of SGX EPC section sizes).|
| ||true||Set to ‘true' if IBM Secure Execution for Linux (IBM Z & LinuxONE) is available and enabled (requires |
| ||string||Comparable CPU vendor ID.|
| ||int||CPU family.|
| ||int||CPU model number.|
The CPU label source is configurable, see worker configuration and
sources.cpu configuration options for details.
|ADX||Multi-Precision Add-Carry Instruction Extensions (ADX)|
|AESNI||Advanced Encryption Standard (AES) New Instructions (AES-NI)|
|AVX||Advanced Vector Extensions (AVX)|
|AVX2||Advanced Vector Extensions 2 (AVX2)|
|AMXBF16||Advanced Matrix Extension, tile multiplication operations on BFLOAT16 numbers|
|AMXINT8||Advanced Matrix Extension, tile multiplication operations on 8-bit integers|
|AMXTILE||Advanced Matrix Extension, base tile architecture support|
|AVX512BF16||AVX-512 BFLOAT16 instructions|
|AVX512BITALG||AVX-512 bit Algorithms|
|AVX512BW||AVX-512 byte and word Instructions|
|AVX512CD||AVX-512 conflict detection instructions|
|AVX512DQ||AVX-512 doubleword and quadword instructions|
|AVX512ER||AVX-512 exponential and reciprocal instructions|
|AVX512FP16||AVX-512 FP16 instructions|
|AVX512IFMA||AVX-512 integer fused multiply-add instructions|
|AVX512PF||AVX-512 prefetch instructions|
|AVX512VBMI||AVX-512 vector bit manipulation instructions|
|AVX512VBMI2||AVX-512 vector bit manipulation instructions, version 2|
|AVX512VL||AVX-512 vector length extensions|
|AVX512VNNI||AVX-512 vector neural network instructions|
|AVX512VP2INTERSECT||AVX-512 intersect for D/Q|
|AVX512VPOPCNTDQ||AVX-512 vector population count doubleword and quadword|
|GFNI||Galois Field New Instructions|
|HYPERVISOR||Running under hypervisor|
|VAES||AVX-512 vector AES instructions|
|VPCLMULQDQ||Carry-less multiplication quadword|
By default, the following CPUID flags have been blacklisted: BMI1, BMI2, CLMUL, CMOV, CX16, ERMS, F16C, HTT, LZCNT, MMX, MMXEXT, NX, POPCNT, RDRAND, RDSEED, RDTSCP, SGX, SSE, SSE2, SSE3, SSE4, SSE42 and SSSE3. See
sources.cpu configuration options to change the behavior.
See the full list in github.com/klauspost/cpuid.
|IDIVA||Integer divide instructions available in ARM mode|
|IDIVT||Integer divide instructions available in Thumb mode|
|VFP||Vector floating point instruction extension (VFP)|
|VFPv3||Vector floating point extension v3|
|VFPv4||Vector floating point extension v4|
|VFPD32||VFP with 32 D-registers|
|HALF||Half-word loads and stores|
|NEON||NEON SIMD instructions|
|LPAE||Large Physical Address Extensions|
|AES||Announcing the Advanced Encryption Standard|
|EVSTRM||Event Stream Frequency Features|
|FPHP||Half Precision(16bit) Floating Point Data Processing Instructions|
|ASIMDHP||Half Precision(16bit) Asimd Data Processing Instructions|
|ATOMICS||Atomic Instructions to the A64|
|ASIMRDM||Support for Rounding Double Multiply Add/Subtract|
|PMULL||Optional Cryptographic and CRC32 Instructions|
|DCPOP||Persistent Memory Support|
|RDTMON||Intel RDT Monitoring Technology|
|RDTCMT||Intel Cache Monitoring (CMT)|
|RDTMBM||Intel Memory Bandwidth Monitoring (MBM)|
|RDTL3CA||Intel L3 Cache Allocation Technology|
|RDTl2CA||Intel L2 Cache Allocation Technology|
|RDTMBA||Intel Memory Bandwidth Allocation (MBA) Technology|
| ||true||IOMMU is present and enabled in the kernel|
DEPRECATED: The iommu source is deprecated and not enabled by default.
| ||true||Kernel config option is enabled (set ‘y' or ‘m'). Default options are |
| ||true||Selinux is enabled on the node|
| ||string||Full kernel version as reported by |
| ||string||First component of the kernel version (e.g. ‘4')|
| ||string||Second component of the kernel version (e.g. ‘5')|
| ||string||Third component of the kernel version (e.g. ‘6')|
The kernel label source is configurable, see worker configuration and
sources.kernel configuration options for details.
| ||true||Multiple memory nodes i.e. NUMA architecture detected|
| ||true||NVDIMM device(s) are present|
| ||true||NVDIMM region(s) configured in DAX mode are present|
| ||true||Single Root Input/Output Virtualization (SR-IOV) enabled Network Interface Card(s) present|
| ||true||SR-IOV virtual functions have been configured|
| ||true||PCI device is detected|
| ||true||Single Root Input/Output Virtualization (SR-IOV) enabled PCI device present|
<device label> is format is configurable and set to
<class>_<vendor> by default. For more more details about configuration of the pci labels, see
sources.pci options and worker configuration instructions.
| ||true||USB device is detected|
<device label> is format is configurable and set to
<class>_<vendor>_<device> by default. For more more details about configuration of the usb labels, see
sources.usb options and worker configuration instructions.
| ||true||Non-rotational disk, like SSD, is present in the node|
| ||string||Operating system identifier|
| ||string||Operating system version identifier (e.g. ‘6.7')|
| ||string||First component of the OS version id (e.g. ‘6')|
| ||string||Second component of the OS version id (e.g. ‘7')|
The custom label source is designed for creating user defined labels. However, it has a few statically defined built-in labels:
| ||true||The node has an RDMA capable Network adapter|
| ||true||The node has the needed RDMA modules loaded to run RDMA traffic|
NFD has many extension points for creating vendor and application specific labels. See the customization guide for detailed documentation.
This feature is experimental and by no means a replacement for the usage of device plugins.
Labels which have integer values, can be promoted to Kubernetes extended resources by listing them to the master
-resource-labels command line flag. These labels won't then show in the node label section, they will appear only as extended resources.
An example use-case for the extended resources could be based on a hook which creates a label for the node SGX EPC memory section size. By giving the name of that label in the
-resource-labels flag, that value will then turn into an extended resource of the node, allowing PODs to request that resource and the Kubernetes scheduler to schedule such PODs to only those nodes which have a sufficient capacity of said resource left.
Similar to labels, the default namespace
feature.node.kubernetes.io is automatically prefixed to the extended resource, if the promoted label doesn't have a namespace.
Example usage of the command line arguments, using a new namespace:
nfd-master -resource-labels=my_source-my.feature,sgx.some.ns/epc -extra-label-ns=sgx.some.ns
The above would result in following extended resources provided that related labels exist:
sgx.some.ns/epc: <label value> feature.node.kubernetes.io/my_source-my.feature: <label value>