Name: node-feature-discovery-master-68cf466d5f-mnmnm Namespace: monitoring Priority: 0 Service Account: node-feature-discovery Node: instance/199.19.213.104 Start Time: Tue, 12 May 2026 11:35:07 +0000 Labels: app.kubernetes.io/instance=node-feature-discovery app.kubernetes.io/name=node-feature-discovery pod-template-hash=68cf466d5f role=master Annotations: Status: Running IP: 10.0.0.34 IPs: IP: 10.0.0.34 Controlled By: ReplicaSet/node-feature-discovery-master-68cf466d5f Containers: master: Container ID: containerd://b75637ae308b75bdc58a26f5028f7a12ec257de59a894f629753c5f3f528d189 Image: harbor.atmosphere.dev/registry.k8s.io/nfd/node-feature-discovery:v0.11.2 Image ID: harbor.atmosphere.dev/registry.k8s.io/nfd/node-feature-discovery@sha256:99112589d9bc5521fb465fd9cba96066a03eb7c904ce2c39c08f6ad709cece56 Port: 8080/TCP Host Port: 0/TCP Command: nfd-master Args: -featurerules-controller=true State: Running Started: Tue, 12 May 2026 11:35:11 +0000 Ready: True Restart Count: 0 Liveness: exec [/usr/bin/grpc_health_probe -addr=:8080] delay=10s timeout=1s period=10s #success=1 #failure=3 Readiness: exec [/usr/bin/grpc_health_probe -addr=:8080] delay=5s timeout=1s period=10s #success=1 #failure=10 Environment: NODE_NAME: (v1:spec.nodeName) Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9tx4k (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-9tx4k: 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: openstack-control-plane=enabled Tolerations: node-role.kubernetes.io/control-plane:NoSchedule node-role.kubernetes.io/master:NoSchedule node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: