</code></pre></div></div><p>The last component (i.e. <codeclass="language-plaintext highlighter-rouge notranslate">attribute-name</code>) is optional, and only used if a feature logically has sub-hierarchy, e.g. <codeclass="language-plaintext highlighter-rouge notranslate">sriov.capable</code> and <codeclass="language-plaintext highlighter-rouge notranslate">sriov.configure</code> from the <codeclass="language-plaintext highlighter-rouge notranslate">network</code> source.</p><p>The <codeclass="language-plaintext highlighter-rouge notranslate">--sources</code> flag controls which sources to use for discovery.</p><p><em>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.</em></p><h2id="feature-sources">Feature sources</h2><h3id="cpu">CPU</h3><p>The <strong>cpu</strong> feature source supports the following labels:</p><table><thead><tr><th>Feature name</th><th>Attribute</th><th>Description</th></tr></thead><tbody><tr><td>cpuid</td><td><cpuid flag></td><td>CPU capability is supported</td></tr><tr><td>hardware_multithreading</td><td></td><td>Hardware multithreading, such as Intel HTT, enabled (number of logical CPUs is greater than physical CPUs)</td></tr><tr><td>power</td><td>sst_bf.enabled</td><td>Intel SST-BF (<ahref="https://www.intel.com/content/www/us/en/architecture-and-technology/speed-select-technology-article.html">Intel Speed Select Technology</a> - Base frequency) enabled</td></tr><tr><td><ahref="https://www.kernel.org/doc/Documentation/cpu-freq/intel-pstate.txt">pstate</a></td><td>turbo</td><td>Set to ‘true' if turbo frequencies are enabled in Intel pstate driver, set to ‘false' if they have been disabled.</td></tr><tr><td><ahref="http://www.intel.com/content/www/us/en/architecture-and-technology/resource-director-technology.html">rdt</a></td><td>RDTMON</td><td>Intel RDT Monitoring Technology</td></tr><tr><td></td><td>RDTCMT</td><td>Intel Cache Monitoring (CMT)</td></tr><tr><td></td><td>RDTMBM</td><td>Intel Memory Bandwidth Monitoring (MBM)</td></tr><tr><td></td><td>RDTL3CA</td><td>Intel L3 Cache Allocation Technology</td></tr><tr><td></td><td>RDTL2CA</td><td>Intel L2 Cache Allocation Technology</td></tr><tr><td></td><td>RDTMBA</td><td>Intel Memory Bandwidth Allocation (MBA) Technology</td></tr></tbody></table><p>The (sub-)set of CPUID attributes to publish is configurable via the <codeclass="language-plaintext highlighter-rouge notranslate">attributeBlacklist</code> and <codeclass="language-plaintext highlighter-rouge notranslate">attributeWhitelist</code> cpuid options of the cpu source. If whitelist is specified, only whitelisted attributes will be published. With blacklist, only blacklisted attributes are filtered out. <codeclass="language-plaintext highlighter-rouge notranslate">attributeWhitelist</code> has priority over <codeclass="language-plaintext highlighter-rouge notranslate">attributeBlacklist</code>. For examples and more information about configurability, see <ahref="deployment-and-usage#configuration">configuration</a>. 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.1, SSE4.2 and SSSE3.</p><p><strong>NOTE</strong> The cpuid features advertise <em>supported</em> CPU capabilities, that is, a capability might be supported but not enabled.</p><h4id="x86-cpuid-attributes-partial-list">X86 CPUID attributes (partial list)</h4><table><thead><tr><th>Attribute</th><th>Description</th></tr></thead><tbody><tr><td>ADX</td><td>Multi-Precision Add-Carry Instruction Extensions (ADX)</td></tr><tr><td>AESNI</td><td>Advanced Encryption Standard (AES) New Instructions (AES-NI)</td></tr><tr><td>A
</code></pre></div></div><h4id="custom-features-format-using-the-nomenclature-defined-above">Custom features format (using the nomenclature defined above)</h4><p>Rules are specified under <codeclass="language-plaintext highlighter-rouge notranslate">sources.custom</code> in the nfd-worker configuration file.</p><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">sources</span><spanclass="pi">:</span>
</code></pre></div></div><h4id="matching-process">Matching process</h4><p>Specifying Rules to match on a feature is done by providing a list of Matchers. Each Matcher contains one or more Rules.</p><p>Logical <em>OR</em> is performed between Matchers and logical <em>AND</em> is performed between Rules of a given Matcher.</p><h4id="rules">Rules</h4><h5id="pciid-rule">PciId Rule</h5><h6id="nomenclature">Nomenclature</h6><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>Attribute :A PCI attribute.
Element :An identifier of the PCI attribute.
</code></pre></div></div><p>The PciId Rule allows matching the PCI devices in the system on the following Attributes: <codeclass="language-plaintext highlighter-rouge notranslate">class</code>,<codeclass="language-plaintext highlighter-rouge notranslate">vendor</code> and <codeclass="language-plaintext highlighter-rouge notranslate">device</code>. A list of Elements is provided for each Attribute.</p><h6id="format">Format</h6><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">pciId </span><spanclass="pi">:</span>
</code></pre></div></div><p>Matching is done by performing a logical <em>OR</em> between Elements of an Attribute and logical <em>AND</em> between the specified Attributes for each PCI device in the system. At least one Attribute must be specified. Missing attributes will not partake in the matching process.</p><h5id="usbid-rule">UsbId Rule</h5><h6id="nomenclature-1">Nomenclature</h6><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>Attribute :A USB attribute.
Element :An identifier of the USB attribute.
</code></pre></div></div><p>The UsbId Rule allows matching the USB devices in the system on the following Attributes: <codeclass="language-plaintext highlighter-rouge notranslate">class</code>,<codeclass="language-plaintext highlighter-rouge notranslate">vendor</code> and <codeclass="language-plaintext highlighter-rouge notranslate">device</code>. A list of Elements is provided for each Attribute.</p><h6id="format-1">Format</h6><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">usbId </span><spanclass="pi">:</span>
</code></pre></div></div><p>Matching is done by performing a logical <em>OR</em> between Elements of an Attribute and logical <em>AND</em> between the specified Attributes for each USB device in the system. At least one Attribute must be specified. Missing attributes will not partake in the matching process.</p><h5id="loadedkmod-rule">LoadedKMod rule</h5><h6id="nomenclature-2">Nomenclature</h6><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>Element :A kernel module
</code></pre></div></div><p>The LoadedKMod Rule allows matching the loaded kernel modules in the system against a provided list of Elements.</p><h6id="format-2">Format</h6><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">loadedKMod </span><spanclass="pi">:</span><spanclass="pi">[</span><spanclass="nv"><kernel module></span><spanclass="pi">,</span><spanclass="nv">...</span><spanclass="pi">]</span>
</code></pre></div></div><p>Matching is done by performing logical <em>AND</em> for each provided Element, i.e the Rule will match if all provided Elements (kernel modules) are loaded in the system.</p><h5id="cpuid-rule">CpuId rule</h5><h6id="nomenclature-3">Nomenclature</h6><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>Element :A CPUID flag
</code></pre></div></div><p>The Rule allows matching the available CPUID flags in the system against a provided list of Elements.</p><h6id="format-3">Format</h6><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">cpuId </span><spanclass="pi">:</span><spanclass="pi">[</span><spanclass="nv"><CPUID flag string></span><spanclass="pi">,</span><spanclass="nv">...</span><spanclass="pi">]</span>
</code></pre></div></div><p>Matching is done by performing logical <em>AND</em> for each provided Element, i.e the Rule will match if all provided Elements (CPUID flag strings) are available in the system.</p><h5id="kconfig-rule">Kconfig rule</h5><h6id="nomenclature-4">Nomenclature</h6><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>Element :A Kconfig option
</code></pre></div></div><p>The Rule allows matching the kconfig options in the system against a provided list of Elements.</p><h6id="format-4">Format</h6><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">kConfig</span><spanclass="pi">:</span><spanclass="pi">[</span><spanclass="nv"><kernel config option ('y' or 'm') or '=<value>'></span><spanclass="pi">,</span><spanclass="nv">...</span><spanclass="pi">]</span>
</code></pre></div></div><p>Matching is done by performing logical <em>AND</em> for each provided Element, i.e the Rule will match if all provided Elements (kernel config options) are enabled (<codeclass="language-plaintext highlighter-rouge notranslate">y</code> or <codeclass="language-plaintext highlighter-rouge notranslate">m</code>) or matching <codeclass="language-plaintext highlighter-rouge notranslate">=<value></code> in the kernel.</p><h4id="example">Example</h4><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">custom</span><spanclass="pi">:</span>
</code></pre></div></div><p><strong>In the example above:</strong></p><ul><li>A node would contain the label: <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io/custom-my.kernel.feature=true</code> if the node has <codeclass="language-plaintext highlighter-rouge notranslate">kmod1</code><em>AND</em><codeclass="language-plaintext highlighter-rouge notranslate">kmod2</code> kernel modules loaded.</li><li>A node would contain the label: <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io/custom-my.pci.feature=true</code> if the node contains a PCI device with a PCI vendor ID of <codeclass="language-plaintext highlighter-rouge notranslate">15b3</code><em>AND</em> PCI device ID of <codeclass="language-plaintext highlighter-rouge notranslate">1014</code><em>OR</em><codeclass="language-plaintext highlighter-rouge notranslate">1017</code>.</li><li>A node would contain the label: <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io/custom-my.usb.feature=true</code> if the node contains a USB device with a USB vendor ID of <codeclass="language-plaintext highlighter-rouge notranslate">1d6b</code><em>AND</em> USB device ID of <codeclass="language-plaintext highlighter-rouge notranslate">0003</code>.</li><li>A node would contain the label: <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io/custom-my.combined.feature=true</code> if <codeclass="language-plaintext highlighter-rouge notranslate">vendor_kmod1</code><em>AND</em><codeclass="language-plaintext highlighter-rouge notranslate">vendor_kmod2</code> kernel modules are loaded <strong>AND</strong> the node contains a PCI device with a PCI vendor ID of <codeclass="language-plaintext highlighter-rouge notranslate">15b3</code><em>AND</em> PCI device ID of <codeclass="language-plaintext highlighter-rouge notranslate">1014</code><em>or</em><codeclass="language-plaintext highlighter-rouge notranslate">1017</code>.</li><li>A node would contain the label: <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io/custom-my.accumulated.feature=true</code> if <codeclass="language-plaintext highlighter-rouge notranslate">some_kmod1</code><em>AND</em><codeclass="language-plaintext highlighter-rouge notranslate">some_kmod2</code> kernel modules are loaded <strong>OR</strong> the node contains a PCI device with a PCI vendor ID of <codeclass="language-plaintext highlighter-rouge notranslate">15b3</code><em>AND</em> PCI device ID of <codeclass="language-plaintext highlighter-rouge notranslate">1014</code><em>OR</em><codeclass="language-plaintext highlighter-rouge notranslate">1017</code>.</li><li>A node would contain the label: <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io/custom-my.kernel.featureneedscpu=true</code> if <codeclass="language-plaintext highlighter-rouge notranslate">KVM_INTEL</code> kernel config is enabled <strong>AND</strong> the node CPU supports <codeclass="language-plaintext highlighter-rouge notranslate">VMX</code> virtual machine extensions</li><li>A node would contain the label: <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io/custom-my.kernel.modulecompiler=true</code> if the in-tree <codeclass="language-plaintext highlighter-rouge notranslate">kmod1</code> kernel module is loaded <strong>AND</strong> it's built with <codeclass="language-plaintext highlighter-rouge notranslate">GCC_VERSION=100101</code>.</li></ul><h4id="statically-defined-features">Statically defined features</h4><p>Some feature labels which are common and generic are defined statically in the <codeclass="language-plaintext highlighter-rouge notranslate">custom</code> feature source. A user may add additional Matchers to these feature labels by defining them in the <codeclass="language-plaintext highlighter-rouge notranslate">nfd-worker</code> configuration file.</p><table><thead><tr><t
</code></pre></div></div><p>Also the set of PCI device classes that the feature source detects is configurable. By default, device classes (0x)03, (0x)0b40 and (0x)12, i.e. GPUs, co-processors and accelerator cards are detected.</p><h3id="usb">USB</h3><p>The <strong>usb</strong> feature source supports the following labels:</p><table><thead><tr><th>Feature</th><th>Attribute</th><th>Description</th></tr></thead><tbody><tr><td><device label></td><td>present</td><td>USB device is detected</td></tr></tbody></table><p><codeclass="language-plaintext highlighter-rouge notranslate"><device label></code> is composed of raw USB IDs, separated by underscores. The set of fields used in <codeclass="language-plaintext highlighter-rouge notranslate"><device label></code> is configurable, valid fields being <codeclass="language-plaintext highlighter-rouge notranslate">class</code>, <codeclass="language-plaintext highlighter-rouge notranslate">vendor</code>, and <codeclass="language-plaintext highlighter-rouge notranslate">device</code>. Defaults are <codeclass="language-plaintext highlighter-rouge notranslate">class</code>, <codeclass="language-plaintext highlighter-rouge notranslate">vendor</code> and <codeclass="language-plaintext highlighter-rouge notranslate">device</code>. An example label using the default label fields:</p><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>feature.node.kubernetes.io/usb-fe_1a6e_089a.present=true
</code></pre></div></div><p>See <ahref="deployment-and-usage#configuration">configuration</a> for more information on NFD config.</p><h3id="storage">Storage</h3><p>The <strong>storage</strong> feature source supports the following labels:</p><table><thead><tr><th>Feature name</th><th>Description</th></tr></thead><tbody><tr><td>nonrotationaldisk</td><td>Non-rotational disk, like SSD, is present in the node</td></tr></tbody></table><h3id="system">System</h3><p>The <strong>system</strong> feature source supports the following labels:</p><table><thead><tr><th>Feature</th><th>Attribute</th><th>Description</th></tr></thead><tbody><tr><td>os_release</td><td>ID</td><td>Operating system identifier</td></tr><tr><td></td><td>VERSION_ID</td><td>Operating system version identifier (e.g. ‘6.7')</td></tr><tr><td></td><td>VERSION_ID.major</td><td>First component of the OS version id (e.g. ‘6')</td></tr><tr><td></td><td>VERSION_ID.minor</td><td>Second component of the OS version id (e.g. ‘7')</td></tr></tbody></table><h3id="local--user-specific-features">Local – user-specific features</h3><p>NFD has a special feature source named <em>local</em> which is designed for getting the labels from user-specific feature detector. It provides a mechanism for users to implement custom feature sources in a pluggable way, without modifying nfd source code or Docker images. The local feature source can be used to advertise new user-specific features, and, for overriding labels created by the other feature sources.</p><p>The <em>local</em> feature source gets its labels by two different ways:</p><ul><li>It tries to execute files found under <codeclass="language-plaintext highlighter-rouge notranslate">/etc/kubernetes/node-feature-discovery/source.d/</code> directory. The hook files must be executable and they are supposed to print all discovered features in <codeclass="language-plaintext highlighter-rouge notranslate">stdout</code>, one per line. With ELF binaries static linking is recommended as the selection of system libraries available in the NFD release image is very limited. Other runtimes currently supported by the NFD stock image are bash and perl.</li><li>It reads files found under <codeclass="language-plaintext highlighter-rouge notranslate">/etc/kubernetes/node-feature-discovery/features.d/</code> directory. The file content is expected to be similar to the hook output (described above).</li></ul><p>These directories must be available inside the Docker image so Volumes and VolumeMounts must be used if standard NFD images are used. The given template files mount by default the <codeclass="language-plaintext highlighter-rouge notranslate">source.d</code> and the <codeclass="language-plaintext highlighter-rouge notranslate">features.d</code> directories respectively from <codeclass="language-plaintext highlighter-rouge notranslate">/etc/kubernetes/node-feature-discovery/source.d/</code> and <codeclass="language-plaintext highlighter-rouge notranslate">/etc/kubernetes/node-feature-discovery/features.d/</code> from the host. You should update them to match your needs.</p><p>In both cases, the labels can be binary or non binary, using either <codeclass="language-plaintext highlighter-rouge notranslate"><name></code> or <codeclass="language-plaintext highlighter-rouge notranslate"><name>=<value></code> format.</p><p>Unlike the other feature sources, the name of the file, instead of the name of the feature source (that would be <codeclass="language-plaintext highlighter-rouge notranslate">local</code> in this case), is used as a prefix in the label name, normally. However, if the <codeclass="language-plaintext highlighter-rouge notranslate"><name></code> of the label starts with a slash (<codeclass="language-plaintext highlighter-rouge notranslate">/</code>) it is used as the label name as is, without any additional prefix. This makes it possible for the user to fully control the feature label names, e.g. for overriding labels created
</code></pre></div></div><p>which, in turn, will translate into the following node labels:</p><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>feature.node.kubernetes.io/my-source-MY_FEATURE_1=true
</code></pre></div></div><h4id="a-file-example">A file example</h4><p>User has a file <codeclass="language-plaintext highlighter-rouge notranslate">/etc/kubernetes/node-feature-discovery/features.d/my-source</code> which contains the following lines:</p><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>MY_FEATURE_1
</code></pre></div></div><p>which, in turn, will translate into the following node labels:</p><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>feature.node.kubernetes.io/my-source-MY_FEATURE_1=true
</code></pre></div></div><p>NFD tries to run any regular files found from the hooks directory. Any additional data files your hook might need (e.g. a configuration file) should be placed in a separate directory in order to avoid NFD unnecessarily trying to execute these. You can use a subdirectory under the hooks directory, for example <codeclass="language-plaintext highlighter-rouge notranslate">/etc/kubernetes/node-feature-discovery/source.d/conf/</code>.</p><p><strong>NOTE!</strong> NFD will blindly run any executables placed/mounted in the hooks directory. It is the user's responsibility to review the hooks for e.g. possible security implications.</p><p><strong>NOTE!</strong> Be careful when creating and/or updating hook or feature files while NFD is running. In order to avoid race conditions you should write into a temporary file (outside the <codeclass="language-plaintext highlighter-rouge notranslate">source.d</code> and <codeclass="language-plaintext highlighter-rouge notranslate">features.d</code> directories), and, atomically create/update the original file by doing a filesystem move operation.</p><h2id="extended-resources">Extended resources</h2><p>This feature is experimental and by no means a replacement for the usage of device plugins.</p><p>Labels which have integer values, can be promoted to Kubernetes extended resources by listing them to the master <codeclass="language-plaintext highlighter-rouge notranslate">--resource-labels</code> command line flag. These labels won't then show in the node label section, they will appear only as extended resources.</p><p>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 <codeclass="language-plaintext highlighter-rouge notranslate">--resource-labels</code> 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.</p><p>Similar to labels, the default namespace <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io</code> is automatically prefixed to the extended resource, if the promoted label doesn't have a namespace.</p><p>Example usage of the command line arguments, using a new namespace: <codeclass="language-plaintext highlighter-rouge notranslate">nfd-master --resource-labels=my_source-my.feature,sgx.some.ns/epc --extra-label-ns=sgx.some.ns</code></p><p>The above would result in following extended resources provided that related labels exist:</p><divclass="language-plaintext highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code> sgx.some.ns/epc: <label value>
</code></pre></div></div><!-- Links --></div></div><divclass="navigation-bottom d-flex flex-justify-between py-3"role="navigation"aria-label="footer navigation"><divclass="prev"><ahref="/node-feature-discovery/v0.7/get-started/deployment-and-usage.html"class="btn"title="Deployment and usage"accesskey="p"rel="prev"><iclass="fa fa-arrow-circle-left"></i> Previous </a></div><divclass="next"><ahref="/node-feature-discovery/v0.7/get-started/examples-and-demos.html"class="btn"title="Examples and demos"accesskey="n"rel="next"> Next <iclass="fa fa-arrow-circle-right"></i></a></div></div><hr><divclass="copyright text-center text-gray"role="contentinfo"><iclass="fa fa-copyright"></i><spanclass="time">2016-2023,</span><aclass="text-gray"href="https://github.com/kubernetes-sigs"rel="noreferrer"target="_blank">Kubernetes SIGs</a> Revision <aclass="text-gray"href="https://github.com/kubernetes-sigs/node-feature-discovery/commit/"title=""rel="noreferrer"target="_blank"></a><br><divclass="generator"> Built with <ahref="https://jekyllrb.com"rel="noreferrer"target="_blank">Jekyll</a> using a <ahref="https://github.com/rundocs/jekyll-rtd-theme"rel="noreferrer"target="_blank"title="remote theme: jekyll-rtd-theme v2.0.9">theme</a> provided by <ahref="https://rundocs.io"rel="noreferrer"target="_blank">RunDocs</a>. </div></div></div></div><divclass="addons-wrap d-flex flex-column overflow-y-auto"><divclass="status d-flex flex-justify-between p-2"><divclass="title p-1"><iclass="fa fa-book"></i> Node Feature Discovery </div><divclass="branch p-1"><spanclass="name"> v0.7 </span><iclass="fa fa-caret-down"></i></div></div><divclass="addons d-flex flex-column height-full p-2 d-none"><dlid="versions"><dt>Versions</dt><scriptsrc="/node-feature-discovery/versions.js"></script><script>vardt=document.getElementById('versions');varitems=getVersionListItems();for(vari=0;i<items.length;i++){vardd=document.createElement('dd');vara=dd.appendChild(document.createElement('a'));a.appendChild(document.createTextNode(items[i].name));a.href=items[i].url;dt.appendChild(dd);}</script></dl><dl><dt>GitHub</dt><dd><ahref="https://github.com/kubernetes-sigs/node-feature-discovery"title="Stars: 548"><iclass="fa fa-github"></i> Homepage </a></dd><dd><ahref="https://github.com/kubernetes-sigs/node-feature-discovery/issues"title="Open issues: 31"><iclass="fa fa-question-circle-o"></i> Issues </a></dd><dd><ahref="https://github.com/kubernetes-sigs/node-feature-discovery/zipball/gh-pages"title="Size: 88715 Kb"><iclass="fa fa-download"></i> Download </a></dd></dl><hr><divclass="license f6 pb-2"> The <ahref="/node-feature-discovery/v0.7/">software</a> is under the terms of <ahref="https://github.com/kubernetes-sigs/node-feature-discovery">Apache License 2.0</a>. </div></div></div><script>window.ui={title:"Node Feature Discovery",baseurl:"/node-feature-discovery/v0.7",i18n:{search_results:"Search Results",search_results_found:"Search finished, found # page(s) matching the search query.",search_results_not_found:"Your search did not match any documents, please make sure that all characters are spelled correctly!"}};</script><scriptsrc="https://cdn.jsdelivr.net/gh/rundocs/jekyll-rtd-theme@2.0.9/assets/js/jquery.min.js"></script><scriptsrc="https://cdn.jsdelivr.net/gh/rundocs/jekyll-rtd-theme@2.0.9/assets/js/theme.min.js"></script></body></html>
