Name: node-feature-discovery-gc-5c98955555-rg8v9 Namespace: monitoring Priority: 0 Service Account: node-feature-discovery-gc Node: instance/162.253.55.49 Start Time: Thu, 19 Feb 2026 04:00:10 +0000 Labels: app.kubernetes.io/instance=node-feature-discovery app.kubernetes.io/name=node-feature-discovery pod-template-hash=5c98955555 role=gc Annotations: Status: Running IP: 172.24.0.238 IPs: IP: 172.24.0.238 Controlled By: ReplicaSet/node-feature-discovery-gc-5c98955555 Containers: gc: Container ID: containerd://59c5e5a9af23313b05d892fa05882d95b98911242a91915e497671d56f21e8ba Image: registry.k8s.io/nfd/node-feature-discovery:v0.15.4 Image ID: registry.k8s.io/nfd/node-feature-discovery@sha256:21c2681deb07aaa1eac74daef2c576392fcc9c72c87ffd4f43769e8a7cd39ddd Port: 8081/TCP Host Port: 0/TCP Command: nfd-gc Args: -gc-interval=1h State: Running Started: Thu, 19 Feb 2026 04:00:20 +0000 Ready: True Restart Count: 0 Environment: NODE_NAME: (v1:spec.nodeName) Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-v92qz (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-v92qz: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: BestEffort Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 21m default-scheduler Successfully assigned monitoring/node-feature-discovery-gc-5c98955555-rg8v9 to instance Normal Pulling 21m kubelet Pulling image "registry.k8s.io/nfd/node-feature-discovery:v0.15.4" Normal Pulled 21m kubelet Successfully pulled image "registry.k8s.io/nfd/node-feature-discovery:v0.15.4" in 237ms (9.652s including waiting) Normal Created 21m kubelet Created container gc Normal Started 21m kubelet Started container gc