Name: node-feature-discovery-gc-5c98955555-kcn5f Namespace: monitoring Priority: 0 Service Account: node-feature-discovery-gc Node: instance/199.204.45.25 Start Time: Wed, 25 Feb 2026 03:22:42 +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: 10.0.0.21 IPs: IP: 10.0.0.21 Controlled By: ReplicaSet/node-feature-discovery-gc-5c98955555 Containers: gc: Container ID: containerd://f0b56c52781600e29b3f994b21909d0502a7e08f53f62b730b1e84735383cb5e 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: Wed, 25 Feb 2026 03:22:47 +0000 Ready: True Restart Count: 0 Environment: NODE_NAME: (v1:spec.nodeName) Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-fz5db (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-fz5db: 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 13m default-scheduler Successfully assigned monitoring/node-feature-discovery-gc-5c98955555-kcn5f to instance Normal Pulling 13m kubelet Pulling image "registry.k8s.io/nfd/node-feature-discovery:v0.15.4" Normal Pulled 13m kubelet Successfully pulled image "registry.k8s.io/nfd/node-feature-discovery:v0.15.4" in 262ms (4.888s including waiting) Normal Created 13m kubelet Created container gc Normal Started 13m kubelet Started container gc