Skip to content

feat(helm): update node-feature-discovery ( 0.18.3 ➔ 0.19.0 ) - #805

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-feature-discovery-0.x
Open

feat(helm): update node-feature-discovery ( 0.18.3 ➔ 0.19.0 )#805
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-feature-discovery-0.x

Conversation

@renovate

@renovate renovate Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
node-feature-discovery minor 0.18.30.19.0
node-feature-discovery HelmChart minor 0.18.30.19.0

Release Notes

kubernetes-sigs/node-feature-discovery (node-feature-discovery)

v0.19.0

Compare Source

Highlights
  • Immediate node re-labeling after a node rebuild (#​2545): nfd-master detects a recreated Node via the surviving NodeFeature's owner-reference / pod-UID annotation and re-labels immediately instead of waiting for the periodic reconcile.
  • Configurable NodeFeature owner references: -owner-refs / core.ownerRefs (pod, ds, node; default pod,ds) (#​2545).
  • core.noPublishFeatures to slim published NodeFeature objects (#​2530; whitespace-trim fix #​2535).
  • New x86-64 microarchitecture level labels cpu-cpuid.X86_64_V1..V4 (#​2490).
  • nfd-topology-updater: per-pod lookups served from a node-scoped Pod informer, eliminating high-volume per-pod GETs at scale (#​2509). Requires an RBAC update — see Action Required.
  • nfd-master reconciles only on NodeFeature/NodeFeatureRule/NodeFeatureGroup spec changes (#​2532); MatchInRegexp pattern compilation cached (#​2531).
Action Required / Behavior Changes
  1. nfd-topology-updater RBAC (#​2509): the ClusterRole needs list+watch on pods (was get only). Helm and kustomize manifests ship the update, but deployments that bump only the image will crash-loop with pods is forbidden ... cannot list resource "pods" until the new RBAC is applied.
  2. NodeFeatureRule templates (#​2507): env, expandenv and getHostByName were removed from the available template functions (security hardening). Templates using them now fail to parse (function "env" not defined); the rule is skipped and an error is logged.
  3. Helm worker updateStrategy default (#​2519): now rollingUpdate: {maxUnavailable: "10%"} (was Kubernetes default 1). Note for type: OnDelete users: the chart's default rollingUpdate block is deep-merged into your values; the API server accepts and ignores it (verified on v1.30). Optionally set worker.updateStrategy.rollingUpdate: null for a clean spec.
  4. resyncPeriod (nfd-master): drives both the informer resync and the (new in this release, #​2415) periodic full reconcile that re-applies labels and cleans up drift. Setting it to 0 disables this safety net entirely.
  5. Node-rebuild re-labeling dependency (#​2545): immediate re-label requires pod in -owner-refs (default) or the POD_UID env set on the worker; with ds-only/empty owner refs and no POD_UID, re-labeling falls back to the periodic reconcile interval. -owner-refs=node is unaffected.
Fixes
  • nfd-master: don't remove node labels when the NodeFeature cache is incomplete; add periodic reconciliation to clean up genuinely absent NodeFeatures (#​2415).
  • nfd-master: prevent stop() panic and informer leak on init failure (#​2534).
  • nfd-worker: trim whitespace in comma-separated command-line list values (#​2535).
  • Helm: render post-delete prune job resources at container level so they actually apply (#​2515).
Other
  • Container images cross-compile from $BUILDPLATFORM via tonistiigi/xx (#​2512).
  • Reduced cognitive complexity refactors in nfd-master controller and nfd-worker config (#​2536); nfd-master command-line unit tests (#​2469); codecov upload non-fatal in CI verify (#​2527); template/custom-api input-validation hardening (#​2507).

Configuration

📅 Schedule: (in timezone Asia/Jerusalem)

  • Branch creation
    • "after 2am and before 7am"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions

github-actions Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Argo CD Diff Preview

Summary:

Modified (2):
± infra (+1|-1)
± node-feature-discovery (+7|-12)
infra (kubernetes/bootstrap/infra.yaml)

Application: argocd/node-feature-discovery

   destination:
     namespace: infra
     server: https://kubernetes.default.svc
   info:
   - name: Chart
-    value: node-feature-discovery@0.18.3
+    value: node-feature-discovery@0.19.0
   project: default
   source:
     path: kubernetes/infra/node-feature-discovery/
     repoURL: https://github.com/mpeterson/homelab
     targetRevision: main
node-feature-discovery (kubernetes/infra/node-feature-discovery/app.yaml)

DaemonSet: infra/node-feature-discovery-worker

         app.kubernetes.io/name: node-feature-discovery
         role: worker
     spec:
       containers:
       - args:
-        - -feature-gates=NodeFeatureGroupAPI=false
+        - -owner-refs=pod,ds
         - -port=8080
         command:
         - nfd-worker
         env:
         - name: NODE_NAME
@@ skipped 6 lines (40 -> 45) @@
               fieldPath: metadata.name
         - name: POD_UID
           valueFrom:
             fieldRef:
               fieldPath: metadata.uid
-        image: registry.k8s.io/nfd/node-feature-discovery:v0.18.3
+        image: registry.k8s.io/nfd/node-feature-discovery:v0.19.0
         imagePullPolicy: IfNotPresent
         livenessProbe:
           httpGet:
             path: /healthz
             port: http
@@ skipped 77 lines (58 -> 134) @@
           items:
           - key: nfd-worker.conf
             path: nfd-worker.conf
           name: node-feature-discovery-worker-conf
         name: nfd-worker-conf
+  updateStrategy:
+    rollingUpdate:
+      maxUnavailable: 10%

Deployment: infra/node-feature-discovery-gc

         env:
         - name: NODE_NAME
           valueFrom:
             fieldRef:
               fieldPath: spec.nodeName
-        image: registry.k8s.io/nfd/node-feature-discovery:v0.18.3
+        image: registry.k8s.io/nfd/node-feature-discovery:v0.19.0
         imagePullPolicy: IfNotPresent
         livenessProbe:
           httpGet:
             path: /healthz
             port: http

Deployment: infra/node-feature-discovery-master

                 values:
                 - ""
             weight: 1
       containers:
       - args:
-        - -enable-leader-election
-        - -feature-gates=NodeFeatureGroupAPI=false
         - -port=8080
         command:
         - nfd-master
         env:
         - name: NODE_NAME
           valueFrom:
             fieldRef:
               fieldPath: spec.nodeName
-        image: registry.k8s.io/nfd/node-feature-discovery:v0.18.3
+        image: registry.k8s.io/nfd/node-feature-discovery:v0.19.0
         imagePullPolicy: IfNotPresent
         livenessProbe:
           httpGet:
             path: /healthz
             port: http

ClusterRole: node-feature-discovery-gc

   resources:
   - nodes
   verbs:
   - list
   - watch
-- apiGroups:
-  - ""
-  resources:
-  - nodes/proxy
-  verbs:
-  - get
 - apiGroups:
   - topology.node.k8s.io
   resources:
   - noderesourcetopologies
   verbs:

Stats:
[Applications: 86], [Full Run: 1m42s], [Rendering: 40s], [Cluster: 18s], [Argo CD: 44s]

@renovate
renovate Bot force-pushed the renovate/node-feature-discovery-0.x branch 6 times, most recently from 1975c97 to 571aaec Compare July 22, 2026 03:15
@renovate
renovate Bot force-pushed the renovate/node-feature-discovery-0.x branch 21 times, most recently from 8070a1b to 45e1272 Compare August 7, 2026 04:33
@renovate
renovate Bot force-pushed the renovate/node-feature-discovery-0.x branch 13 times, most recently from faf8640 to 6f220d0 Compare August 19, 2026 22:05
@renovate
renovate Bot force-pushed the renovate/node-feature-discovery-0.x branch 14 times, most recently from 7e71186 to fbd87ea Compare August 27, 2026 02:13
@renovate
renovate Bot force-pushed the renovate/node-feature-discovery-0.x branch 2 times, most recently from 33bf59f to 77a0f95 Compare August 27, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants