</code></pre></div></div><h2id="extralabelns">extraLabelNs</h2><p><codeclass="language-plaintext highlighter-rouge notranslate">extraLabelNs</code> specifies a 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">denyLabelNs</code> parameter.</p><p>The same namespace control and this option applies to Extended Resources (created with <codeclass="language-plaintext highlighter-rouge notranslate">resourceLabels</code>), too.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">extraLabelNs</span><spanclass="pi">:</span><spanclass="pi">[</span><spanclass="s2">"</span><spanclass="s">added.ns.io"</span><spanclass="pi">,</span><spanclass="s2">"</span><spanclass="s">added.kubernets.io"</span><spanclass="pi">]</span>
</code></pre></div></div><h2id="denylabelns">denyLabelNs</h2><p><codeclass="language-plaintext highlighter-rouge notranslate">denyLabelNs</code> specifies a 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. 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-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">denyLabelNs</span><spanclass="pi">:</span><spanclass="pi">[</span><spanclass="s2">"</span><spanclass="s">denied.ns.io"</span><spanclass="pi">,</span><spanclass="s2">"</span><spanclass="s">denied.kubernetes.io"</span><spanclass="pi">]</span>
</code></pre></div></div><h2id="resourcelabels">resourceLabels</h2><p><strong>DEPRECATED</strong>: <ahref="/node-feature-discovery/master/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">resourceLabels</code> option specifies a 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 option.</p><p>Default: <em>empty</em></p><p>Example:</p><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">resourceLabels</span><spanclass="pi">:</span><spanclass="pi">[</span><spanclass="s2">"</span><spanclass="s">vendor-1.com/feature-1"</span><spanclass="pi">,</span><spanclass="s2">"</span><spanclass="s">vendor-2.io/feature-2"</span><spanclass="pi">]</span>
</code></pre></div></div><h2id="labelwhitelist">labelWhiteList</h2><p><codeclass="language-plaintext highlighter-rouge notranslate">labelWhiteList</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-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="na">labelWhiteList</span><spanclass="pi">:</span><spanclass="s2">"</span><spanclass="s">foo"</span>
</code></pre></div></div><h3id="resyncperiod">resyncPeriod</h3><p>The <codeclass="language-plaintext highlighter-rouge notranslate">resyncPeriod</code> option specifies the NFD API controller resync period. The resync means nfd-master replaying all NodeFeature and NodeFeatureRule objects, thus effectively re-syncing all nodes in the cluster (i.e. ensuring labels, annotations, extended resources and taints are in place). Only has effect when the <ahref="/node-feature-discovery/master/usage/custom-resources.html#nodefeature">NodeFeature</a> CRD API has been enabled with <ahref="/node-feature-discovery/master/reference/master-commandline-reference.html#-enable-nodefeature-api"><codeclass="language-plaintext highlighter-rouge notranslate">-enable-nodefeature-api</code></a>.</p><p>Default: 1 hour.</p><p>Example:</p><divclass="language-yaml highlighter-rouge notranslate"><divclass="highlight"><preclass="highlight"><code><spanclass="s">resyncPeriod=2h</span>
