Name: node-feature-discovery-gc-6675cbb6d9-6ldnz Namespace: monitoring Priority: 0 Service Account: node-feature-discovery-gc Node: instance/199.204.45.44 Start Time: Tue, 12 May 2026 17:10:37 +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.209 IPs: IP: 10.0.0.209 Controlled By: ReplicaSet/node-feature-discovery-gc-6675cbb6d9 Containers: gc: Container ID: containerd://ef5e1ddc6a8ddd4f6820d905c9b2083d3547b562a9f7b60013a3f6598ce96fb1 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: Tue, 12 May 2026 17:10:41 +0000 Ready: True Restart Count: 0 Environment: NODE_NAME: (v1:spec.nodeName) Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-t9qck (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-t9qck: 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: