Name: node-feature-discovery-gc-6675cbb6d9-dts54 Namespace: monitoring Priority: 0 Service Account: node-feature-discovery-gc Node: instance/199.204.45.65 Start Time: Fri, 17 Apr 2026 01:03:12 +0000 Labels: app.kubernetes.io/instance=node-feature-discovery app.kubernetes.io/name=node-feature-discovery pod-template-hash=6675cbb6d9 role=gc Annotations: Status: Running IP: 10.0.0.82 IPs: IP: 10.0.0.82 Controlled By: ReplicaSet/node-feature-discovery-gc-6675cbb6d9 Containers: gc: Container ID: containerd://0fde0da7f3b452e55cf9f1917a394f68d1fda6ffa448fc7c9b32734ee82f1430 Image: harbor.atmosphere.dev/registry.k8s.io/nfd/node-feature-discovery:v0.15.4 Image ID: harbor.atmosphere.dev/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: Fri, 17 Apr 2026 01:03:13 +0000 Ready: True Restart Count: 0 Environment: NODE_NAME: (v1:spec.nodeName) Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-vwmdp (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-vwmdp: 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 42m default-scheduler Successfully assigned monitoring/node-feature-discovery-gc-6675cbb6d9-dts54 to instance Normal Pulled 42m kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/nfd/node-feature-discovery:v0.15.4" already present on machine Normal Created 42m kubelet Created container gc Normal Started 42m kubelet Started container gc