</code></pre></div></div><h3id="-h--help">-h, -help</h3><p>Print usage and exit.</p><h3id="-version">-version</h3><p>Print version and exit.</p><h3id="-config">-config</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-config</code> flag specifies the path of the nfd-worker configuration file to use.</p><p>Default: /etc/kubernetes/node-feature-discovery/nfd-worker.conf</p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-config</span><spanclass="o">=</span>/opt/nfd/worker.conf
</code></pre></div></div><h3id="-options">-options</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-options</code> flag may be used to specify and override configuration file options directly from the command line. The required format is the same as in the config file i.e. JSON or YAML. Configuration options specified via this flag will override those from the configuration file:</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-options</span><spanclass="o">=</span><spanclass="s1">'{"sources":{"cpu":{"cpuid":{"attributeWhitelist":["AVX","AVX2"]}}}}'</span>
</code></pre></div></div><h3id="-server">-server</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-server</code> flag specifies the address of the nfd-master endpoint where to connect to.</p><p>Default: localhost:8080</p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-server</span><spanclass="o">=</span>nfd-master.nfd.svc.cluster.local:443
</code></pre></div></div><h3id="-ca-file">-ca-file</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-ca-file</code> is one of the three flags (together with <codeclass="language-plaintext highlighter-rouge notranslate">-cert-file</code> and <codeclass="language-plaintext highlighter-rouge notranslate">-key-file</code>) controlling the mutual TLS authentication on the worker side. This flag specifies the TLS root certificate that is used for verifying the authenticity of nfd-master.</p><p>Default: <em>empty</em></p><p>Note: Must be specified together with <codeclass="language-plaintext highlighter-rouge notranslate">-cert-file</code> and <codeclass="language-plaintext highlighter-rouge notranslate">-key-file</code></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-ca-file</span><spanclass="o">=</span>/opt/nfd/ca.crt <spanclass="nt">-cert-file</span><spanclass="o">=</span>/opt/nfd/worker.crt <spanclass="nt">-key-file</span><spanclass="o">=</span>/opt/nfd/worker.key
</code></pre></div></div><h3id="-cert-file">-cert-file</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-cert-file</code> is one of the three flags (together with <codeclass="language-plaintext highlighter-rouge notranslate">-ca-file</code> and <codeclass="language-plaintext highlighter-rouge notranslate">-key-file</code>) controlling mutual TLS authentication on the worker side. This flag specifies the TLS certificate presented for authenticating outgoing requests.</p><p>Default: <em>empty</em></p><p>Note: Must be specified together with <codeclass="language-plaintext highlighter-rouge notranslate">-ca-file</code> and <codeclass="language-plaintext highlighter-rouge notranslate">-key-file</code></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-workerr <spanclass="nt">-cert-file</span><spanclass="o">=</span>/opt/nfd/worker.crt <spanclass="nt">-key-file</span><spanclass="o">=</span>/opt/nfd/worker.key <spanclass="nt">-ca-file</span><spanclass="o">=</span>/opt/nfd/ca.crt
</code></pre></div></div><h3id="-key-file">-key-file</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-key-file</code> is one of the three flags (together with <codeclass="language-plaintext highlighter-rouge notranslate">-ca-file</code> and <codeclass="language-plaintext highlighter-rouge notranslate">-cert-file</code>) controlling the mutual TLS authentication on the worker side. This flag specifies the private key corresponding the given certificate file (<codeclass="language-plaintext highlighter-rouge notranslate">-cert-file</code>) that is used for authenticating outgoing requests.</p><p>Default: <em>empty</em></p><p>Note: Must be specified together with <codeclass="language-plaintext highlighter-rouge notranslate">-cert-file</code> and <codeclass="language-plaintext highlighter-rouge notranslate">-ca-file</code></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-key-file</span><spanclass="o">=</span>/opt/nfd/worker.key <spanclass="nt">-cert-file</span><spanclass="o">=</span>/opt/nfd/worker.crt <spanclass="nt">-ca-file</span><spanclass="o">=</span>/opt/nfd/ca.crt
</code></pre></div></div><h3id="-kubeconfig">-kubeconfig</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-kubeconfig</code> flag specifies the kubeconfig to use for connecting to the Kubernetes API server. It is only needed for manipulating <ahref="/node-feature-discovery/v0.13/usage/custom-resources.html#nodefeature">NodeFeature</a> objects, and thus the flag only takes effect when <ahref="#-enable-nodefeature-api"><codeclass="language-plaintext highlighter-rouge notranslate">-enable-nodefeature-api</code></a>) is specified. An empty value (which is also the default) implies in-cluster kubeconfig.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-kubeconfig</span><spanclass="k">${</span><spanclass="nv">HOME</span><spanclass="k">}</span>/.kube/config
</code></pre></div></div><h3id="-server-name-override">-server-name-override</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-server-name-override</code> flag specifies the common name (CN) which to expect from the nfd-master TLS certificate. This flag is mostly intended for development and debugging purposes.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-server-name-override</span><spanclass="o">=</span>localhost
</code></pre></div></div><h3id="-feature-sources">-feature-sources</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-feature-sources</code> flag specifies a comma-separated list of enabled feature sources. A special value <codeclass="language-plaintext highlighter-rouge notranslate">all</code> enables all sources. Prefixing a source name with <codeclass="language-plaintext highlighter-rouge notranslate">-</code> indicates that the source will be disabled instead - this is only meaningful when used in conjunction with <codeclass="language-plaintext highlighter-rouge notranslate">all</code>. This command line flag allows completely disabling the feature detection so that neither standard feature labels are generated nor the raw feature data is available for custom rule processing. Consider using the <codeclass="language-plaintext highlighter-rouge notranslate">core.featureSources</code> config file option, instead, allowing dynamic configurability.</p><p>Note: This flag takes precedence over the <codeclass="language-plaintext highlighter-rouge notranslate">core.featureSources</code> configuration file option.</p><p>Default: all</p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-feature-sources</span><spanclass="o">=</span>all,-pci
</code></pre></div></div><h3id="-label-sources">-label-sources</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-label-sources</code> flag specifies a comma-separated list of enabled label sources. A special value <codeclass="language-plaintext highlighter-rouge notranslate">all</code> enables all sources. Prefixing a source name with <codeclass="language-plaintext highlighter-rouge notranslate">-</code> indicates that the source will be disabled instead - this is only meaningful when used in conjunction with <codeclass="language-plaintext highlighter-rouge notranslate">all</code>. Consider using the <codeclass="language-plaintext highlighter-rouge notranslate">core.labelSources</code> config file option, instead, allowing dynamic configurability.</p><p>Note: This flag takes precedence over the <codeclass="language-plaintext highlighter-rouge notranslate">core.labelSources</code> configuration file option.</p><p>Default: all</p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-label-sources</span><spanclass="o">=</span>kernel,system,local
</code></pre></div></div><h3id="-enable-nodefeature-api">-enable-nodefeature-api</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-enable-nodefeature-api</code> flag enables the experimental <ahref="/node-feature-discovery/v0.13/usage/custom-resources.html#nodefeature">NodeFeature</a> CRD API for communicating with nfd-master. This will also automatically disable the gRPC communication to nfd-master. When enabled, nfd-worker will create per-node NodeFeature objects the contain all discovered node features and the set of feature labels to be created.</p><p>Default: false</p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-enable-nodefeature-api</span>
</code></pre></div></div><h3id="-no-publish">-no-publish</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-no-publish</code> flag disables all communication with the nfd-master and the Kubernetes API server. It is effectively a "dry-run" flag for nfd-worker. NFD-Worker runs feature detection normally, but no labeling requests are sent to nfd-master and no NodeFeature objects are created or updated in the API server.</p><p>Note: This flag takes precedence over the <ahref="/node-feature-discovery/v0.13/reference/worker-configuration-reference.html#corenopublish"><codeclass="language-plaintext highlighter-rouge notranslate">core.noPublish</code></a> configuration file option.</p><p>Default: <em>false</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-no-publish</span>
</code></pre></div></div><h3id="-oneshot">-oneshot</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-oneshot</code> flag causes nfd-worker to exit after one pass of feature detection.</p><p>Default: <em>false</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-worker <spanclass="nt">-oneshot</span><spanclass="nt">-no-publish</span>
</code></pre></div></div><h3id="logging">Logging</h3><p>The following logging-related flags are inherited from the <ahref="https://pkg.go.dev/k8s.io/klog/v2">klog</a> package.</p><p>Note: The logger setup can also be specified via the <codeclass="language-plaintext highlighter-rouge notranslate">core.klog</code> configuration file options. However, the command line flags take precedence over any corresponding config file options specified.</p><h4id="-add_dir_header">-add_dir_header</h4><p>If true, adds the file directory to the header of the log messages.</p><p>Default: false</p><h4id="-alsologtostderr">-alsologtostderr</h4><p>Log to standard error as well as files.</p><p>Default: false</p><h4id="-log_backtrace_at">-log_backtrace_at</h4><p>When logging hits line file:N, emit a stack trace.</p><p>Default: <em>empty</em></p><h4id="-log_dir">-log_dir</h4><p>If non-empty, write log files in this directory.</p><p>Default: <em>empty</em></p><h4id="-log_file">-log_file</h4><p>If non-empty, use this log file.</p><p>Default: <em>empty</em></p><h4id="-log_file_max_size">-log_file_max_size</h4><p>Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited.</p><p>Default: 1800</p><h4id="-logtostderr">-logtostderr</h4><p>Log to standard error instead of files</p><p>Default: true</p><h4id="-skip_headers">-skip_headers</h4><p>If true, avoid header prefixes in the log messages.</p><p>Default: false</p><h4id="-skip_log_headers">-skip_log_headers</h4><p>If true, avoid headers when opening log files.</p><p>Default: false</p><h4id="-stderrthreshold">-stderrthreshold</h4><p>Logs at or above this threshold go to stderr.</p><p>Default: 2</p><h4id="-v">-v</h4><p>Number for the log level verbosity.</p><p>Default: 0</p><h4id="-vmodule">-vmodule</h4><p>Comma-separated list of <codeclass="language-plaintext highlighter-rouge notranslate">pattern=N</code> settings for file-filtered logging.</p><p>Default: <em>empty</em></p></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.13/reference/master-commandline-reference.html"class="btn"title="Master cmdline reference"accesskey="p"rel="prev"><iclass="fa fa-arrow-circle-left"></i> Previous </a></div><divclass="next"><ahref="/node-feature-discovery/v0.13/reference/master-configuration-reference.html"class="btn"title="Master config reference"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://pages.github.com"rel="noreferrer"target="_blank"title="github-pages v227">GitHub Pages</a> using a <ahref="https://github.com/rundocs/jekyll-rtd-theme"rel="noreferrer"target="_blank"title="rundocs/jekyll-rtd-theme v2.0.10">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.13 </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');var
