Name: node-feature-discovery-gc-6675cbb6d9-n79s7 Namespace: monitoring Priority: 0 Service Account: node-feature-discovery-gc Node: instance/199.204.45.205 Start Time: Tue, 19 May 2026 08:08:46 +0000 Labels: app.kubernetes.io/instance=node-feature-discovery app.kubernetes.io/name=node-feature-discovery pod-template-hash=6675cbb6d9 role=gc Annotations: Status: Pending IP: IPs: Controlled By: ReplicaSet/node-feature-discovery-gc-6675cbb6d9 Containers: gc: Container ID: Image: harbor.atmosphere.dev/registry.k8s.io/nfd/node-feature-discovery:v0.15.4 Image ID: Port: 8081/TCP Host Port: 0/TCP Command: nfd-gc Args: -gc-interval=1h State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Environment: NODE_NAME: (v1:spec.nodeName) Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-jsvvr (ro) Conditions: Type Status Initialized True Ready False ContainersReady False PodScheduled True Volumes: kube-api-access-jsvvr: 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 4m default-scheduler Successfully assigned monitoring/node-feature-discovery-gc-6675cbb6d9-n79s7 to instance Normal Pulling 3m59s kubelet Pulling image "harbor.atmosphere.dev/registry.k8s.io/nfd/node-feature-discovery:v0.15.4"