</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="-prune">-prune</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-prune</code> flag is a sub-command like option for cleaning up the cluster. It causes nfd-master to remove all NFD related labels, annotations and extended resources from all Node objects of the cluster and exit.</p><h3id="-port">-port</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-port</code> flag specifies the TCP port that nfd-master listens for incoming requests.</p><p>Default: 8080</p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-port</span><spanclass="o">=</span>443
</code></pre></div></div><h3id="-instance">-instance</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-instance</code> flag makes it possible to run multiple NFD deployments in parallel. In practice, it separates the node annotations between deployments so that each of them can store metadata independently. The instance name must start and end with an alphanumeric character and may only contain alphanumeric characters, <codeclass="language-plaintext highlighter-rouge notranslate">-</code>, <codeclass="language-plaintext highlighter-rouge notranslate">_</code> or <codeclass="language-plaintext highlighter-rouge notranslate">.</code>.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-instance</span><spanclass="o">=</span>network
</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 master-worker mutual TLS authentication on the nfd-master side. This flag specifies the TLS root certificate that is used for authenticating incoming connections. NFD-Worker side needs to have matching key and cert files configured in order for the incoming requests to be accepted.</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-master <spanclass="nt">-ca-file</span><spanclass="o">=</span>/opt/nfd/ca.crt <spanclass="nt">-cert-file</span><spanclass="o">=</span>/opt/nfd/master.crt <spanclass="nt">-key-file</span><spanclass="o">=</span>/opt/nfd/master.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 master-worker mutual TLS authentication on the nfd-master side. This flag specifies the TLS certificate presented for authenticating outgoing traffic towards nfd-worker.</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-master <spanclass="nt">-cert-file</span><spanclass="o">=</span>/opt/nfd/master.crt <spanclass="nt">-key-file</span><spanclass="o">=</span>/opt/nfd/master.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 master-worker mutual TLS authentication on the nfd-master 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 traffic.</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-master <spanclass="nt">-key-file</span><spanclass="o">=</span>/opt/nfd/master.key <spanclass="nt">-cert-file</span><spanclass="o">=</span>/opt/nfd/master.crt <spanclass="nt">-ca-file</span><spanclass="o">=</span>/opt/nfd/ca.crt
</code></pre></div></div><h3id="-verify-node-name">-verify-node-name</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-verify-node-name</code> flag controls the NodeName based authorization of incoming requests and only has effect when mTLS authentication has been enabled (with <codeclass="language-plaintext highlighter-rouge notranslate">-ca-file</code>, <codeclass="language-plaintext highlighter-rouge notranslate">-cert-file</code> and <codeclass="language-plaintext highlighter-rouge notranslate">-key-file</code>). If enabled, the worker node name of the incoming must match with the CN or a SAN in its TLS certificate. Thus, workers are only able to label the node they are running on (or the node whose certificate they present).</p><p>Node Name based authorization is disabled by default.</p><p>Default: <em>false</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-verify-node-name</span><spanclass="nt">-ca-file</span><spanclass="o">=</span>/opt/nfd/ca.crt <spanclass="se">\</span>
</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 <ahref="/node-feature-discovery/v0.13/usage/custom-resources.html#nodefeature">NodeFeature</a> CRD API for receiving feature requests. This will also automatically disable the gRPC interface.</p><p>Default: false</p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-enable-nodefeature-api</span>
</code></pre></div></div><h3id="-enable-taints">-enable-taints</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-enable-taints</code> flag enables/disables node tainting feature of NFD.</p><p>Default: <em>false</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-enable-taints</span><spanclass="o">=</span><spanclass="nb">true</span>
</code></pre></div></div><h3id="-no-publish">-no-publish</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-no-publish</code> flag disables updates to the Node objects in the Kubernetes API server, making a "dry-run" flag for nfd-master. No Labels, Annotations or ExtendedResources of nodes are updated.</p><p>Default: <em>false</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-no-publish</span>
</code></pre></div></div><h3id="-crd-controller">-crd-controller</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-crd-controller</code> flag specifies whether the NFD CRD API controller is enabled or not. The controller is responsible for processing <ahref="/node-feature-discovery/v0.13/usage/custom-resources.html#nodefeature">NodeFeature</a> and <ahref="/node-feature-discovery/v0.13/usage/custom-resources.html#nodefeaturerule">NodeFeatureRule</a> objects.</p><p>Default: <em>true</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-crd-controller</span><spanclass="o">=</span><spanclass="nb">false</span>
</code></pre></div></div><h3id="-featurerules-controller">-featurerules-controller</h3><p><strong>DEPRECATED</strong>: use <ahref="#-crd-controller"><codeclass="language-plaintext highlighter-rouge notranslate">-crd-controller</code></a> instead.</p><h3id="-label-whitelist">-label-whitelist</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-label-whitelist</code> specifies a regular expression for filtering feature labels based on their name. Each label must match against the given reqular expression in order to be published.</p><p>Note: The regular expression is only matches against the "basename" part of the label, i.e. to the part of the name after ‘/'. The label namespace is omitted.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-label-whitelist</span><spanclass="o">=</span><spanclass="s1">'.*cpuid\.'</span>
</code></pre></div></div><h3id="-extra-label-ns">-extra-label-ns</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-extra-label-ns</code> flag specifies a comma-separated list of allowed feature label namespaces. This option can be used to allow other vendor or application specific namespaces for custom labels from the local and custom feature sources, even though these labels were denied using the <codeclass="language-plaintext highlighter-rouge notranslate">deny-label-ns</code> flag.</p><p>The same namespace control and this flag applies Extended Resources (created with <codeclass="language-plaintext highlighter-rouge notranslate">-resource-labels</code>), too.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-extra-label-ns</span><spanclass="o">=</span>vendor-1.com,vendor-2.io
</code></pre></div></div><h3id="-deny-label-ns">-deny-label-ns</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-deny-label-ns</code> flag specifies a comma-separated list of excluded label namespaces. By default, nfd-master allows creating labels in all namespaces, excluding <codeclass="language-plaintext highlighter-rouge notranslate">kubernetes.io</code> namespace and its sub-namespaces (i.e. <codeclass="language-plaintext highlighter-rouge notranslate">*.kubernetes.io</code>). However, you should note that <codeclass="language-plaintext highlighter-rouge notranslate">kubernetes.io</code> and its sub-namespaces are always denied. For example, <codeclass="language-plaintext highlighter-rouge notranslate">nfd-master -deny-label-ns=""</code> would still disallow <codeclass="language-plaintext highlighter-rouge notranslate">kubernetes.io</code> and <codeclass="language-plaintext highlighter-rouge notranslate">*.kubernetes.io</code>. This option can be used to exclude some vendors or application specific namespaces. Note that the namespaces <codeclass="language-plaintext highlighter-rouge notranslate">feature.node.kubernetes.io</code> and <codeclass="language-plaintext highlighter-rouge notranslate">profile.node.kubernetes.io</code> and their sub-namespaces are always allowed and cannot be denied.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-deny-label-ns</span><spanclass="o">=</span><spanclass="k">*</span>.vendor.com,vendor-2.io
</code></pre></div></div><h3id="-resource-labels">-resource-labels</h3><p><strong>DEPRECATED</strong>: <ahref="/node-feature-discovery/v0.13/usage/custom-resources.html#nodefeaturerule">NodeFeatureRule</a> should be used for managing extended resources in NFD.</p><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-resource-labels</code> flag specifies a comma-separated list of features to be advertised as extended resources instead of labels. Features that have integer values can be published as Extended Resources by listing them in this flag.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-resource-labels</span><spanclass="o">=</span>vendor-1.com/feature-1,vendor-2.io/feature-2
</code></pre></div></div><h3id="-config">-config</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">-config</code> flag specifies the path of the nfd-master configuration file to use.</p><p>Default: /etc/kubernetes/node-feature-discovery/nfd-master.conf</p><p>Example:</p><divclass="language-bash highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code>nfd-master <spanclass="nt">-config</span><spanclass="o">=</span>/opt/nfd/master.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-master <spanclass="nt">-options</span><spanclass="o">=</span><spanclass="s1">'{"noPublish": true}'</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><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"></div><divclass="next"><ahref="/node-feature-discovery/v0.13/reference/worker-commandline-reference.html"class="btn"title="Worker cmdline 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');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: 621"><iclass="fa fa-github"></i> Homepage </a></dd><dd><ahref="https://github.com/kubernetes-sigs/node-feature-discovery/issues"title="Open issues: 21"><iclass="fa fa-question-circle-o"></i> Issue
