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