I0507 22:15:53.587132 21 test_context.go:429] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready I0507 22:15:53.587245 21 e2e.go:129] Starting e2e run "5335c2db-b8ec-4e3a-9d8c-722cb7be471b" on Ginkgo node 1 {"msg":"Test Suite starting","total":17,"completed":0,"skipped":0,"failed":0} Running Suite: Kubernetes e2e suite =================================== Random Seed: 1620425752 - Will randomize all specs Will run 17 of 5484 specs May 7 22:15:53.644: INFO: >>> kubeConfig: /root/.kube/config May 7 22:15:53.649: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable May 7 22:15:53.677: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready May 7 22:15:53.751: INFO: The status of Pod cmk-init-discover-node1-krbjn is Succeeded, skipping waiting May 7 22:15:53.751: INFO: The status of Pod cmk-init-discover-node2-kd9gg is Succeeded, skipping waiting May 7 22:15:53.751: INFO: 40 / 42 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) May 7 22:15:53.751: INFO: expected 8 pod replicas in namespace 'kube-system', 8 are Running and Ready. May 7 22:15:53.751: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start May 7 22:15:53.766: INFO: 2 / 2 pods ready in namespace 'kube-system' in daemonset 'cmk' (0 seconds elapsed) May 7 22:15:53.766: INFO: 5 / 5 pods ready in namespace 'kube-system' in daemonset 'kube-flannel' (0 seconds elapsed) May 7 22:15:53.766: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-flannel-ds-arm' (0 seconds elapsed) May 7 22:15:53.766: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-flannel-ds-arm64' (0 seconds elapsed) May 7 22:15:53.766: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-flannel-ds-ppc64le' (0 seconds elapsed) May 7 22:15:53.766: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-flannel-ds-s390x' (0 seconds elapsed) May 7 22:15:53.766: INFO: 5 / 5 pods ready in namespace 'kube-system' in daemonset 'kube-multus-ds-amd64' (0 seconds elapsed) May 7 22:15:53.766: INFO: 5 / 5 pods ready in namespace 'kube-system' in daemonset 'kube-proxy' (0 seconds elapsed) May 7 22:15:53.766: INFO: 2 / 2 pods ready in namespace 'kube-system' in daemonset 'node-feature-discovery-worker' (0 seconds elapsed) May 7 22:15:53.766: INFO: 2 / 2 pods ready in namespace 'kube-system' in daemonset 'sriov-net-dp-kube-sriov-device-plugin-amd64' (0 seconds elapsed) May 7 22:15:53.766: INFO: e2e test version: v1.19.10 May 7 22:15:53.767: INFO: kube-apiserver version: v1.19.8 May 7 22:15:53.767: INFO: >>> kubeConfig: /root/.kube/config May 7 22:15:53.773: INFO: Cluster IP family: ipv4 SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:15:53.775: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename namespaces May 7 22:15:53.796: INFO: Found PodSecurityPolicies; testing pod creation to see if PodSecurityPolicy is enabled May 7 22:15:53.799: INFO: Error creating dryrun pod; assuming PodSecurityPolicy is disabled: admission webhook "cmk.intel.com" does not support dry run STEP: Waiting for a default service account to be provisioned in namespace [It] should ensure that all services are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Creating a test namespace STEP: Waiting for a default service account to be provisioned in namespace STEP: Creating a service in the namespace STEP: Deleting the namespace STEP: Waiting for the namespace to be removed. STEP: Recreating the namespace STEP: Verifying there is no service in the namespace [AfterEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:15:59.861: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "namespaces-5680" for this suite. STEP: Destroying namespace "nsdeletetest-2332" for this suite. May 7 22:15:59.870: INFO: Namespace nsdeletetest-2332 was already deleted STEP: Destroying namespace "nsdeletetest-7434" for this suite. • [SLOW TEST:6.101 seconds] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23 should ensure that all services are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted [Conformance]","total":17,"completed":1,"skipped":113,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:15:59.886: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:134 [It] should run and stop complex daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:15:59.921: INFO: Creating daemon "daemon-set" with a node selector STEP: Initially, daemon pods should not be running on any nodes. May 7 22:15:59.928: INFO: Number of nodes with available pods: 0 May 7 22:15:59.928: INFO: Number of running nodes: 0, number of available pods: 0 STEP: Change node label to blue, check that daemon pod is launched. May 7 22:15:59.943: INFO: Number of nodes with available pods: 0 May 7 22:15:59.943: INFO: Node node1 is running more than one daemon pod May 7 22:16:00.946: INFO: Number of nodes with available pods: 0 May 7 22:16:00.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:01.948: INFO: Number of nodes with available pods: 0 May 7 22:16:01.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:02.947: INFO: Number of nodes with available pods: 0 May 7 22:16:02.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:03.947: INFO: Number of nodes with available pods: 0 May 7 22:16:03.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:04.947: INFO: Number of nodes with available pods: 0 May 7 22:16:04.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:05.946: INFO: Number of nodes with available pods: 0 May 7 22:16:05.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:06.947: INFO: Number of nodes with available pods: 0 May 7 22:16:06.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:07.947: INFO: Number of nodes with available pods: 0 May 7 22:16:07.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:08.947: INFO: Number of nodes with available pods: 0 May 7 22:16:08.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:09.947: INFO: Number of nodes with available pods: 0 May 7 22:16:09.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:10.948: INFO: Number of nodes with available pods: 0 May 7 22:16:10.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:11.949: INFO: Number of nodes with available pods: 0 May 7 22:16:11.949: INFO: Node node1 is running more than one daemon pod May 7 22:16:12.945: INFO: Number of nodes with available pods: 0 May 7 22:16:12.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:13.948: INFO: Number of nodes with available pods: 0 May 7 22:16:13.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:14.949: INFO: Number of nodes with available pods: 0 May 7 22:16:14.949: INFO: Node node1 is running more than one daemon pod May 7 22:16:15.946: INFO: Number of nodes with available pods: 0 May 7 22:16:15.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:16.947: INFO: Number of nodes with available pods: 0 May 7 22:16:16.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:17.948: INFO: Number of nodes with available pods: 0 May 7 22:16:17.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:18.946: INFO: Number of nodes with available pods: 0 May 7 22:16:18.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:19.946: INFO: Number of nodes with available pods: 0 May 7 22:16:19.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:20.946: INFO: Number of nodes with available pods: 0 May 7 22:16:20.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:21.947: INFO: Number of nodes with available pods: 0 May 7 22:16:21.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:22.947: INFO: Number of nodes with available pods: 0 May 7 22:16:22.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:23.947: INFO: Number of nodes with available pods: 0 May 7 22:16:23.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:24.946: INFO: Number of nodes with available pods: 0 May 7 22:16:24.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:25.948: INFO: Number of nodes with available pods: 0 May 7 22:16:25.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:26.946: INFO: Number of nodes with available pods: 0 May 7 22:16:26.946: INFO: Node node1 is running more than one daemon pod May 7 22:16:27.947: INFO: Number of nodes with available pods: 0 May 7 22:16:27.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:28.947: INFO: Number of nodes with available pods: 0 May 7 22:16:28.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:29.947: INFO: Number of nodes with available pods: 0 May 7 22:16:29.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:30.947: INFO: Number of nodes with available pods: 0 May 7 22:16:30.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:31.948: INFO: Number of nodes with available pods: 0 May 7 22:16:31.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:32.947: INFO: Number of nodes with available pods: 0 May 7 22:16:32.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:33.948: INFO: Number of nodes with available pods: 0 May 7 22:16:33.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:34.948: INFO: Number of nodes with available pods: 0 May 7 22:16:34.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:35.949: INFO: Number of nodes with available pods: 0 May 7 22:16:35.949: INFO: Node node1 is running more than one daemon pod May 7 22:16:36.948: INFO: Number of nodes with available pods: 0 May 7 22:16:36.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:37.947: INFO: Number of nodes with available pods: 0 May 7 22:16:37.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:38.947: INFO: Number of nodes with available pods: 0 May 7 22:16:38.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:39.947: INFO: Number of nodes with available pods: 0 May 7 22:16:39.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:40.948: INFO: Number of nodes with available pods: 0 May 7 22:16:40.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:41.947: INFO: Number of nodes with available pods: 0 May 7 22:16:41.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:42.947: INFO: Number of nodes with available pods: 0 May 7 22:16:42.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:43.947: INFO: Number of nodes with available pods: 0 May 7 22:16:43.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:44.949: INFO: Number of nodes with available pods: 0 May 7 22:16:44.949: INFO: Node node1 is running more than one daemon pod May 7 22:16:45.948: INFO: Number of nodes with available pods: 0 May 7 22:16:45.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:46.947: INFO: Number of nodes with available pods: 0 May 7 22:16:46.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:47.947: INFO: Number of nodes with available pods: 0 May 7 22:16:47.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:48.948: INFO: Number of nodes with available pods: 0 May 7 22:16:48.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:49.948: INFO: Number of nodes with available pods: 0 May 7 22:16:49.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:50.947: INFO: Number of nodes with available pods: 0 May 7 22:16:50.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:51.947: INFO: Number of nodes with available pods: 0 May 7 22:16:51.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:52.947: INFO: Number of nodes with available pods: 0 May 7 22:16:52.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:53.948: INFO: Number of nodes with available pods: 0 May 7 22:16:53.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:54.949: INFO: Number of nodes with available pods: 0 May 7 22:16:54.949: INFO: Node node1 is running more than one daemon pod May 7 22:16:55.946: INFO: Number of nodes with available pods: 0 May 7 22:16:55.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:56.949: INFO: Number of nodes with available pods: 0 May 7 22:16:56.949: INFO: Node node1 is running more than one daemon pod May 7 22:16:57.948: INFO: Number of nodes with available pods: 0 May 7 22:16:57.948: INFO: Node node1 is running more than one daemon pod May 7 22:16:58.947: INFO: Number of nodes with available pods: 0 May 7 22:16:58.947: INFO: Node node1 is running more than one daemon pod May 7 22:16:59.947: INFO: Number of nodes with available pods: 0 May 7 22:16:59.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:00.948: INFO: Number of nodes with available pods: 0 May 7 22:17:00.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:01.948: INFO: Number of nodes with available pods: 0 May 7 22:17:01.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:02.948: INFO: Number of nodes with available pods: 0 May 7 22:17:02.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:03.947: INFO: Number of nodes with available pods: 0 May 7 22:17:03.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:04.948: INFO: Number of nodes with available pods: 0 May 7 22:17:04.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:05.947: INFO: Number of nodes with available pods: 0 May 7 22:17:05.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:06.946: INFO: Number of nodes with available pods: 0 May 7 22:17:06.946: INFO: Node node1 is running more than one daemon pod May 7 22:17:07.948: INFO: Number of nodes with available pods: 0 May 7 22:17:07.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:08.947: INFO: Number of nodes with available pods: 0 May 7 22:17:08.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:09.949: INFO: Number of nodes with available pods: 0 May 7 22:17:09.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:10.949: INFO: Number of nodes with available pods: 0 May 7 22:17:10.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:11.949: INFO: Number of nodes with available pods: 0 May 7 22:17:11.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:12.947: INFO: Number of nodes with available pods: 0 May 7 22:17:12.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:13.947: INFO: Number of nodes with available pods: 0 May 7 22:17:13.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:14.949: INFO: Number of nodes with available pods: 0 May 7 22:17:14.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:15.947: INFO: Number of nodes with available pods: 0 May 7 22:17:15.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:16.947: INFO: Number of nodes with available pods: 0 May 7 22:17:16.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:17.947: INFO: Number of nodes with available pods: 0 May 7 22:17:17.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:18.947: INFO: Number of nodes with available pods: 0 May 7 22:17:18.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:19.947: INFO: Number of nodes with available pods: 0 May 7 22:17:19.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:20.949: INFO: Number of nodes with available pods: 0 May 7 22:17:20.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:21.948: INFO: Number of nodes with available pods: 0 May 7 22:17:21.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:22.948: INFO: Number of nodes with available pods: 0 May 7 22:17:22.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:23.947: INFO: Number of nodes with available pods: 0 May 7 22:17:23.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:24.949: INFO: Number of nodes with available pods: 0 May 7 22:17:24.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:25.950: INFO: Number of nodes with available pods: 0 May 7 22:17:25.950: INFO: Node node1 is running more than one daemon pod May 7 22:17:26.947: INFO: Number of nodes with available pods: 0 May 7 22:17:26.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:27.947: INFO: Number of nodes with available pods: 0 May 7 22:17:27.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:28.948: INFO: Number of nodes with available pods: 0 May 7 22:17:28.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:29.947: INFO: Number of nodes with available pods: 0 May 7 22:17:29.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:30.949: INFO: Number of nodes with available pods: 0 May 7 22:17:30.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:31.948: INFO: Number of nodes with available pods: 0 May 7 22:17:31.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:32.948: INFO: Number of nodes with available pods: 0 May 7 22:17:32.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:33.946: INFO: Number of nodes with available pods: 0 May 7 22:17:33.946: INFO: Node node1 is running more than one daemon pod May 7 22:17:34.948: INFO: Number of nodes with available pods: 0 May 7 22:17:34.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:35.949: INFO: Number of nodes with available pods: 0 May 7 22:17:35.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:36.948: INFO: Number of nodes with available pods: 0 May 7 22:17:36.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:37.947: INFO: Number of nodes with available pods: 0 May 7 22:17:37.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:38.947: INFO: Number of nodes with available pods: 0 May 7 22:17:38.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:39.950: INFO: Number of nodes with available pods: 0 May 7 22:17:39.950: INFO: Node node1 is running more than one daemon pod May 7 22:17:40.948: INFO: Number of nodes with available pods: 0 May 7 22:17:40.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:41.947: INFO: Number of nodes with available pods: 0 May 7 22:17:41.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:42.948: INFO: Number of nodes with available pods: 0 May 7 22:17:42.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:43.947: INFO: Number of nodes with available pods: 0 May 7 22:17:43.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:44.949: INFO: Number of nodes with available pods: 0 May 7 22:17:44.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:45.949: INFO: Number of nodes with available pods: 0 May 7 22:17:45.949: INFO: Node node1 is running more than one daemon pod May 7 22:17:46.947: INFO: Number of nodes with available pods: 0 May 7 22:17:46.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:47.947: INFO: Number of nodes with available pods: 0 May 7 22:17:47.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:48.947: INFO: Number of nodes with available pods: 0 May 7 22:17:48.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:49.946: INFO: Number of nodes with available pods: 0 May 7 22:17:49.946: INFO: Node node1 is running more than one daemon pod May 7 22:17:50.947: INFO: Number of nodes with available pods: 0 May 7 22:17:50.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:51.948: INFO: Number of nodes with available pods: 0 May 7 22:17:51.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:52.947: INFO: Number of nodes with available pods: 0 May 7 22:17:52.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:53.947: INFO: Number of nodes with available pods: 0 May 7 22:17:53.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:54.950: INFO: Number of nodes with available pods: 0 May 7 22:17:54.950: INFO: Node node1 is running more than one daemon pod May 7 22:17:55.948: INFO: Number of nodes with available pods: 0 May 7 22:17:55.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:56.947: INFO: Number of nodes with available pods: 0 May 7 22:17:56.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:57.948: INFO: Number of nodes with available pods: 0 May 7 22:17:57.948: INFO: Node node1 is running more than one daemon pod May 7 22:17:58.947: INFO: Number of nodes with available pods: 0 May 7 22:17:58.947: INFO: Node node1 is running more than one daemon pod May 7 22:17:59.947: INFO: Number of nodes with available pods: 0 May 7 22:17:59.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:00.947: INFO: Number of nodes with available pods: 0 May 7 22:18:00.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:01.946: INFO: Number of nodes with available pods: 0 May 7 22:18:01.946: INFO: Node node1 is running more than one daemon pod May 7 22:18:02.947: INFO: Number of nodes with available pods: 0 May 7 22:18:02.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:03.948: INFO: Number of nodes with available pods: 0 May 7 22:18:03.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:04.949: INFO: Number of nodes with available pods: 0 May 7 22:18:04.949: INFO: Node node1 is running more than one daemon pod May 7 22:18:05.948: INFO: Number of nodes with available pods: 0 May 7 22:18:05.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:06.947: INFO: Number of nodes with available pods: 0 May 7 22:18:06.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:07.947: INFO: Number of nodes with available pods: 0 May 7 22:18:07.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:08.947: INFO: Number of nodes with available pods: 0 May 7 22:18:08.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:09.947: INFO: Number of nodes with available pods: 0 May 7 22:18:09.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:10.947: INFO: Number of nodes with available pods: 0 May 7 22:18:10.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:11.947: INFO: Number of nodes with available pods: 0 May 7 22:18:11.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:12.947: INFO: Number of nodes with available pods: 0 May 7 22:18:12.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:13.946: INFO: Number of nodes with available pods: 0 May 7 22:18:13.946: INFO: Node node1 is running more than one daemon pod May 7 22:18:14.947: INFO: Number of nodes with available pods: 0 May 7 22:18:14.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:15.949: INFO: Number of nodes with available pods: 0 May 7 22:18:15.949: INFO: Node node1 is running more than one daemon pod May 7 22:18:16.947: INFO: Number of nodes with available pods: 0 May 7 22:18:16.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:17.947: INFO: Number of nodes with available pods: 0 May 7 22:18:17.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:18.947: INFO: Number of nodes with available pods: 0 May 7 22:18:18.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:19.947: INFO: Number of nodes with available pods: 0 May 7 22:18:19.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:20.948: INFO: Number of nodes with available pods: 0 May 7 22:18:20.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:21.947: INFO: Number of nodes with available pods: 0 May 7 22:18:21.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:22.947: INFO: Number of nodes with available pods: 0 May 7 22:18:22.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:23.947: INFO: Number of nodes with available pods: 0 May 7 22:18:23.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:24.949: INFO: Number of nodes with available pods: 0 May 7 22:18:24.949: INFO: Node node1 is running more than one daemon pod May 7 22:18:25.947: INFO: Number of nodes with available pods: 0 May 7 22:18:25.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:26.949: INFO: Number of nodes with available pods: 0 May 7 22:18:26.949: INFO: Node node1 is running more than one daemon pod May 7 22:18:27.947: INFO: Number of nodes with available pods: 0 May 7 22:18:27.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:28.946: INFO: Number of nodes with available pods: 0 May 7 22:18:28.946: INFO: Node node1 is running more than one daemon pod May 7 22:18:29.948: INFO: Number of nodes with available pods: 0 May 7 22:18:29.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:30.946: INFO: Number of nodes with available pods: 0 May 7 22:18:30.946: INFO: Node node1 is running more than one daemon pod May 7 22:18:31.948: INFO: Number of nodes with available pods: 0 May 7 22:18:31.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:32.947: INFO: Number of nodes with available pods: 0 May 7 22:18:32.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:33.946: INFO: Number of nodes with available pods: 0 May 7 22:18:33.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:34.947: INFO: Number of nodes with available pods: 0 May 7 22:18:34.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:35.949: INFO: Number of nodes with available pods: 0 May 7 22:18:35.949: INFO: Node node1 is running more than one daemon pod May 7 22:18:36.947: INFO: Number of nodes with available pods: 0 May 7 22:18:36.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:37.947: INFO: Number of nodes with available pods: 0 May 7 22:18:37.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:38.947: INFO: Number of nodes with available pods: 0 May 7 22:18:38.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:39.947: INFO: Number of nodes with available pods: 0 May 7 22:18:39.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:40.947: INFO: Number of nodes with available pods: 0 May 7 22:18:40.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:41.947: INFO: Number of nodes with available pods: 0 May 7 22:18:41.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:42.947: INFO: Number of nodes with available pods: 0 May 7 22:18:42.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:43.947: INFO: Number of nodes with available pods: 0 May 7 22:18:43.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:44.949: INFO: Number of nodes with available pods: 0 May 7 22:18:44.949: INFO: Node node1 is running more than one daemon pod May 7 22:18:45.947: INFO: Number of nodes with available pods: 0 May 7 22:18:45.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:46.947: INFO: Number of nodes with available pods: 0 May 7 22:18:46.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:47.948: INFO: Number of nodes with available pods: 0 May 7 22:18:47.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:48.947: INFO: Number of nodes with available pods: 0 May 7 22:18:48.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:49.948: INFO: Number of nodes with available pods: 0 May 7 22:18:49.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:50.948: INFO: Number of nodes with available pods: 0 May 7 22:18:50.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:51.948: INFO: Number of nodes with available pods: 0 May 7 22:18:51.948: INFO: Node node1 is running more than one daemon pod May 7 22:18:52.947: INFO: Number of nodes with available pods: 0 May 7 22:18:52.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:53.947: INFO: Number of nodes with available pods: 0 May 7 22:18:53.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:54.949: INFO: Number of nodes with available pods: 0 May 7 22:18:54.949: INFO: Node node1 is running more than one daemon pod May 7 22:18:55.947: INFO: Number of nodes with available pods: 0 May 7 22:18:55.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:56.946: INFO: Number of nodes with available pods: 0 May 7 22:18:56.946: INFO: Node node1 is running more than one daemon pod May 7 22:18:57.947: INFO: Number of nodes with available pods: 0 May 7 22:18:57.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:58.947: INFO: Number of nodes with available pods: 0 May 7 22:18:58.947: INFO: Node node1 is running more than one daemon pod May 7 22:18:59.947: INFO: Number of nodes with available pods: 0 May 7 22:18:59.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:00.949: INFO: Number of nodes with available pods: 0 May 7 22:19:00.949: INFO: Node node1 is running more than one daemon pod May 7 22:19:01.947: INFO: Number of nodes with available pods: 0 May 7 22:19:01.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:02.947: INFO: Number of nodes with available pods: 0 May 7 22:19:02.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:03.947: INFO: Number of nodes with available pods: 0 May 7 22:19:03.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:04.949: INFO: Number of nodes with available pods: 0 May 7 22:19:04.949: INFO: Node node1 is running more than one daemon pod May 7 22:19:05.947: INFO: Number of nodes with available pods: 0 May 7 22:19:05.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:06.947: INFO: Number of nodes with available pods: 0 May 7 22:19:06.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:07.947: INFO: Number of nodes with available pods: 0 May 7 22:19:07.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:08.946: INFO: Number of nodes with available pods: 0 May 7 22:19:08.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:09.947: INFO: Number of nodes with available pods: 0 May 7 22:19:09.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:10.948: INFO: Number of nodes with available pods: 0 May 7 22:19:10.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:11.947: INFO: Number of nodes with available pods: 0 May 7 22:19:11.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:12.946: INFO: Number of nodes with available pods: 0 May 7 22:19:12.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:13.947: INFO: Number of nodes with available pods: 0 May 7 22:19:13.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:14.948: INFO: Number of nodes with available pods: 0 May 7 22:19:14.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:15.948: INFO: Number of nodes with available pods: 0 May 7 22:19:15.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:16.948: INFO: Number of nodes with available pods: 0 May 7 22:19:16.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:17.947: INFO: Number of nodes with available pods: 0 May 7 22:19:17.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:18.947: INFO: Number of nodes with available pods: 0 May 7 22:19:18.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:19.947: INFO: Number of nodes with available pods: 0 May 7 22:19:19.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:20.948: INFO: Number of nodes with available pods: 0 May 7 22:19:20.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:21.947: INFO: Number of nodes with available pods: 0 May 7 22:19:21.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:22.948: INFO: Number of nodes with available pods: 0 May 7 22:19:22.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:23.949: INFO: Number of nodes with available pods: 0 May 7 22:19:23.949: INFO: Node node1 is running more than one daemon pod May 7 22:19:24.946: INFO: Number of nodes with available pods: 0 May 7 22:19:24.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:25.947: INFO: Number of nodes with available pods: 0 May 7 22:19:25.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:26.946: INFO: Number of nodes with available pods: 0 May 7 22:19:26.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:27.947: INFO: Number of nodes with available pods: 0 May 7 22:19:27.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:28.947: INFO: Number of nodes with available pods: 0 May 7 22:19:28.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:29.947: INFO: Number of nodes with available pods: 0 May 7 22:19:29.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:30.949: INFO: Number of nodes with available pods: 0 May 7 22:19:30.949: INFO: Node node1 is running more than one daemon pod May 7 22:19:31.947: INFO: Number of nodes with available pods: 0 May 7 22:19:31.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:32.947: INFO: Number of nodes with available pods: 0 May 7 22:19:32.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:33.947: INFO: Number of nodes with available pods: 0 May 7 22:19:33.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:34.950: INFO: Number of nodes with available pods: 0 May 7 22:19:34.950: INFO: Node node1 is running more than one daemon pod May 7 22:19:35.946: INFO: Number of nodes with available pods: 0 May 7 22:19:35.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:36.950: INFO: Number of nodes with available pods: 0 May 7 22:19:36.950: INFO: Node node1 is running more than one daemon pod May 7 22:19:37.947: INFO: Number of nodes with available pods: 0 May 7 22:19:37.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:38.947: INFO: Number of nodes with available pods: 0 May 7 22:19:38.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:39.948: INFO: Number of nodes with available pods: 0 May 7 22:19:39.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:40.946: INFO: Number of nodes with available pods: 0 May 7 22:19:40.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:41.946: INFO: Number of nodes with available pods: 0 May 7 22:19:41.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:42.947: INFO: Number of nodes with available pods: 0 May 7 22:19:42.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:43.946: INFO: Number of nodes with available pods: 0 May 7 22:19:43.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:44.947: INFO: Number of nodes with available pods: 0 May 7 22:19:44.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:45.947: INFO: Number of nodes with available pods: 0 May 7 22:19:45.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:46.947: INFO: Number of nodes with available pods: 0 May 7 22:19:46.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:47.948: INFO: Number of nodes with available pods: 0 May 7 22:19:47.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:48.946: INFO: Number of nodes with available pods: 0 May 7 22:19:48.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:49.947: INFO: Number of nodes with available pods: 0 May 7 22:19:49.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:50.947: INFO: Number of nodes with available pods: 0 May 7 22:19:50.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:51.947: INFO: Number of nodes with available pods: 0 May 7 22:19:51.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:52.947: INFO: Number of nodes with available pods: 0 May 7 22:19:52.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:53.946: INFO: Number of nodes with available pods: 0 May 7 22:19:53.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:54.949: INFO: Number of nodes with available pods: 0 May 7 22:19:54.949: INFO: Node node1 is running more than one daemon pod May 7 22:19:55.949: INFO: Number of nodes with available pods: 0 May 7 22:19:55.950: INFO: Node node1 is running more than one daemon pod May 7 22:19:56.947: INFO: Number of nodes with available pods: 0 May 7 22:19:56.947: INFO: Node node1 is running more than one daemon pod May 7 22:19:57.946: INFO: Number of nodes with available pods: 0 May 7 22:19:57.946: INFO: Node node1 is running more than one daemon pod May 7 22:19:58.948: INFO: Number of nodes with available pods: 0 May 7 22:19:58.948: INFO: Node node1 is running more than one daemon pod May 7 22:19:59.949: INFO: Number of nodes with available pods: 0 May 7 22:19:59.949: INFO: Node node1 is running more than one daemon pod May 7 22:20:00.949: INFO: Number of nodes with available pods: 0 May 7 22:20:00.949: INFO: Node node1 is running more than one daemon pod May 7 22:20:01.946: INFO: Number of nodes with available pods: 0 May 7 22:20:01.946: INFO: Node node1 is running more than one daemon pod May 7 22:20:02.947: INFO: Number of nodes with available pods: 0 May 7 22:20:02.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:03.947: INFO: Number of nodes with available pods: 0 May 7 22:20:03.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:04.948: INFO: Number of nodes with available pods: 0 May 7 22:20:04.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:05.947: INFO: Number of nodes with available pods: 0 May 7 22:20:05.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:06.947: INFO: Number of nodes with available pods: 0 May 7 22:20:06.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:07.948: INFO: Number of nodes with available pods: 0 May 7 22:20:07.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:08.947: INFO: Number of nodes with available pods: 0 May 7 22:20:08.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:09.947: INFO: Number of nodes with available pods: 0 May 7 22:20:09.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:10.948: INFO: Number of nodes with available pods: 0 May 7 22:20:10.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:11.947: INFO: Number of nodes with available pods: 0 May 7 22:20:11.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:12.947: INFO: Number of nodes with available pods: 0 May 7 22:20:12.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:13.947: INFO: Number of nodes with available pods: 0 May 7 22:20:13.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:14.948: INFO: Number of nodes with available pods: 0 May 7 22:20:14.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:15.947: INFO: Number of nodes with available pods: 0 May 7 22:20:15.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:16.948: INFO: Number of nodes with available pods: 0 May 7 22:20:16.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:17.947: INFO: Number of nodes with available pods: 0 May 7 22:20:17.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:18.947: INFO: Number of nodes with available pods: 0 May 7 22:20:18.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:19.947: INFO: Number of nodes with available pods: 0 May 7 22:20:19.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:20.946: INFO: Number of nodes with available pods: 0 May 7 22:20:20.946: INFO: Node node1 is running more than one daemon pod May 7 22:20:21.946: INFO: Number of nodes with available pods: 0 May 7 22:20:21.946: INFO: Node node1 is running more than one daemon pod May 7 22:20:22.949: INFO: Number of nodes with available pods: 0 May 7 22:20:22.949: INFO: Node node1 is running more than one daemon pod May 7 22:20:23.947: INFO: Number of nodes with available pods: 0 May 7 22:20:23.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:24.947: INFO: Number of nodes with available pods: 0 May 7 22:20:24.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:25.948: INFO: Number of nodes with available pods: 0 May 7 22:20:25.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:26.948: INFO: Number of nodes with available pods: 0 May 7 22:20:26.949: INFO: Node node1 is running more than one daemon pod May 7 22:20:27.947: INFO: Number of nodes with available pods: 0 May 7 22:20:27.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:28.947: INFO: Number of nodes with available pods: 0 May 7 22:20:28.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:29.947: INFO: Number of nodes with available pods: 0 May 7 22:20:29.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:30.947: INFO: Number of nodes with available pods: 0 May 7 22:20:30.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:31.947: INFO: Number of nodes with available pods: 0 May 7 22:20:31.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:32.948: INFO: Number of nodes with available pods: 0 May 7 22:20:32.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:33.947: INFO: Number of nodes with available pods: 0 May 7 22:20:33.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:34.948: INFO: Number of nodes with available pods: 0 May 7 22:20:34.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:35.948: INFO: Number of nodes with available pods: 0 May 7 22:20:35.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:36.948: INFO: Number of nodes with available pods: 0 May 7 22:20:36.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:37.946: INFO: Number of nodes with available pods: 0 May 7 22:20:37.946: INFO: Node node1 is running more than one daemon pod May 7 22:20:38.947: INFO: Number of nodes with available pods: 0 May 7 22:20:38.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:39.949: INFO: Number of nodes with available pods: 0 May 7 22:20:39.949: INFO: Node node1 is running more than one daemon pod May 7 22:20:40.948: INFO: Number of nodes with available pods: 0 May 7 22:20:40.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:41.947: INFO: Number of nodes with available pods: 0 May 7 22:20:41.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:42.947: INFO: Number of nodes with available pods: 0 May 7 22:20:42.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:43.947: INFO: Number of nodes with available pods: 0 May 7 22:20:43.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:44.949: INFO: Number of nodes with available pods: 0 May 7 22:20:44.949: INFO: Node node1 is running more than one daemon pod May 7 22:20:45.947: INFO: Number of nodes with available pods: 0 May 7 22:20:45.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:46.947: INFO: Number of nodes with available pods: 0 May 7 22:20:46.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:47.947: INFO: Number of nodes with available pods: 0 May 7 22:20:47.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:48.947: INFO: Number of nodes with available pods: 0 May 7 22:20:48.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:49.947: INFO: Number of nodes with available pods: 0 May 7 22:20:49.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:50.946: INFO: Number of nodes with available pods: 0 May 7 22:20:50.946: INFO: Node node1 is running more than one daemon pod May 7 22:20:51.948: INFO: Number of nodes with available pods: 0 May 7 22:20:51.948: INFO: Node node1 is running more than one daemon pod May 7 22:20:52.947: INFO: Number of nodes with available pods: 0 May 7 22:20:52.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:53.946: INFO: Number of nodes with available pods: 0 May 7 22:20:53.946: INFO: Node node1 is running more than one daemon pod May 7 22:20:54.946: INFO: Number of nodes with available pods: 0 May 7 22:20:54.946: INFO: Node node1 is running more than one daemon pod May 7 22:20:55.947: INFO: Number of nodes with available pods: 0 May 7 22:20:55.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:56.949: INFO: Number of nodes with available pods: 0 May 7 22:20:56.949: INFO: Node node1 is running more than one daemon pod May 7 22:20:57.947: INFO: Number of nodes with available pods: 0 May 7 22:20:57.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:58.946: INFO: Number of nodes with available pods: 0 May 7 22:20:58.946: INFO: Node node1 is running more than one daemon pod May 7 22:20:59.947: INFO: Number of nodes with available pods: 0 May 7 22:20:59.947: INFO: Node node1 is running more than one daemon pod May 7 22:20:59.949: INFO: Number of nodes with available pods: 0 May 7 22:20:59.950: INFO: Node node1 is running more than one daemon pod May 7 22:20:59.950: FAIL: error waiting for daemon pods to be running on new nodes Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/apps.glob..func3.4() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:203 +0x84e k8s.io/kubernetes/test/e2e.RunE2ETests(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x345 k8s.io/kubernetes/test/e2e.TestE2E(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:145 +0x2b testing.tRunner(0xc00211a180, 0x4de37a0) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:100 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-3254, will wait for the garbage collector to delete the pods May 7 22:21:00.013: INFO: Deleting DaemonSet.extensions daemon-set took: 6.040896ms May 7 22:21:00.713: INFO: Terminating DaemonSet.extensions daemon-set pods took: 700.260944ms May 7 22:21:02.316: INFO: Number of nodes with available pods: 0 May 7 22:21:02.316: INFO: Number of running nodes: 0, number of available pods: 0 May 7 22:21:02.323: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"selfLink":"/apis/apps/v1/namespaces/daemonsets-3254/daemonsets","resourceVersion":"51395"},"items":null} May 7 22:21:02.325: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"selfLink":"/api/v1/namespaces/daemonsets-3254/pods","resourceVersion":"51395"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 STEP: Collecting events from namespace "daemonsets-3254". STEP: Found 10 events. May 7 22:21:02.345: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-9rfwd: { } Scheduled: Successfully assigned daemonsets-3254/daemon-set-9rfwd to node1 May 7 22:21:02.345: INFO: At 2021-05-07 22:15:59 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-9rfwd May 7 22:21:02.345: INFO: At 2021-05-07 22:16:01 +0000 UTC - event for daemon-set-9rfwd: {multus } AddedInterface: Add eth0 [10.244.3.203/24] May 7 22:21:02.345: INFO: At 2021-05-07 22:16:01 +0000 UTC - event for daemon-set-9rfwd: {kubelet node1} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:21:02.345: INFO: At 2021-05-07 22:16:02 +0000 UTC - event for daemon-set-9rfwd: {kubelet node1} Failed: Error: ErrImagePull May 7 22:21:02.345: INFO: At 2021-05-07 22:16:02 +0000 UTC - event for daemon-set-9rfwd: {kubelet node1} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:21:02.345: INFO: At 2021-05-07 22:16:03 +0000 UTC - event for daemon-set-9rfwd: {kubelet node1} SandboxChanged: Pod sandbox changed, it will be killed and re-created. May 7 22:21:02.345: INFO: At 2021-05-07 22:16:05 +0000 UTC - event for daemon-set-9rfwd: {multus } AddedInterface: Add eth0 [10.244.3.204/24] May 7 22:21:02.345: INFO: At 2021-05-07 22:16:05 +0000 UTC - event for daemon-set-9rfwd: {kubelet node1} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:21:02.345: INFO: At 2021-05-07 22:16:05 +0000 UTC - event for daemon-set-9rfwd: {kubelet node1} Failed: Error: ImagePullBackOff May 7 22:21:02.347: INFO: POD NODE PHASE GRACE CONDITIONS May 7 22:21:02.347: INFO: May 7 22:21:02.351: INFO: Logging node info for node master1 May 7 22:21:02.353: INFO: Node Info: &Node{ObjectMeta:{master1 /api/v1/nodes/master1 7277f528-99fb-4be3-a928-27761a4599e8 51377 0 2021-05-07 19:59:27 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master1 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"a2:74:f5:d6:48:e4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.202 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/master.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 19:59:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 19:59:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.0.0/24\"":{}},"f:taints":{}}}} {nfd-master Update v1 2021-05-07 20:08:42 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/master.version":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.0.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.0.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:15 +0000 UTC,LastTransitionTime:2021-05-07 20:05:15 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:57 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:57 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:57 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:20:57 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.202,},NodeAddress{Type:Hostname,Address:master1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:44253340a37b4ed7bf5b3a3547b5f57d,SystemUUID:00ACFB60-0631-E711-906E-0017A4403562,BootID:2a44f9c3-2714-4b5c-975d-25d069f66483,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:9d07c391aeb1a9d02eb4343c113ed01825227c70c32b3cae861711f90191b0fd quay.io/coreos/kube-rbac-proxy:v0.4.1],SizeBytes:41317870,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[quay.io/coreos/prometheus-operator@sha256:a54e806fb27d2fb0251da4f3b2a3bb5320759af63a54a755788304775f2384a7 quay.io/coreos/prometheus-operator:v0.40.0],SizeBytes:38238457,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[registry@sha256:1cd9409a311350c3072fe510b52046f104416376c126a479cef9a4dfe692cf57 registry:2.7.0],SizeBytes:24191168,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 tas-controller:latest localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[nginx@sha256:a97eb9ecc708c8aa715ccfb5e9338f5456e4b65575daf304f108301f3b497314 nginx:1.19.2-alpine],SizeBytes:22052669,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 tas-extender:latest localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[@ :],SizeBytes:5577654,},ContainerImage{Names:[alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a alpine:3.12.1],SizeBytes:5573013,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:21:02.354: INFO: Logging kubelet events for node master1 May 7 22:21:02.356: INFO: Logging pods the kubelet thinks is on node master1 May 7 22:21:02.371: INFO: kube-apiserver-master1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.372: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:21:02.372: INFO: kube-controller-manager-master1 started at 2021-05-07 20:04:26 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.372: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:21:02.372: INFO: kube-scheduler-master1 started at 2021-05-07 20:15:37 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.372: INFO: Container kube-scheduler ready: true, restart count 0 May 7 22:21:02.372: INFO: kube-flannel-nj6vr started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:21:02.372: INFO: Init container install-cni ready: true, restart count 0 May 7 22:21:02.372: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:21:02.372: INFO: coredns-7677f9bb54-wvd65 started at 2021-05-07 20:02:30 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.372: INFO: Container coredns ready: true, restart count 2 May 7 22:21:02.372: INFO: node-feature-discovery-controller-5bf5c49849-z2bj7 started at 2021-05-07 20:08:34 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.372: INFO: Container nfd-controller ready: true, restart count 0 May 7 22:21:02.372: INFO: node-exporter-9sm5v started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.372: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:21:02.372: INFO: Container node-exporter ready: true, restart count 0 May 7 22:21:02.372: INFO: kube-proxy-qpvcb started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.372: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:21:02.372: INFO: kube-multus-ds-amd64-8tjh4 started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.372: INFO: Container kube-multus ready: true, restart count 1 May 7 22:21:02.372: INFO: docker-registry-docker-registry-56cbc7bc58-267wq started at 2021-05-07 20:05:51 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.372: INFO: Container docker-registry ready: true, restart count 0 May 7 22:21:02.372: INFO: Container nginx ready: true, restart count 0 May 7 22:21:02.372: INFO: prometheus-operator-5bb8cb9d8f-xqpnw started at 2021-05-07 20:12:35 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.372: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:21:02.372: INFO: Container prometheus-operator ready: true, restart count 0 W0507 22:21:02.385440 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:21:02.411: INFO: Latency metrics for node master1 May 7 22:21:02.411: INFO: Logging node info for node master2 May 7 22:21:02.413: INFO: Node Info: &Node{ObjectMeta:{master2 /api/v1/nodes/master2 8193aa97-7914-4d63-b6cf-a7ceb8fe519c 51359 0 2021-05-07 20:00:06 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master2 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"86:88:6a:bc:18:32"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.203 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {kube-controller-manager Update v1 2021-05-07 20:01:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.1.0/24\"":{}},"f:taints":{}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}}]},Spec:NodeSpec{PodCIDR:10.244.1.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234767872 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324603904 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:58 +0000 UTC,LastTransitionTime:2021-05-07 20:04:58 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:54 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:54 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:54 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:20:54 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.203,},NodeAddress{Type:Hostname,Address:master2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:cf652b4fb7284de2aaafc5f52f51e312,SystemUUID:00A0DE53-E51D-E711-906E-0017A4403562,BootID:df4da196-5a1c-4b40-aef7-034e79f7a8e2,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:21:02.413: INFO: Logging kubelet events for node master2 May 7 22:21:02.415: INFO: Logging pods the kubelet thinks is on node master2 May 7 22:21:02.428: INFO: dns-autoscaler-5b7b5c9b6f-flqh2 started at 2021-05-07 20:02:33 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.428: INFO: Container autoscaler ready: true, restart count 2 May 7 22:21:02.428: INFO: node-exporter-6nqvj started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.428: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:21:02.428: INFO: Container node-exporter ready: true, restart count 0 May 7 22:21:02.428: INFO: kube-apiserver-master2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.428: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:21:02.428: INFO: kube-controller-manager-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.428: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:21:02.429: INFO: kube-scheduler-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.429: INFO: Container kube-scheduler ready: true, restart count 2 May 7 22:21:02.429: INFO: kube-proxy-fg5dt started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.429: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:21:02.429: INFO: kube-flannel-wwlww started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:21:02.429: INFO: Init container install-cni ready: true, restart count 0 May 7 22:21:02.429: INFO: Container kube-flannel ready: true, restart count 1 May 7 22:21:02.429: INFO: kube-multus-ds-amd64-44vrh started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.429: INFO: Container kube-multus ready: true, restart count 1 W0507 22:21:02.441921 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:21:02.464: INFO: Latency metrics for node master2 May 7 22:21:02.464: INFO: Logging node info for node master3 May 7 22:21:02.466: INFO: Node Info: &Node{ObjectMeta:{master3 /api/v1/nodes/master3 27e1bfdf-bb8c-4924-9488-acacef172e76 51358 0 2021-05-07 20:00:17 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master3 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"de:31:a8:23:73:1a"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.204 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:18 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.2.0/24\"":{}},"f:taints":{}}}}]},Spec:NodeSpec{PodCIDR:10.244.2.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.2.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:10 +0000 UTC,LastTransitionTime:2021-05-07 20:04:10 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:53 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:53 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:53 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:20:53 +0000 UTC,LastTransitionTime:2021-05-07 20:03:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.204,},NodeAddress{Type:Hostname,Address:master3,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:01ba71adbf0d4ef79a9af064c18faf21,SystemUUID:008B1444-141E-E711-906E-0017A4403562,BootID:1692e58d-c13c-425c-b11a-62d901f965ec,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:21:02.467: INFO: Logging kubelet events for node master3 May 7 22:21:02.468: INFO: Logging pods the kubelet thinks is on node master3 May 7 22:21:02.481: INFO: kube-proxy-lvj72 started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.482: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:21:02.482: INFO: kube-flannel-j2xn4 started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:21:02.482: INFO: Init container install-cni ready: true, restart count 1 May 7 22:21:02.482: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:21:02.482: INFO: kube-multus-ds-amd64-hhqgw started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.482: INFO: Container kube-multus ready: true, restart count 1 May 7 22:21:02.482: INFO: coredns-7677f9bb54-pj7xl started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.482: INFO: Container coredns ready: true, restart count 2 May 7 22:21:02.482: INFO: node-exporter-tsk7w started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.482: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:21:02.482: INFO: Container node-exporter ready: true, restart count 0 May 7 22:21:02.482: INFO: kube-apiserver-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.482: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:21:02.482: INFO: kube-controller-manager-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.482: INFO: Container kube-controller-manager ready: true, restart count 3 May 7 22:21:02.482: INFO: kube-scheduler-master3 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.482: INFO: Container kube-scheduler ready: true, restart count 2 W0507 22:21:02.493793 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:21:02.523: INFO: Latency metrics for node master3 May 7 22:21:02.523: INFO: Logging node info for node node1 May 7 22:21:02.525: INFO: Node Info: &Node{ObjectMeta:{node1 /api/v1/nodes/node1 24d047f7-eb29-4f1d-96d0-63b225220bd5 51396 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node1 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"da:1d:6f:d2:a8:b4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.207 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.3.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:09 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {kubelet Update v1 2021-05-07 20:11:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.3.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:03:55 +0000 UTC,LastTransitionTime:2021-05-07 20:03:55 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:58 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:58 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:58 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:20:58 +0000 UTC,LastTransitionTime:2021-05-07 20:03:44 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.207,},NodeAddress{Type:Hostname,Address:node1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:d79c3a817fbd4f03a173930e545bb174,SystemUUID:00CDA902-D022-E711-906E-0017A4403562,BootID:53771151-d654-4c88-80fe-48032d3317a5,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[@ :],SizeBytes:1002488002,},ContainerImage{Names:[opnfv/barometer-collectd@sha256:ed5c574f653e2a39e784ff322033a2319aafde7366c803a88f20f7a2a8bc1efb opnfv/barometer-collectd:stable],SizeBytes:825413035,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[golang@sha256:1636899c10870ab66c48d960a9df620f4f9e86a0c72fbacf36032d27404e7e6c golang:alpine3.12],SizeBytes:301156062,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[grafana/grafana@sha256:89304bc2335f4976618548d7b93d165ed67369d3a051d2f627fc4e0aa3d0aff1 grafana/grafana:7.1.0],SizeBytes:179601493,},ContainerImage{Names:[quay.io/prometheus/prometheus@sha256:d4ba4dd1a9ebb90916d0bfed3c204adcb118ed24546bf8dd2e6b30fc0fd2009e quay.io/prometheus/prometheus:v2.20.0],SizeBytes:144886595,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[directxman12/k8s-prometheus-adapter-amd64@sha256:b63dc612e3cb73f79d2401a4516f794f9f0a83002600ca72e675e41baecff437 directxman12/k8s-prometheus-adapter-amd64:v0.6.0],SizeBytes:53267842,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d nfvpe/sriov-device-plugin:latest localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[quay.io/coreos/prometheus-config-reloader@sha256:c679a143b24b7731ad1577a9865aa3805426cbf1b25e30807b951dff68466ffd quay.io/coreos/prometheus-config-reloader:v0.40.0],SizeBytes:10131705,},ContainerImage{Names:[jimmidyson/configmap-reload@sha256:d107c7a235c266273b1c3502a391fec374430e5625539403d0de797fa9c556a2 jimmidyson/configmap-reload:v0.3.0],SizeBytes:9700438,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[appropriate/curl@sha256:027a0ad3c69d085fea765afca9984787b780c172cead6502fec989198b98d8bb appropriate/curl:edge],SizeBytes:5654234,},ContainerImage{Names:[alpine@sha256:36553b10a4947067b9fbb7d532951066293a68eae893beba1d9235f7d11a20ad alpine:3.12],SizeBytes:5581415,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[gcr.io/authenticated-image-pulling/alpine@sha256:7ff177862cb50c602bfe81f805969412e619c054a2bbead977d0c276988aa4a0 gcr.io/authenticated-image-pulling/alpine:3.7],SizeBytes:4206620,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:21:02.526: INFO: Logging kubelet events for node node1 May 7 22:21:02.528: INFO: Logging pods the kubelet thinks is on node node1 May 7 22:21:02.545: INFO: kube-proxy-bms7z started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.545: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:21:02.545: INFO: cmk-init-discover-node1-krbjn started at 2021-05-07 20:11:05 +0000 UTC (0+3 container statuses recorded) May 7 22:21:02.545: INFO: Container discover ready: false, restart count 0 May 7 22:21:02.545: INFO: Container init ready: false, restart count 0 May 7 22:21:02.545: INFO: Container install ready: false, restart count 0 May 7 22:21:02.545: INFO: cmk-gjhf2 started at 2021-05-07 20:11:48 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.545: INFO: Container nodereport ready: true, restart count 0 May 7 22:21:02.545: INFO: Container reconcile ready: true, restart count 0 May 7 22:21:02.545: INFO: kube-multus-ds-amd64-fxgdb started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.545: INFO: Container kube-multus ready: true, restart count 1 May 7 22:21:02.545: INFO: prometheus-k8s-0 started at 2021-05-07 20:12:50 +0000 UTC (0+5 container statuses recorded) May 7 22:21:02.546: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:21:02.546: INFO: Container grafana ready: true, restart count 0 May 7 22:21:02.546: INFO: Container prometheus ready: true, restart count 1 May 7 22:21:02.546: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:21:02.546: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:21:02.546: INFO: kube-flannel-qm7lv started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:21:02.546: INFO: Init container install-cni ready: true, restart count 2 May 7 22:21:02.546: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:21:02.546: INFO: nginx-proxy-node1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.546: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:21:02.546: INFO: kubernetes-metrics-scraper-678c97765c-g7srv started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.546: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:21:02.546: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.546: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:21:02.546: INFO: node-exporter-mpq58 started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.546: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:21:02.546: INFO: Container node-exporter ready: true, restart count 0 May 7 22:21:02.546: INFO: collectd-tmjfs started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:21:02.546: INFO: Container collectd ready: true, restart count 0 May 7 22:21:02.546: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:21:02.546: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:21:02.546: INFO: node-feature-discovery-worker-xvbpd started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.546: INFO: Container nfd-worker ready: true, restart count 0 W0507 22:21:02.558904 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:21:02.589: INFO: Latency metrics for node node1 May 7 22:21:02.589: INFO: Logging node info for node node2 May 7 22:21:02.592: INFO: Node Info: &Node{ObjectMeta:{node2 /api/v1/nodes/node2 eae422ac-f6f0-4e9a-961d-e133dffc36be 51376 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node2 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"22:df:da:84:9b:00"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.208 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.4.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:31 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {kubelet Update v1 2021-05-07 20:11:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.4.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:02 +0000 UTC,LastTransitionTime:2021-05-07 20:05:02 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:57 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:57 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:20:57 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:20:57 +0000 UTC,LastTransitionTime:2021-05-07 20:02:07 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.208,},NodeAddress{Type:Hostname,Address:node2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:6f56c5a750d0441dba0ffa6273fb1a17,SystemUUID:80B3CD56-852F-E711-906E-0017A4403562,BootID:98b263e9-3136-45ed-9b07-5f5b6b9d69b8,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[k8s.gcr.io/etcd@sha256:4ad90a11b55313b182afc186b9876c8e891531b8db4c9bf1541953021618d0e2 k8s.gcr.io/etcd:3.4.13-0],SizeBytes:253392289,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/sample-apiserver@sha256:ff02aacd9766d597883fabafc7ad604c719a57611db1bcc1564c69a45b000a55 gcr.io/kubernetes-e2e-test-images/sample-apiserver:1.17],SizeBytes:60684726,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:21:02.593: INFO: Logging kubelet events for node node2 May 7 22:21:02.595: INFO: Logging pods the kubelet thinks is on node node2 May 7 22:21:02.612: INFO: kube-flannel-htqkx started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:21:02.612: INFO: Init container install-cni ready: true, restart count 2 May 7 22:21:02.612: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:21:02.612: INFO: kube-multus-ds-amd64-g98hm started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.612: INFO: Container kube-multus ready: true, restart count 1 May 7 22:21:02.612: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f started at 2021-05-07 20:15:36 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.612: INFO: Container tas-controller ready: true, restart count 0 May 7 22:21:02.612: INFO: Container tas-extender ready: true, restart count 0 May 7 22:21:02.612: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.612: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:21:02.612: INFO: cmk-init-discover-node2-kd9gg started at 2021-05-07 20:11:26 +0000 UTC (0+3 container statuses recorded) May 7 22:21:02.612: INFO: Container discover ready: false, restart count 0 May 7 22:21:02.612: INFO: Container init ready: false, restart count 0 May 7 22:21:02.612: INFO: Container install ready: false, restart count 0 May 7 22:21:02.612: INFO: cmk-gvh7j started at 2021-05-07 20:11:49 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.612: INFO: Container nodereport ready: true, restart count 0 May 7 22:21:02.612: INFO: Container reconcile ready: true, restart count 0 May 7 22:21:02.612: INFO: cmk-webhook-6c9d5f8578-94s58 started at 2021-05-07 20:11:49 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.612: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:21:02.612: INFO: collectd-p5gbt started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:21:02.612: INFO: Container collectd ready: true, restart count 0 May 7 22:21:02.612: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:21:02.612: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:21:02.612: INFO: nginx-proxy-node2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.612: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:21:02.612: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.612: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:21:02.612: INFO: kube-proxy-rgw7h started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.612: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:21:02.612: INFO: node-feature-discovery-worker-wp5n6 started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:21:02.612: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:21:02.612: INFO: node-exporter-4bcls started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:21:02.613: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:21:02.613: INFO: Container node-exporter ready: true, restart count 0 W0507 22:21:02.627360 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:21:02.658: INFO: Latency metrics for node node2 May 7 22:21:02.658: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-3254" for this suite. • Failure [302.781 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should run and stop complex daemon [Conformance] [It] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:20:59.950: error waiting for daemon pods to be running on new nodes Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:203 ------------------------------ {"msg":"FAILED [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","total":17,"completed":1,"skipped":858,"failed":1,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:21:02.683: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:89 May 7 22:21:02.712: INFO: Waiting up to 1m0s for all nodes to be ready May 7 22:22:02.760: INFO: Waiting for terminating namespaces to be deleted... [BeforeEach] PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:22:02.762: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption-path STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:487 STEP: Finding an available node STEP: Trying to launch a pod without a label to get a node which can launch it. STEP: Explicitly delete pod here to free the resource it takes. May 7 22:22:06.816: INFO: found a healthy node: node1 [It] runs ReplicaSets to verify preemption running path [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:22:20.870: INFO: pods created so far: [1 1 1] May 7 22:22:20.870: INFO: length of pods created so far: 3 May 7 22:22:36.886: INFO: pods created so far: [2 2 1] [AfterEach] PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:22:43.886: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-path-2391" for this suite. [AfterEach] PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:461 [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:22:43.923: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-3659" for this suite. [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:77 • [SLOW TEST:101.278 seconds] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:450 runs ReplicaSets to verify preemption running path [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]","total":17,"completed":2,"skipped":1397,"failed":1,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:22:43.963: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 May 7 22:22:43.985: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready May 7 22:22:43.997: INFO: Waiting for terminating namespaces to be deleted... May 7 22:22:44.001: INFO: Logging pods the apiserver thinks is on node node1 before test May 7 22:22:44.009: INFO: cmk-gjhf2 from kube-system started at 2021-05-07 20:11:48 +0000 UTC (2 container statuses recorded) May 7 22:22:44.009: INFO: Container nodereport ready: true, restart count 0 May 7 22:22:44.009: INFO: Container reconcile ready: true, restart count 0 May 7 22:22:44.009: INFO: cmk-init-discover-node1-krbjn from kube-system started at 2021-05-07 20:11:05 +0000 UTC (3 container statuses recorded) May 7 22:22:44.009: INFO: Container discover ready: false, restart count 0 May 7 22:22:44.009: INFO: Container init ready: false, restart count 0 May 7 22:22:44.009: INFO: Container install ready: false, restart count 0 May 7 22:22:44.009: INFO: kube-flannel-qm7lv from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:22:44.009: INFO: kube-multus-ds-amd64-fxgdb from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container kube-multus ready: true, restart count 1 May 7 22:22:44.009: INFO: kube-proxy-bms7z from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:22:44.009: INFO: kubernetes-metrics-scraper-678c97765c-g7srv from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:22:44.009: INFO: nginx-proxy-node1 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:22:44.009: INFO: node-feature-discovery-worker-xvbpd from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:22:44.009: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:22:44.009: INFO: collectd-tmjfs from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:22:44.009: INFO: Container collectd ready: true, restart count 0 May 7 22:22:44.009: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:22:44.009: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:22:44.009: INFO: node-exporter-mpq58 from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:22:44.009: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:22:44.009: INFO: Container node-exporter ready: true, restart count 0 May 7 22:22:44.009: INFO: prometheus-k8s-0 from monitoring started at 2021-05-07 20:12:50 +0000 UTC (5 container statuses recorded) May 7 22:22:44.009: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:22:44.009: INFO: Container grafana ready: true, restart count 0 May 7 22:22:44.009: INFO: Container prometheus ready: true, restart count 1 May 7 22:22:44.009: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:22:44.009: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:22:44.009: INFO: pod4 from sched-preemption-path-2391 started at 2021-05-07 22:22:35 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container pod4 ready: true, restart count 0 May 7 22:22:44.009: INFO: rs-pod3-lhf27 from sched-preemption-path-2391 started at 2021-05-07 22:22:16 +0000 UTC (1 container statuses recorded) May 7 22:22:44.009: INFO: Container pod3 ready: true, restart count 0 May 7 22:22:44.009: INFO: Logging pods the apiserver thinks is on node node2 before test May 7 22:22:44.018: INFO: cmk-gvh7j from kube-system started at 2021-05-07 20:11:49 +0000 UTC (2 container statuses recorded) May 7 22:22:44.018: INFO: Container nodereport ready: true, restart count 0 May 7 22:22:44.018: INFO: Container reconcile ready: true, restart count 0 May 7 22:22:44.018: INFO: cmk-init-discover-node2-kd9gg from kube-system started at 2021-05-07 20:11:26 +0000 UTC (3 container statuses recorded) May 7 22:22:44.018: INFO: Container discover ready: false, restart count 0 May 7 22:22:44.018: INFO: Container init ready: false, restart count 0 May 7 22:22:44.018: INFO: Container install ready: false, restart count 0 May 7 22:22:44.018: INFO: cmk-webhook-6c9d5f8578-94s58 from kube-system started at 2021-05-07 20:11:49 +0000 UTC (1 container statuses recorded) May 7 22:22:44.018: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:22:44.018: INFO: kube-flannel-htqkx from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:22:44.018: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:22:44.018: INFO: kube-multus-ds-amd64-g98hm from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:22:44.018: INFO: Container kube-multus ready: true, restart count 1 May 7 22:22:44.018: INFO: kube-proxy-rgw7h from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:22:44.018: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:22:44.018: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:22:44.018: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:22:44.018: INFO: nginx-proxy-node2 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:22:44.018: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:22:44.018: INFO: node-feature-discovery-worker-wp5n6 from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:22:44.018: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:22:44.018: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:22:44.018: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:22:44.018: INFO: collectd-p5gbt from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:22:44.018: INFO: Container collectd ready: true, restart count 0 May 7 22:22:44.018: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:22:44.018: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:22:44.018: INFO: node-exporter-4bcls from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:22:44.018: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:22:44.018: INFO: Container node-exporter ready: true, restart count 0 May 7 22:22:44.018: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f from monitoring started at 2021-05-07 20:15:36 +0000 UTC (2 container statuses recorded) May 7 22:22:44.018: INFO: Container tas-controller ready: true, restart count 0 May 7 22:22:44.018: INFO: Container tas-extender ready: true, restart count 0 [It] validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Trying to launch a pod without a label to get a node which can launch it. STEP: Explicitly delete pod here to free the resource it takes. STEP: Trying to apply a random label on the found node. STEP: verifying the node has the label kubernetes.io/e2e-9693e5b9-46c9-4d35-9083-e8d937c2fd2d 95 STEP: Trying to create a pod(pod4) with hostport 54322 and hostIP 0.0.0.0(empty string here) and expect scheduled STEP: Trying to create another pod(pod5) with hostport 54322 but hostIP 127.0.0.1 on the node which pod4 resides and expect not scheduled STEP: removing the label kubernetes.io/e2e-9693e5b9-46c9-4d35-9083-e8d937c2fd2d off the node node1 STEP: verifying the node doesn't have the label kubernetes.io/e2e-9693e5b9-46c9-4d35-9083-e8d937c2fd2d [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:27:52.109: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-6130" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 • [SLOW TEST:308.154 seconds] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance]","total":17,"completed":3,"skipped":1532,"failed":1,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:27:52.122: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:134 [It] should run and stop simple daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Creating simple DaemonSet "daemon-set" STEP: Check that daemon pods launch on every node of the cluster. May 7 22:27:52.174: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:52.174: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:52.175: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:52.178: INFO: Number of nodes with available pods: 0 May 7 22:27:52.178: INFO: Node node1 is running more than one daemon pod May 7 22:27:53.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:53.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:53.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:53.187: INFO: Number of nodes with available pods: 0 May 7 22:27:53.187: INFO: Node node1 is running more than one daemon pod May 7 22:27:54.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:54.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:54.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:54.189: INFO: Number of nodes with available pods: 0 May 7 22:27:54.189: INFO: Node node1 is running more than one daemon pod May 7 22:27:55.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:55.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:55.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:55.188: INFO: Number of nodes with available pods: 0 May 7 22:27:55.188: INFO: Node node1 is running more than one daemon pod May 7 22:27:56.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:56.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:56.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:56.188: INFO: Number of nodes with available pods: 0 May 7 22:27:56.188: INFO: Node node1 is running more than one daemon pod May 7 22:27:57.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:57.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:57.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:57.186: INFO: Number of nodes with available pods: 0 May 7 22:27:57.186: INFO: Node node1 is running more than one daemon pod May 7 22:27:58.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:58.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:58.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:58.185: INFO: Number of nodes with available pods: 0 May 7 22:27:58.185: INFO: Node node1 is running more than one daemon pod May 7 22:27:59.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:59.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:59.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:27:59.186: INFO: Number of nodes with available pods: 0 May 7 22:27:59.186: INFO: Node node1 is running more than one daemon pod May 7 22:28:00.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:00.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:00.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:00.188: INFO: Number of nodes with available pods: 0 May 7 22:28:00.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:01.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:01.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:01.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:01.185: INFO: Number of nodes with available pods: 0 May 7 22:28:01.185: INFO: Node node1 is running more than one daemon pod May 7 22:28:02.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:02.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:02.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:02.187: INFO: Number of nodes with available pods: 0 May 7 22:28:02.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:03.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:03.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:03.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:03.187: INFO: Number of nodes with available pods: 0 May 7 22:28:03.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:04.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:04.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:04.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:04.186: INFO: Number of nodes with available pods: 0 May 7 22:28:04.186: INFO: Node node1 is running more than one daemon pod May 7 22:28:05.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:05.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:05.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:05.186: INFO: Number of nodes with available pods: 0 May 7 22:28:05.186: INFO: Node node1 is running more than one daemon pod May 7 22:28:06.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:06.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:06.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:06.187: INFO: Number of nodes with available pods: 0 May 7 22:28:06.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:07.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:07.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:07.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:07.188: INFO: Number of nodes with available pods: 0 May 7 22:28:07.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:08.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:08.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:08.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:08.187: INFO: Number of nodes with available pods: 0 May 7 22:28:08.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:09.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:09.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:09.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:09.188: INFO: Number of nodes with available pods: 0 May 7 22:28:09.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:10.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:10.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:10.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:10.187: INFO: Number of nodes with available pods: 0 May 7 22:28:10.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:11.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:11.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:11.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:11.186: INFO: Number of nodes with available pods: 0 May 7 22:28:11.186: INFO: Node node1 is running more than one daemon pod May 7 22:28:12.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:12.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:12.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:12.188: INFO: Number of nodes with available pods: 0 May 7 22:28:12.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:13.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:13.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:13.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:13.187: INFO: Number of nodes with available pods: 0 May 7 22:28:13.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:14.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:14.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:14.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:14.186: INFO: Number of nodes with available pods: 0 May 7 22:28:14.186: INFO: Node node1 is running more than one daemon pod May 7 22:28:15.187: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:15.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:15.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:15.189: INFO: Number of nodes with available pods: 0 May 7 22:28:15.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:16.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:16.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:16.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:16.188: INFO: Number of nodes with available pods: 0 May 7 22:28:16.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:17.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:17.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:17.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:17.189: INFO: Number of nodes with available pods: 0 May 7 22:28:17.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:18.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:18.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:18.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:18.188: INFO: Number of nodes with available pods: 0 May 7 22:28:18.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:19.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:19.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:19.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:19.188: INFO: Number of nodes with available pods: 0 May 7 22:28:19.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:20.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:20.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:20.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:20.189: INFO: Number of nodes with available pods: 0 May 7 22:28:20.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:21.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:21.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:21.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:21.187: INFO: Number of nodes with available pods: 0 May 7 22:28:21.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:22.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:22.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:22.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:22.188: INFO: Number of nodes with available pods: 0 May 7 22:28:22.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:23.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:23.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:23.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:23.189: INFO: Number of nodes with available pods: 0 May 7 22:28:23.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:24.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:24.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:24.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:24.186: INFO: Number of nodes with available pods: 0 May 7 22:28:24.186: INFO: Node node1 is running more than one daemon pod May 7 22:28:25.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:25.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:25.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:25.189: INFO: Number of nodes with available pods: 0 May 7 22:28:25.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:26.187: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:26.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:26.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:26.191: INFO: Number of nodes with available pods: 0 May 7 22:28:26.191: INFO: Node node1 is running more than one daemon pod May 7 22:28:27.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:27.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:27.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:27.189: INFO: Number of nodes with available pods: 0 May 7 22:28:27.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:28.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:28.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:28.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:28.187: INFO: Number of nodes with available pods: 0 May 7 22:28:28.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:29.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:29.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:29.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:29.187: INFO: Number of nodes with available pods: 0 May 7 22:28:29.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:30.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:30.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:30.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:30.188: INFO: Number of nodes with available pods: 0 May 7 22:28:30.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:31.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:31.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:31.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:31.189: INFO: Number of nodes with available pods: 0 May 7 22:28:31.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:32.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:32.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:32.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:32.188: INFO: Number of nodes with available pods: 0 May 7 22:28:32.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:33.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:33.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:33.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:33.187: INFO: Number of nodes with available pods: 0 May 7 22:28:33.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:34.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:34.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:34.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:34.187: INFO: Number of nodes with available pods: 0 May 7 22:28:34.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:35.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:35.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:35.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:35.187: INFO: Number of nodes with available pods: 0 May 7 22:28:35.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:36.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:36.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:36.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:36.188: INFO: Number of nodes with available pods: 0 May 7 22:28:36.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:37.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:37.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:37.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:37.189: INFO: Number of nodes with available pods: 0 May 7 22:28:37.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:38.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:38.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:38.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:38.188: INFO: Number of nodes with available pods: 0 May 7 22:28:38.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:39.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:39.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:39.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:39.187: INFO: Number of nodes with available pods: 0 May 7 22:28:39.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:40.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:40.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:40.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:40.188: INFO: Number of nodes with available pods: 0 May 7 22:28:40.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:41.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:41.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:41.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:41.188: INFO: Number of nodes with available pods: 0 May 7 22:28:41.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:42.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:42.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:42.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:42.187: INFO: Number of nodes with available pods: 0 May 7 22:28:42.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:43.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:43.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:43.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:43.187: INFO: Number of nodes with available pods: 0 May 7 22:28:43.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:44.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:44.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:44.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:44.188: INFO: Number of nodes with available pods: 0 May 7 22:28:44.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:45.187: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:45.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:45.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:45.190: INFO: Number of nodes with available pods: 0 May 7 22:28:45.190: INFO: Node node1 is running more than one daemon pod May 7 22:28:46.189: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:46.189: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:46.189: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:46.192: INFO: Number of nodes with available pods: 0 May 7 22:28:46.192: INFO: Node node1 is running more than one daemon pod May 7 22:28:47.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:47.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:47.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:47.188: INFO: Number of nodes with available pods: 0 May 7 22:28:47.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:48.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:48.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:48.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:48.189: INFO: Number of nodes with available pods: 0 May 7 22:28:48.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:49.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:49.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:49.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:49.186: INFO: Number of nodes with available pods: 0 May 7 22:28:49.186: INFO: Node node1 is running more than one daemon pod May 7 22:28:50.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:50.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:50.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:50.187: INFO: Number of nodes with available pods: 0 May 7 22:28:50.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:51.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:51.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:51.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:51.187: INFO: Number of nodes with available pods: 0 May 7 22:28:51.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:52.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:52.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:52.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:52.187: INFO: Number of nodes with available pods: 0 May 7 22:28:52.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:53.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:53.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:53.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:53.188: INFO: Number of nodes with available pods: 0 May 7 22:28:53.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:54.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:54.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:54.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:54.187: INFO: Number of nodes with available pods: 0 May 7 22:28:54.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:55.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:55.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:55.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:55.189: INFO: Number of nodes with available pods: 0 May 7 22:28:55.189: INFO: Node node1 is running more than one daemon pod May 7 22:28:56.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:56.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:56.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:56.187: INFO: Number of nodes with available pods: 0 May 7 22:28:56.187: INFO: Node node1 is running more than one daemon pod May 7 22:28:57.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:57.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:57.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:57.186: INFO: Number of nodes with available pods: 0 May 7 22:28:57.186: INFO: Node node1 is running more than one daemon pod May 7 22:28:58.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:58.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:58.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:58.188: INFO: Number of nodes with available pods: 0 May 7 22:28:58.188: INFO: Node node1 is running more than one daemon pod May 7 22:28:59.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:59.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:59.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:28:59.186: INFO: Number of nodes with available pods: 0 May 7 22:28:59.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:00.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:00.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:00.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:00.187: INFO: Number of nodes with available pods: 0 May 7 22:29:00.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:01.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:01.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:01.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:01.188: INFO: Number of nodes with available pods: 0 May 7 22:29:01.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:02.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:02.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:02.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:02.186: INFO: Number of nodes with available pods: 0 May 7 22:29:02.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:03.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:03.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:03.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:03.186: INFO: Number of nodes with available pods: 0 May 7 22:29:03.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:04.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:04.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:04.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:04.187: INFO: Number of nodes with available pods: 0 May 7 22:29:04.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:05.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:05.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:05.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:05.188: INFO: Number of nodes with available pods: 0 May 7 22:29:05.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:06.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:06.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:06.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:06.185: INFO: Number of nodes with available pods: 0 May 7 22:29:06.185: INFO: Node node1 is running more than one daemon pod May 7 22:29:07.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:07.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:07.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:07.188: INFO: Number of nodes with available pods: 0 May 7 22:29:07.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:08.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:08.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:08.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:08.186: INFO: Number of nodes with available pods: 0 May 7 22:29:08.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:09.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:09.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:09.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:09.186: INFO: Number of nodes with available pods: 0 May 7 22:29:09.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:10.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:10.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:10.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:10.187: INFO: Number of nodes with available pods: 0 May 7 22:29:10.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:11.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:11.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:11.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:11.188: INFO: Number of nodes with available pods: 0 May 7 22:29:11.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:12.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:12.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:12.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:12.187: INFO: Number of nodes with available pods: 0 May 7 22:29:12.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:13.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:13.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:13.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:13.187: INFO: Number of nodes with available pods: 0 May 7 22:29:13.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:14.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:14.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:14.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:14.189: INFO: Number of nodes with available pods: 0 May 7 22:29:14.189: INFO: Node node1 is running more than one daemon pod May 7 22:29:15.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:15.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:15.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:15.189: INFO: Number of nodes with available pods: 0 May 7 22:29:15.189: INFO: Node node1 is running more than one daemon pod May 7 22:29:16.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:16.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:16.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:16.187: INFO: Number of nodes with available pods: 0 May 7 22:29:16.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:17.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:17.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:17.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:17.189: INFO: Number of nodes with available pods: 0 May 7 22:29:17.189: INFO: Node node1 is running more than one daemon pod May 7 22:29:18.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:18.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:18.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:18.186: INFO: Number of nodes with available pods: 0 May 7 22:29:18.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:19.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:19.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:19.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:19.186: INFO: Number of nodes with available pods: 0 May 7 22:29:19.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:20.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:20.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:20.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:20.188: INFO: Number of nodes with available pods: 0 May 7 22:29:20.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:21.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:21.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:21.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:21.185: INFO: Number of nodes with available pods: 0 May 7 22:29:21.185: INFO: Node node1 is running more than one daemon pod May 7 22:29:22.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:22.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:22.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:22.188: INFO: Number of nodes with available pods: 0 May 7 22:29:22.189: INFO: Node node1 is running more than one daemon pod May 7 22:29:23.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:23.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:23.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:23.190: INFO: Number of nodes with available pods: 0 May 7 22:29:23.190: INFO: Node node1 is running more than one daemon pod May 7 22:29:24.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:24.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:24.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:24.186: INFO: Number of nodes with available pods: 0 May 7 22:29:24.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:25.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:25.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:25.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:25.186: INFO: Number of nodes with available pods: 0 May 7 22:29:25.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:26.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:26.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:26.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:26.185: INFO: Number of nodes with available pods: 0 May 7 22:29:26.185: INFO: Node node1 is running more than one daemon pod May 7 22:29:27.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:27.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:27.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:27.187: INFO: Number of nodes with available pods: 0 May 7 22:29:27.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:28.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:28.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:28.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:28.186: INFO: Number of nodes with available pods: 0 May 7 22:29:28.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:29.182: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:29.182: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:29.182: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:29.186: INFO: Number of nodes with available pods: 0 May 7 22:29:29.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:30.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:30.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:30.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:30.186: INFO: Number of nodes with available pods: 0 May 7 22:29:30.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:31.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:31.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:31.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:31.188: INFO: Number of nodes with available pods: 0 May 7 22:29:31.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:32.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:32.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:32.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:32.189: INFO: Number of nodes with available pods: 0 May 7 22:29:32.189: INFO: Node node1 is running more than one daemon pod May 7 22:29:33.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:33.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:33.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:33.186: INFO: Number of nodes with available pods: 0 May 7 22:29:33.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:34.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:34.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:34.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:34.186: INFO: Number of nodes with available pods: 0 May 7 22:29:34.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:35.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:35.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:35.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:35.187: INFO: Number of nodes with available pods: 0 May 7 22:29:35.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:36.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:36.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:36.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:36.186: INFO: Number of nodes with available pods: 0 May 7 22:29:36.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:37.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:37.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:37.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:37.186: INFO: Number of nodes with available pods: 0 May 7 22:29:37.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:38.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:38.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:38.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:38.185: INFO: Number of nodes with available pods: 0 May 7 22:29:38.185: INFO: Node node1 is running more than one daemon pod May 7 22:29:39.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:39.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:39.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:39.187: INFO: Number of nodes with available pods: 0 May 7 22:29:39.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:40.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:40.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:40.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:40.186: INFO: Number of nodes with available pods: 0 May 7 22:29:40.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:41.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:41.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:41.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:41.186: INFO: Number of nodes with available pods: 0 May 7 22:29:41.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:42.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:42.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:42.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:42.186: INFO: Number of nodes with available pods: 0 May 7 22:29:42.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:43.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:43.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:43.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:43.188: INFO: Number of nodes with available pods: 0 May 7 22:29:43.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:44.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:44.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:44.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:44.188: INFO: Number of nodes with available pods: 0 May 7 22:29:44.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:45.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:45.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:45.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:45.186: INFO: Number of nodes with available pods: 0 May 7 22:29:45.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:46.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:46.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:46.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:46.186: INFO: Number of nodes with available pods: 0 May 7 22:29:46.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:47.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:47.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:47.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:47.188: INFO: Number of nodes with available pods: 0 May 7 22:29:47.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:48.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:48.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:48.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:48.187: INFO: Number of nodes with available pods: 0 May 7 22:29:48.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:49.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:49.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:49.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:49.186: INFO: Number of nodes with available pods: 0 May 7 22:29:49.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:50.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:50.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:50.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:50.189: INFO: Number of nodes with available pods: 0 May 7 22:29:50.189: INFO: Node node1 is running more than one daemon pod May 7 22:29:51.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:51.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:51.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:51.188: INFO: Number of nodes with available pods: 0 May 7 22:29:51.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:52.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:52.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:52.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:52.187: INFO: Number of nodes with available pods: 0 May 7 22:29:52.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:53.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:53.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:53.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:53.186: INFO: Number of nodes with available pods: 0 May 7 22:29:53.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:54.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:54.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:54.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:54.187: INFO: Number of nodes with available pods: 0 May 7 22:29:54.187: INFO: Node node1 is running more than one daemon pod May 7 22:29:55.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:55.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:55.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:55.188: INFO: Number of nodes with available pods: 0 May 7 22:29:55.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:56.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:56.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:56.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:56.188: INFO: Number of nodes with available pods: 0 May 7 22:29:56.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:57.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:57.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:57.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:57.186: INFO: Number of nodes with available pods: 0 May 7 22:29:57.186: INFO: Node node1 is running more than one daemon pod May 7 22:29:58.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:58.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:58.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:58.188: INFO: Number of nodes with available pods: 0 May 7 22:29:58.188: INFO: Node node1 is running more than one daemon pod May 7 22:29:59.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:59.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:59.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:29:59.186: INFO: Number of nodes with available pods: 0 May 7 22:29:59.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:00.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:00.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:00.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:00.187: INFO: Number of nodes with available pods: 0 May 7 22:30:00.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:01.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:01.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:01.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:01.190: INFO: Number of nodes with available pods: 0 May 7 22:30:01.190: INFO: Node node1 is running more than one daemon pod May 7 22:30:02.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:02.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:02.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:02.188: INFO: Number of nodes with available pods: 0 May 7 22:30:02.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:03.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:03.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:03.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:03.187: INFO: Number of nodes with available pods: 0 May 7 22:30:03.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:04.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:04.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:04.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:04.186: INFO: Number of nodes with available pods: 0 May 7 22:30:04.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:05.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:05.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:05.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:05.186: INFO: Number of nodes with available pods: 0 May 7 22:30:05.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:06.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:06.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:06.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:06.187: INFO: Number of nodes with available pods: 0 May 7 22:30:06.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:07.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:07.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:07.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:07.189: INFO: Number of nodes with available pods: 0 May 7 22:30:07.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:08.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:08.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:08.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:08.187: INFO: Number of nodes with available pods: 0 May 7 22:30:08.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:09.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:09.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:09.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:09.187: INFO: Number of nodes with available pods: 0 May 7 22:30:09.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:10.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:10.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:10.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:10.188: INFO: Number of nodes with available pods: 0 May 7 22:30:10.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:11.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:11.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:11.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:11.189: INFO: Number of nodes with available pods: 0 May 7 22:30:11.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:12.187: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:12.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:12.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:12.190: INFO: Number of nodes with available pods: 0 May 7 22:30:12.190: INFO: Node node1 is running more than one daemon pod May 7 22:30:13.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:13.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:13.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:13.188: INFO: Number of nodes with available pods: 0 May 7 22:30:13.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:14.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:14.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:14.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:14.187: INFO: Number of nodes with available pods: 0 May 7 22:30:14.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:15.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:15.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:15.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:15.187: INFO: Number of nodes with available pods: 0 May 7 22:30:15.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:16.187: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:16.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:16.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:16.189: INFO: Number of nodes with available pods: 0 May 7 22:30:16.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:17.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:17.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:17.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:17.185: INFO: Number of nodes with available pods: 0 May 7 22:30:17.185: INFO: Node node1 is running more than one daemon pod May 7 22:30:18.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:18.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:18.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:18.186: INFO: Number of nodes with available pods: 0 May 7 22:30:18.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:19.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:19.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:19.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:19.187: INFO: Number of nodes with available pods: 0 May 7 22:30:19.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:20.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:20.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:20.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:20.188: INFO: Number of nodes with available pods: 0 May 7 22:30:20.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:21.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:21.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:21.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:21.187: INFO: Number of nodes with available pods: 0 May 7 22:30:21.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:22.187: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:22.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:22.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:22.190: INFO: Number of nodes with available pods: 0 May 7 22:30:22.190: INFO: Node node1 is running more than one daemon pod May 7 22:30:23.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:23.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:23.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:23.187: INFO: Number of nodes with available pods: 0 May 7 22:30:23.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:24.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:24.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:24.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:24.188: INFO: Number of nodes with available pods: 0 May 7 22:30:24.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:25.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:25.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:25.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:25.186: INFO: Number of nodes with available pods: 0 May 7 22:30:25.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:26.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:26.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:26.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:26.189: INFO: Number of nodes with available pods: 0 May 7 22:30:26.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:27.187: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:27.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:27.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:27.190: INFO: Number of nodes with available pods: 0 May 7 22:30:27.190: INFO: Node node1 is running more than one daemon pod May 7 22:30:28.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:28.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:28.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:28.187: INFO: Number of nodes with available pods: 0 May 7 22:30:28.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:29.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:29.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:29.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:29.187: INFO: Number of nodes with available pods: 0 May 7 22:30:29.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:30.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:30.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:30.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:30.188: INFO: Number of nodes with available pods: 0 May 7 22:30:30.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:31.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:31.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:31.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:31.187: INFO: Number of nodes with available pods: 0 May 7 22:30:31.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:32.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:32.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:32.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:32.189: INFO: Number of nodes with available pods: 0 May 7 22:30:32.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:33.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:33.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:33.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:33.186: INFO: Number of nodes with available pods: 0 May 7 22:30:33.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:34.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:34.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:34.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:34.187: INFO: Number of nodes with available pods: 0 May 7 22:30:34.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:35.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:35.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:35.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:35.189: INFO: Number of nodes with available pods: 0 May 7 22:30:35.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:36.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:36.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:36.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:36.188: INFO: Number of nodes with available pods: 0 May 7 22:30:36.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:37.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:37.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:37.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:37.186: INFO: Number of nodes with available pods: 0 May 7 22:30:37.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:38.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:38.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:38.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:38.189: INFO: Number of nodes with available pods: 0 May 7 22:30:38.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:39.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:39.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:39.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:39.186: INFO: Number of nodes with available pods: 0 May 7 22:30:39.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:40.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:40.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:40.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:40.188: INFO: Number of nodes with available pods: 0 May 7 22:30:40.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:41.182: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:41.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:41.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:41.185: INFO: Number of nodes with available pods: 0 May 7 22:30:41.185: INFO: Node node1 is running more than one daemon pod May 7 22:30:42.188: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:42.188: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:42.188: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:42.191: INFO: Number of nodes with available pods: 0 May 7 22:30:42.191: INFO: Node node1 is running more than one daemon pod May 7 22:30:43.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:43.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:43.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:43.187: INFO: Number of nodes with available pods: 0 May 7 22:30:43.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:44.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:44.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:44.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:44.187: INFO: Number of nodes with available pods: 0 May 7 22:30:44.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:45.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:45.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:45.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:45.187: INFO: Number of nodes with available pods: 0 May 7 22:30:45.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:46.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:46.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:46.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:46.187: INFO: Number of nodes with available pods: 0 May 7 22:30:46.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:47.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:47.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:47.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:47.188: INFO: Number of nodes with available pods: 0 May 7 22:30:47.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:48.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:48.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:48.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:48.187: INFO: Number of nodes with available pods: 0 May 7 22:30:48.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:49.182: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:49.182: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:49.182: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:49.186: INFO: Number of nodes with available pods: 0 May 7 22:30:49.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:50.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:50.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:50.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:50.189: INFO: Number of nodes with available pods: 0 May 7 22:30:50.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:51.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:51.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:51.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:51.187: INFO: Number of nodes with available pods: 0 May 7 22:30:51.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:52.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:52.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:52.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:52.189: INFO: Number of nodes with available pods: 0 May 7 22:30:52.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:53.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:53.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:53.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:53.186: INFO: Number of nodes with available pods: 0 May 7 22:30:53.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:54.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:54.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:54.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:54.186: INFO: Number of nodes with available pods: 0 May 7 22:30:54.186: INFO: Node node1 is running more than one daemon pod May 7 22:30:55.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:55.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:55.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:55.189: INFO: Number of nodes with available pods: 0 May 7 22:30:55.189: INFO: Node node1 is running more than one daemon pod May 7 22:30:56.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:56.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:56.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:56.187: INFO: Number of nodes with available pods: 0 May 7 22:30:56.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:57.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:57.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:57.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:57.187: INFO: Number of nodes with available pods: 0 May 7 22:30:57.187: INFO: Node node1 is running more than one daemon pod May 7 22:30:58.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:58.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:58.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:58.188: INFO: Number of nodes with available pods: 0 May 7 22:30:58.188: INFO: Node node1 is running more than one daemon pod May 7 22:30:59.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:59.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:59.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:30:59.187: INFO: Number of nodes with available pods: 0 May 7 22:30:59.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:00.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:00.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:00.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:00.190: INFO: Number of nodes with available pods: 0 May 7 22:31:00.190: INFO: Node node1 is running more than one daemon pod May 7 22:31:01.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:01.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:01.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:01.186: INFO: Number of nodes with available pods: 0 May 7 22:31:01.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:02.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:02.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:02.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:02.187: INFO: Number of nodes with available pods: 0 May 7 22:31:02.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:03.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:03.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:03.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:03.187: INFO: Number of nodes with available pods: 0 May 7 22:31:03.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:04.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:04.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:04.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:04.188: INFO: Number of nodes with available pods: 0 May 7 22:31:04.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:05.182: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:05.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:05.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:05.185: INFO: Number of nodes with available pods: 0 May 7 22:31:05.185: INFO: Node node1 is running more than one daemon pod May 7 22:31:06.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:06.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:06.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:06.186: INFO: Number of nodes with available pods: 0 May 7 22:31:06.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:07.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:07.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:07.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:07.188: INFO: Number of nodes with available pods: 0 May 7 22:31:07.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:08.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:08.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:08.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:08.186: INFO: Number of nodes with available pods: 0 May 7 22:31:08.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:09.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:09.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:09.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:09.186: INFO: Number of nodes with available pods: 0 May 7 22:31:09.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:10.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:10.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:10.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:10.188: INFO: Number of nodes with available pods: 0 May 7 22:31:10.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:11.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:11.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:11.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:11.189: INFO: Number of nodes with available pods: 0 May 7 22:31:11.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:12.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:12.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:12.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:12.188: INFO: Number of nodes with available pods: 0 May 7 22:31:12.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:13.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:13.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:13.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:13.187: INFO: Number of nodes with available pods: 0 May 7 22:31:13.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:14.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:14.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:14.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:14.186: INFO: Number of nodes with available pods: 0 May 7 22:31:14.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:15.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:15.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:15.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:15.186: INFO: Number of nodes with available pods: 0 May 7 22:31:15.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:16.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:16.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:16.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:16.189: INFO: Number of nodes with available pods: 0 May 7 22:31:16.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:17.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:17.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:17.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:17.187: INFO: Number of nodes with available pods: 0 May 7 22:31:17.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:18.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:18.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:18.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:18.188: INFO: Number of nodes with available pods: 0 May 7 22:31:18.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:19.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:19.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:19.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:19.186: INFO: Number of nodes with available pods: 0 May 7 22:31:19.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:20.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:20.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:20.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:20.189: INFO: Number of nodes with available pods: 0 May 7 22:31:20.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:21.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:21.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:21.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:21.187: INFO: Number of nodes with available pods: 0 May 7 22:31:21.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:22.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:22.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:22.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:22.188: INFO: Number of nodes with available pods: 0 May 7 22:31:22.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:23.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:23.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:23.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:23.189: INFO: Number of nodes with available pods: 0 May 7 22:31:23.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:24.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:24.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:24.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:24.187: INFO: Number of nodes with available pods: 0 May 7 22:31:24.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:25.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:25.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:25.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:25.187: INFO: Number of nodes with available pods: 0 May 7 22:31:25.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:26.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:26.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:26.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:26.186: INFO: Number of nodes with available pods: 0 May 7 22:31:26.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:27.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:27.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:27.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:27.188: INFO: Number of nodes with available pods: 0 May 7 22:31:27.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:28.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:28.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:28.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:28.186: INFO: Number of nodes with available pods: 0 May 7 22:31:28.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:29.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:29.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:29.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:29.188: INFO: Number of nodes with available pods: 0 May 7 22:31:29.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:30.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:30.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:30.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:30.187: INFO: Number of nodes with available pods: 0 May 7 22:31:30.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:31.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:31.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:31.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:31.189: INFO: Number of nodes with available pods: 0 May 7 22:31:31.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:32.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:32.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:32.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:32.186: INFO: Number of nodes with available pods: 0 May 7 22:31:32.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:33.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:33.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:33.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:33.186: INFO: Number of nodes with available pods: 0 May 7 22:31:33.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:34.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:34.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:34.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:34.187: INFO: Number of nodes with available pods: 0 May 7 22:31:34.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:35.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:35.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:35.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:35.188: INFO: Number of nodes with available pods: 0 May 7 22:31:35.188: INFO: Node node1 is running more than one daemon pod May 7 22:31:36.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:36.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:36.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:36.189: INFO: Number of nodes with available pods: 0 May 7 22:31:36.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:37.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:37.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:37.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:37.187: INFO: Number of nodes with available pods: 0 May 7 22:31:37.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:38.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:38.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:38.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:38.187: INFO: Number of nodes with available pods: 0 May 7 22:31:38.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:39.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:39.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:39.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:39.186: INFO: Number of nodes with available pods: 0 May 7 22:31:39.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:40.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:40.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:40.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:40.186: INFO: Number of nodes with available pods: 0 May 7 22:31:40.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:41.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:41.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:41.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:41.186: INFO: Number of nodes with available pods: 0 May 7 22:31:41.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:42.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:42.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:42.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:42.189: INFO: Number of nodes with available pods: 0 May 7 22:31:42.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:43.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:43.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:43.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:43.190: INFO: Number of nodes with available pods: 0 May 7 22:31:43.190: INFO: Node node1 is running more than one daemon pod May 7 22:31:44.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:44.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:44.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:44.186: INFO: Number of nodes with available pods: 0 May 7 22:31:44.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:45.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:45.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:45.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:45.186: INFO: Number of nodes with available pods: 0 May 7 22:31:45.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:46.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:46.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:46.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:46.186: INFO: Number of nodes with available pods: 0 May 7 22:31:46.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:47.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:47.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:47.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:47.187: INFO: Number of nodes with available pods: 0 May 7 22:31:47.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:48.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:48.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:48.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:48.189: INFO: Number of nodes with available pods: 0 May 7 22:31:48.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:49.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:49.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:49.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:49.186: INFO: Number of nodes with available pods: 0 May 7 22:31:49.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:50.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:50.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:50.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:50.187: INFO: Number of nodes with available pods: 0 May 7 22:31:50.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:51.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:51.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:51.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:51.187: INFO: Number of nodes with available pods: 0 May 7 22:31:51.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:52.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:52.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:52.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:52.187: INFO: Number of nodes with available pods: 0 May 7 22:31:52.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:53.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:53.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:53.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:53.186: INFO: Number of nodes with available pods: 0 May 7 22:31:53.186: INFO: Node node1 is running more than one daemon pod May 7 22:31:54.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:54.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:54.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:54.187: INFO: Number of nodes with available pods: 0 May 7 22:31:54.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:55.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:55.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:55.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:55.190: INFO: Number of nodes with available pods: 0 May 7 22:31:55.190: INFO: Node node1 is running more than one daemon pod May 7 22:31:56.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:56.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:56.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:56.189: INFO: Number of nodes with available pods: 0 May 7 22:31:56.189: INFO: Node node1 is running more than one daemon pod May 7 22:31:57.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:57.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:57.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:57.185: INFO: Number of nodes with available pods: 0 May 7 22:31:57.185: INFO: Node node1 is running more than one daemon pod May 7 22:31:58.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:58.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:58.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:58.187: INFO: Number of nodes with available pods: 0 May 7 22:31:58.187: INFO: Node node1 is running more than one daemon pod May 7 22:31:59.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:59.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:59.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:31:59.189: INFO: Number of nodes with available pods: 0 May 7 22:31:59.189: INFO: Node node1 is running more than one daemon pod May 7 22:32:00.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:00.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:00.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:00.188: INFO: Number of nodes with available pods: 0 May 7 22:32:00.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:01.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:01.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:01.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:01.186: INFO: Number of nodes with available pods: 0 May 7 22:32:01.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:02.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:02.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:02.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:02.189: INFO: Number of nodes with available pods: 0 May 7 22:32:02.189: INFO: Node node1 is running more than one daemon pod May 7 22:32:03.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:03.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:03.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:03.189: INFO: Number of nodes with available pods: 0 May 7 22:32:03.189: INFO: Node node1 is running more than one daemon pod May 7 22:32:04.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:04.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:04.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:04.186: INFO: Number of nodes with available pods: 0 May 7 22:32:04.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:05.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:05.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:05.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:05.186: INFO: Number of nodes with available pods: 0 May 7 22:32:05.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:06.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:06.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:06.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:06.188: INFO: Number of nodes with available pods: 0 May 7 22:32:06.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:07.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:07.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:07.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:07.187: INFO: Number of nodes with available pods: 0 May 7 22:32:07.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:08.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:08.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:08.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:08.188: INFO: Number of nodes with available pods: 0 May 7 22:32:08.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:09.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:09.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:09.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:09.187: INFO: Number of nodes with available pods: 0 May 7 22:32:09.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:10.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:10.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:10.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:10.186: INFO: Number of nodes with available pods: 0 May 7 22:32:10.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:11.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:11.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:11.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:11.188: INFO: Number of nodes with available pods: 0 May 7 22:32:11.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:12.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:12.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:12.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:12.187: INFO: Number of nodes with available pods: 0 May 7 22:32:12.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:13.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:13.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:13.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:13.186: INFO: Number of nodes with available pods: 0 May 7 22:32:13.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:14.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:14.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:14.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:14.188: INFO: Number of nodes with available pods: 0 May 7 22:32:14.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:15.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:15.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:15.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:15.188: INFO: Number of nodes with available pods: 0 May 7 22:32:15.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:16.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:16.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:16.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:16.188: INFO: Number of nodes with available pods: 0 May 7 22:32:16.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:17.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:17.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:17.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:17.186: INFO: Number of nodes with available pods: 0 May 7 22:32:17.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:18.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:18.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:18.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:18.186: INFO: Number of nodes with available pods: 0 May 7 22:32:18.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:19.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:19.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:19.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:19.187: INFO: Number of nodes with available pods: 0 May 7 22:32:19.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:20.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:20.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:20.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:20.188: INFO: Number of nodes with available pods: 0 May 7 22:32:20.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:21.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:21.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:21.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:21.186: INFO: Number of nodes with available pods: 0 May 7 22:32:21.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:22.187: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:22.187: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:22.187: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:22.189: INFO: Number of nodes with available pods: 0 May 7 22:32:22.189: INFO: Node node1 is running more than one daemon pod May 7 22:32:23.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:23.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:23.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:23.188: INFO: Number of nodes with available pods: 0 May 7 22:32:23.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:24.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:24.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:24.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:24.188: INFO: Number of nodes with available pods: 0 May 7 22:32:24.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:25.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:25.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:25.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:25.187: INFO: Number of nodes with available pods: 0 May 7 22:32:25.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:26.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:26.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:26.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:26.188: INFO: Number of nodes with available pods: 0 May 7 22:32:26.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:27.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:27.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:27.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:27.187: INFO: Number of nodes with available pods: 0 May 7 22:32:27.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:28.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:28.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:28.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:28.187: INFO: Number of nodes with available pods: 0 May 7 22:32:28.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:29.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:29.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:29.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:29.186: INFO: Number of nodes with available pods: 0 May 7 22:32:29.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:30.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:30.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:30.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:30.189: INFO: Number of nodes with available pods: 0 May 7 22:32:30.189: INFO: Node node1 is running more than one daemon pod May 7 22:32:31.182: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:31.182: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:31.182: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:31.185: INFO: Number of nodes with available pods: 0 May 7 22:32:31.185: INFO: Node node1 is running more than one daemon pod May 7 22:32:32.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:32.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:32.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:32.186: INFO: Number of nodes with available pods: 0 May 7 22:32:32.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:33.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:33.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:33.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:33.186: INFO: Number of nodes with available pods: 0 May 7 22:32:33.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:34.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:34.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:34.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:34.185: INFO: Number of nodes with available pods: 0 May 7 22:32:34.185: INFO: Node node1 is running more than one daemon pod May 7 22:32:35.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:35.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:35.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:35.187: INFO: Number of nodes with available pods: 0 May 7 22:32:35.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:36.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:36.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:36.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:36.187: INFO: Number of nodes with available pods: 0 May 7 22:32:36.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:37.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:37.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:37.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:37.186: INFO: Number of nodes with available pods: 0 May 7 22:32:37.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:38.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:38.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:38.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:38.186: INFO: Number of nodes with available pods: 0 May 7 22:32:38.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:39.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:39.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:39.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:39.187: INFO: Number of nodes with available pods: 0 May 7 22:32:39.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:40.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:40.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:40.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:40.186: INFO: Number of nodes with available pods: 0 May 7 22:32:40.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:41.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:41.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:41.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:41.187: INFO: Number of nodes with available pods: 0 May 7 22:32:41.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:42.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:42.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:42.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:42.189: INFO: Number of nodes with available pods: 0 May 7 22:32:42.189: INFO: Node node1 is running more than one daemon pod May 7 22:32:43.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:43.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:43.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:43.189: INFO: Number of nodes with available pods: 0 May 7 22:32:43.189: INFO: Node node1 is running more than one daemon pod May 7 22:32:44.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:44.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:44.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:44.186: INFO: Number of nodes with available pods: 0 May 7 22:32:44.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:45.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:45.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:45.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:45.186: INFO: Number of nodes with available pods: 0 May 7 22:32:45.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:46.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:46.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:46.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:46.188: INFO: Number of nodes with available pods: 0 May 7 22:32:46.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:47.186: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:47.186: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:47.186: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:47.189: INFO: Number of nodes with available pods: 0 May 7 22:32:47.189: INFO: Node node1 is running more than one daemon pod May 7 22:32:48.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:48.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:48.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:48.188: INFO: Number of nodes with available pods: 0 May 7 22:32:48.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:49.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:49.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:49.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:49.188: INFO: Number of nodes with available pods: 0 May 7 22:32:49.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:50.185: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:50.185: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:50.185: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:50.188: INFO: Number of nodes with available pods: 0 May 7 22:32:50.188: INFO: Node node1 is running more than one daemon pod May 7 22:32:51.184: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:51.184: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:51.184: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:51.187: INFO: Number of nodes with available pods: 0 May 7 22:32:51.187: INFO: Node node1 is running more than one daemon pod May 7 22:32:52.183: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:52.183: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:52.183: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:52.186: INFO: Number of nodes with available pods: 0 May 7 22:32:52.186: INFO: Node node1 is running more than one daemon pod May 7 22:32:52.190: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:52.190: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:52.190: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:52.193: INFO: Number of nodes with available pods: 0 May 7 22:32:52.193: INFO: Node node1 is running more than one daemon pod May 7 22:32:52.193: FAIL: error waiting for daemon pod to start Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/apps.glob..func3.3() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:163 +0x4f0 k8s.io/kubernetes/test/e2e.RunE2ETests(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x345 k8s.io/kubernetes/test/e2e.TestE2E(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:145 +0x2b testing.tRunner(0xc00211a180, 0x4de37a0) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:100 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-578, will wait for the garbage collector to delete the pods May 7 22:32:52.257: INFO: Deleting DaemonSet.extensions daemon-set took: 6.165797ms May 7 22:32:52.957: INFO: Terminating DaemonSet.extensions daemon-set pods took: 700.314169ms May 7 22:32:54.059: INFO: Number of nodes with available pods: 0 May 7 22:32:54.059: INFO: Number of running nodes: 0, number of available pods: 0 May 7 22:32:54.062: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"selfLink":"/apis/apps/v1/namespaces/daemonsets-578/daemonsets","resourceVersion":"54273"},"items":null} May 7 22:32:54.064: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"selfLink":"/api/v1/namespaces/daemonsets-578/pods","resourceVersion":"54273"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 STEP: Collecting events from namespace "daemonsets-578". STEP: Found 20 events. May 7 22:32:54.078: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-6s4b8: { } Scheduled: Successfully assigned daemonsets-578/daemon-set-6s4b8 to node2 May 7 22:32:54.078: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-gvr2n: { } Scheduled: Successfully assigned daemonsets-578/daemon-set-gvr2n to node1 May 7 22:32:54.078: INFO: At 2021-05-07 22:27:52 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-gvr2n May 7 22:32:54.078: INFO: At 2021-05-07 22:27:52 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-6s4b8 May 7 22:32:54.078: INFO: At 2021-05-07 22:27:53 +0000 UTC - event for daemon-set-6s4b8: {multus } AddedInterface: Add eth0 [10.244.4.253/24] May 7 22:32:54.078: INFO: At 2021-05-07 22:27:53 +0000 UTC - event for daemon-set-6s4b8: {kubelet node2} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:32:54.078: INFO: At 2021-05-07 22:27:53 +0000 UTC - event for daemon-set-gvr2n: {multus } AddedInterface: Add eth0 [10.244.3.212/24] May 7 22:32:54.078: INFO: At 2021-05-07 22:27:53 +0000 UTC - event for daemon-set-gvr2n: {kubelet node1} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:32:54.078: INFO: At 2021-05-07 22:27:54 +0000 UTC - event for daemon-set-6s4b8: {kubelet node2} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:32:54.078: INFO: At 2021-05-07 22:27:54 +0000 UTC - event for daemon-set-6s4b8: {kubelet node2} Failed: Error: ErrImagePull May 7 22:32:54.078: INFO: At 2021-05-07 22:27:54 +0000 UTC - event for daemon-set-gvr2n: {kubelet node1} Failed: Error: ErrImagePull May 7 22:32:54.078: INFO: At 2021-05-07 22:27:54 +0000 UTC - event for daemon-set-gvr2n: {kubelet node1} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:32:54.078: INFO: At 2021-05-07 22:27:55 +0000 UTC - event for daemon-set-6s4b8: {kubelet node2} SandboxChanged: Pod sandbox changed, it will be killed and re-created. May 7 22:32:54.078: INFO: At 2021-05-07 22:27:55 +0000 UTC - event for daemon-set-gvr2n: {kubelet node1} SandboxChanged: Pod sandbox changed, it will be killed and re-created. May 7 22:32:54.078: INFO: At 2021-05-07 22:27:57 +0000 UTC - event for daemon-set-6s4b8: {kubelet node2} Failed: Error: ImagePullBackOff May 7 22:32:54.078: INFO: At 2021-05-07 22:27:57 +0000 UTC - event for daemon-set-6s4b8: {kubelet node2} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:32:54.078: INFO: At 2021-05-07 22:27:57 +0000 UTC - event for daemon-set-6s4b8: {multus } AddedInterface: Add eth0 [10.244.4.254/24] May 7 22:32:54.078: INFO: At 2021-05-07 22:27:57 +0000 UTC - event for daemon-set-gvr2n: {multus } AddedInterface: Add eth0 [10.244.3.213/24] May 7 22:32:54.078: INFO: At 2021-05-07 22:27:57 +0000 UTC - event for daemon-set-gvr2n: {kubelet node1} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:32:54.078: INFO: At 2021-05-07 22:27:57 +0000 UTC - event for daemon-set-gvr2n: {kubelet node1} Failed: Error: ImagePullBackOff May 7 22:32:54.080: INFO: POD NODE PHASE GRACE CONDITIONS May 7 22:32:54.080: INFO: May 7 22:32:54.084: INFO: Logging node info for node master1 May 7 22:32:54.087: INFO: Node Info: &Node{ObjectMeta:{master1 /api/v1/nodes/master1 7277f528-99fb-4be3-a928-27761a4599e8 54257 0 2021-05-07 19:59:27 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master1 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"a2:74:f5:d6:48:e4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.202 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/master.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 19:59:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 19:59:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.0.0/24\"":{}},"f:taints":{}}}} {nfd-master Update v1 2021-05-07 20:08:42 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/master.version":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.0.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.0.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:15 +0000 UTC,LastTransitionTime:2021-05-07 20:05:15 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:50 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:50 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:50 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:32:50 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.202,},NodeAddress{Type:Hostname,Address:master1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:44253340a37b4ed7bf5b3a3547b5f57d,SystemUUID:00ACFB60-0631-E711-906E-0017A4403562,BootID:2a44f9c3-2714-4b5c-975d-25d069f66483,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:9d07c391aeb1a9d02eb4343c113ed01825227c70c32b3cae861711f90191b0fd quay.io/coreos/kube-rbac-proxy:v0.4.1],SizeBytes:41317870,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[quay.io/coreos/prometheus-operator@sha256:a54e806fb27d2fb0251da4f3b2a3bb5320759af63a54a755788304775f2384a7 quay.io/coreos/prometheus-operator:v0.40.0],SizeBytes:38238457,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[registry@sha256:1cd9409a311350c3072fe510b52046f104416376c126a479cef9a4dfe692cf57 registry:2.7.0],SizeBytes:24191168,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 tas-controller:latest localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[nginx@sha256:a97eb9ecc708c8aa715ccfb5e9338f5456e4b65575daf304f108301f3b497314 nginx:1.19.2-alpine],SizeBytes:22052669,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 tas-extender:latest localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[@ :],SizeBytes:5577654,},ContainerImage{Names:[alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a alpine:3.12.1],SizeBytes:5573013,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:32:54.087: INFO: Logging kubelet events for node master1 May 7 22:32:54.089: INFO: Logging pods the kubelet thinks is on node master1 May 7 22:32:54.104: INFO: kube-multus-ds-amd64-8tjh4 started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.104: INFO: Container kube-multus ready: true, restart count 1 May 7 22:32:54.104: INFO: docker-registry-docker-registry-56cbc7bc58-267wq started at 2021-05-07 20:05:51 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.104: INFO: Container docker-registry ready: true, restart count 0 May 7 22:32:54.104: INFO: Container nginx ready: true, restart count 0 May 7 22:32:54.104: INFO: prometheus-operator-5bb8cb9d8f-xqpnw started at 2021-05-07 20:12:35 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.104: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:32:54.104: INFO: Container prometheus-operator ready: true, restart count 0 May 7 22:32:54.104: INFO: kube-proxy-qpvcb started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.104: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:32:54.104: INFO: kube-controller-manager-master1 started at 2021-05-07 20:04:26 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.105: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:32:54.105: INFO: kube-scheduler-master1 started at 2021-05-07 20:15:37 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.105: INFO: Container kube-scheduler ready: true, restart count 0 May 7 22:32:54.105: INFO: kube-flannel-nj6vr started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:32:54.105: INFO: Init container install-cni ready: true, restart count 0 May 7 22:32:54.105: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:32:54.105: INFO: coredns-7677f9bb54-wvd65 started at 2021-05-07 20:02:30 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.105: INFO: Container coredns ready: true, restart count 2 May 7 22:32:54.105: INFO: node-feature-discovery-controller-5bf5c49849-z2bj7 started at 2021-05-07 20:08:34 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.105: INFO: Container nfd-controller ready: true, restart count 0 May 7 22:32:54.105: INFO: node-exporter-9sm5v started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.105: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:32:54.105: INFO: Container node-exporter ready: true, restart count 0 May 7 22:32:54.105: INFO: kube-apiserver-master1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.105: INFO: Container kube-apiserver ready: true, restart count 0 W0507 22:32:54.118180 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:32:54.150: INFO: Latency metrics for node master1 May 7 22:32:54.150: INFO: Logging node info for node master2 May 7 22:32:54.153: INFO: Node Info: &Node{ObjectMeta:{master2 /api/v1/nodes/master2 8193aa97-7914-4d63-b6cf-a7ceb8fe519c 54242 0 2021-05-07 20:00:06 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master2 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"86:88:6a:bc:18:32"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.203 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {kube-controller-manager Update v1 2021-05-07 20:01:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.1.0/24\"":{}},"f:taints":{}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}}]},Spec:NodeSpec{PodCIDR:10.244.1.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234767872 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324603904 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:58 +0000 UTC,LastTransitionTime:2021-05-07 20:04:58 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:46 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:46 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:46 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:32:46 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.203,},NodeAddress{Type:Hostname,Address:master2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:cf652b4fb7284de2aaafc5f52f51e312,SystemUUID:00A0DE53-E51D-E711-906E-0017A4403562,BootID:df4da196-5a1c-4b40-aef7-034e79f7a8e2,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:32:54.153: INFO: Logging kubelet events for node master2 May 7 22:32:54.156: INFO: Logging pods the kubelet thinks is on node master2 May 7 22:32:54.171: INFO: dns-autoscaler-5b7b5c9b6f-flqh2 started at 2021-05-07 20:02:33 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.171: INFO: Container autoscaler ready: true, restart count 2 May 7 22:32:54.171: INFO: node-exporter-6nqvj started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.171: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:32:54.171: INFO: Container node-exporter ready: true, restart count 0 May 7 22:32:54.171: INFO: kube-apiserver-master2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.171: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:32:54.171: INFO: kube-controller-manager-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.171: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:32:54.171: INFO: kube-scheduler-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.171: INFO: Container kube-scheduler ready: true, restart count 2 May 7 22:32:54.171: INFO: kube-proxy-fg5dt started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.171: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:32:54.171: INFO: kube-flannel-wwlww started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:32:54.171: INFO: Init container install-cni ready: true, restart count 0 May 7 22:32:54.171: INFO: Container kube-flannel ready: true, restart count 1 May 7 22:32:54.171: INFO: kube-multus-ds-amd64-44vrh started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.171: INFO: Container kube-multus ready: true, restart count 1 W0507 22:32:54.183204 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:32:54.206: INFO: Latency metrics for node master2 May 7 22:32:54.206: INFO: Logging node info for node master3 May 7 22:32:54.209: INFO: Node Info: &Node{ObjectMeta:{master3 /api/v1/nodes/master3 27e1bfdf-bb8c-4924-9488-acacef172e76 54245 0 2021-05-07 20:00:17 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master3 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"de:31:a8:23:73:1a"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.204 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:18 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.2.0/24\"":{}},"f:taints":{}}}}]},Spec:NodeSpec{PodCIDR:10.244.2.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.2.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:10 +0000 UTC,LastTransitionTime:2021-05-07 20:04:10 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:47 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:47 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:47 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:32:47 +0000 UTC,LastTransitionTime:2021-05-07 20:03:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.204,},NodeAddress{Type:Hostname,Address:master3,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:01ba71adbf0d4ef79a9af064c18faf21,SystemUUID:008B1444-141E-E711-906E-0017A4403562,BootID:1692e58d-c13c-425c-b11a-62d901f965ec,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:32:54.210: INFO: Logging kubelet events for node master3 May 7 22:32:54.211: INFO: Logging pods the kubelet thinks is on node master3 May 7 22:32:54.227: INFO: coredns-7677f9bb54-pj7xl started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.227: INFO: Container coredns ready: true, restart count 2 May 7 22:32:54.227: INFO: node-exporter-tsk7w started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.227: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:32:54.227: INFO: Container node-exporter ready: true, restart count 0 May 7 22:32:54.227: INFO: kube-apiserver-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.227: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:32:54.227: INFO: kube-controller-manager-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.227: INFO: Container kube-controller-manager ready: true, restart count 3 May 7 22:32:54.227: INFO: kube-scheduler-master3 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.227: INFO: Container kube-scheduler ready: true, restart count 2 May 7 22:32:54.227: INFO: kube-proxy-lvj72 started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.227: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:32:54.227: INFO: kube-flannel-j2xn4 started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:32:54.227: INFO: Init container install-cni ready: true, restart count 1 May 7 22:32:54.227: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:32:54.227: INFO: kube-multus-ds-amd64-hhqgw started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.227: INFO: Container kube-multus ready: true, restart count 1 W0507 22:32:54.239547 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:32:54.268: INFO: Latency metrics for node master3 May 7 22:32:54.268: INFO: Logging node info for node node1 May 7 22:32:54.270: INFO: Node Info: &Node{ObjectMeta:{node1 /api/v1/nodes/node1 24d047f7-eb29-4f1d-96d0-63b225220bd5 54261 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node1 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"da:1d:6f:d2:a8:b4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.207 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.3.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:09 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {kubelet Update v1 2021-05-07 22:22:09 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:example.com/fakecpu":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {e2e.test Update v1 2021-05-07 22:22:48 +0000 UTC FieldsV1 {"f:status":{"f:capacity":{"f:example.com/fakecpu":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.3.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},example.com/fakecpu: {{1 3} {} 1k DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},example.com/fakecpu: {{1 3} {} 1k DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:03:55 +0000 UTC,LastTransitionTime:2021-05-07 20:03:55 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:51 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:51 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:51 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:32:51 +0000 UTC,LastTransitionTime:2021-05-07 20:03:44 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.207,},NodeAddress{Type:Hostname,Address:node1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:d79c3a817fbd4f03a173930e545bb174,SystemUUID:00CDA902-D022-E711-906E-0017A4403562,BootID:53771151-d654-4c88-80fe-48032d3317a5,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[@ :],SizeBytes:1002488002,},ContainerImage{Names:[opnfv/barometer-collectd@sha256:ed5c574f653e2a39e784ff322033a2319aafde7366c803a88f20f7a2a8bc1efb opnfv/barometer-collectd:stable],SizeBytes:825413035,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[golang@sha256:1636899c10870ab66c48d960a9df620f4f9e86a0c72fbacf36032d27404e7e6c golang:alpine3.12],SizeBytes:301156062,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[grafana/grafana@sha256:89304bc2335f4976618548d7b93d165ed67369d3a051d2f627fc4e0aa3d0aff1 grafana/grafana:7.1.0],SizeBytes:179601493,},ContainerImage{Names:[quay.io/prometheus/prometheus@sha256:d4ba4dd1a9ebb90916d0bfed3c204adcb118ed24546bf8dd2e6b30fc0fd2009e quay.io/prometheus/prometheus:v2.20.0],SizeBytes:144886595,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[directxman12/k8s-prometheus-adapter-amd64@sha256:b63dc612e3cb73f79d2401a4516f794f9f0a83002600ca72e675e41baecff437 directxman12/k8s-prometheus-adapter-amd64:v0.6.0],SizeBytes:53267842,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d nfvpe/sriov-device-plugin:latest localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[quay.io/coreos/prometheus-config-reloader@sha256:c679a143b24b7731ad1577a9865aa3805426cbf1b25e30807b951dff68466ffd quay.io/coreos/prometheus-config-reloader:v0.40.0],SizeBytes:10131705,},ContainerImage{Names:[jimmidyson/configmap-reload@sha256:d107c7a235c266273b1c3502a391fec374430e5625539403d0de797fa9c556a2 jimmidyson/configmap-reload:v0.3.0],SizeBytes:9700438,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[appropriate/curl@sha256:027a0ad3c69d085fea765afca9984787b780c172cead6502fec989198b98d8bb appropriate/curl:edge],SizeBytes:5654234,},ContainerImage{Names:[alpine@sha256:36553b10a4947067b9fbb7d532951066293a68eae893beba1d9235f7d11a20ad alpine:3.12],SizeBytes:5581415,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[gcr.io/authenticated-image-pulling/alpine@sha256:7ff177862cb50c602bfe81f805969412e619c054a2bbead977d0c276988aa4a0 gcr.io/authenticated-image-pulling/alpine:3.7],SizeBytes:4206620,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:32:54.271: INFO: Logging kubelet events for node node1 May 7 22:32:54.273: INFO: Logging pods the kubelet thinks is on node node1 May 7 22:32:54.292: INFO: cmk-gjhf2 started at 2021-05-07 20:11:48 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.292: INFO: Container nodereport ready: true, restart count 0 May 7 22:32:54.292: INFO: Container reconcile ready: true, restart count 0 May 7 22:32:54.292: INFO: kube-multus-ds-amd64-fxgdb started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.292: INFO: Container kube-multus ready: true, restart count 1 May 7 22:32:54.292: INFO: prometheus-k8s-0 started at 2021-05-07 20:12:50 +0000 UTC (0+5 container statuses recorded) May 7 22:32:54.292: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:32:54.292: INFO: Container grafana ready: true, restart count 0 May 7 22:32:54.292: INFO: Container prometheus ready: true, restart count 1 May 7 22:32:54.292: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:32:54.292: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:32:54.292: INFO: kube-flannel-qm7lv started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:32:54.292: INFO: Init container install-cni ready: true, restart count 2 May 7 22:32:54.292: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:32:54.292: INFO: nginx-proxy-node1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.292: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:32:54.292: INFO: kubernetes-metrics-scraper-678c97765c-g7srv started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.292: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:32:54.292: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.292: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:32:54.292: INFO: node-exporter-mpq58 started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.292: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:32:54.292: INFO: Container node-exporter ready: true, restart count 0 May 7 22:32:54.292: INFO: collectd-tmjfs started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:32:54.292: INFO: Container collectd ready: true, restart count 0 May 7 22:32:54.292: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:32:54.292: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:32:54.292: INFO: node-feature-discovery-worker-xvbpd started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.292: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:32:54.292: INFO: kube-proxy-bms7z started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.292: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:32:54.292: INFO: cmk-init-discover-node1-krbjn started at 2021-05-07 20:11:05 +0000 UTC (0+3 container statuses recorded) May 7 22:32:54.292: INFO: Container discover ready: false, restart count 0 May 7 22:32:54.292: INFO: Container init ready: false, restart count 0 May 7 22:32:54.292: INFO: Container install ready: false, restart count 0 W0507 22:32:54.306151 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:32:54.336: INFO: Latency metrics for node node1 May 7 22:32:54.336: INFO: Logging node info for node node2 May 7 22:32:54.338: INFO: Node Info: &Node{ObjectMeta:{node2 /api/v1/nodes/node2 eae422ac-f6f0-4e9a-961d-e133dffc36be 54260 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node2 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"22:df:da:84:9b:00"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.208 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.4.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:31 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {kubelet Update v1 2021-05-07 20:11:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.4.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:02 +0000 UTC,LastTransitionTime:2021-05-07 20:05:02 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:51 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:51 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:32:51 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:32:51 +0000 UTC,LastTransitionTime:2021-05-07 20:02:07 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.208,},NodeAddress{Type:Hostname,Address:node2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:6f56c5a750d0441dba0ffa6273fb1a17,SystemUUID:80B3CD56-852F-E711-906E-0017A4403562,BootID:98b263e9-3136-45ed-9b07-5f5b6b9d69b8,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[k8s.gcr.io/etcd@sha256:4ad90a11b55313b182afc186b9876c8e891531b8db4c9bf1541953021618d0e2 k8s.gcr.io/etcd:3.4.13-0],SizeBytes:253392289,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/sample-apiserver@sha256:ff02aacd9766d597883fabafc7ad604c719a57611db1bcc1564c69a45b000a55 gcr.io/kubernetes-e2e-test-images/sample-apiserver:1.17],SizeBytes:60684726,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:32:54.339: INFO: Logging kubelet events for node node2 May 7 22:32:54.341: INFO: Logging pods the kubelet thinks is on node node2 May 7 22:32:54.357: INFO: nginx-proxy-node2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.357: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:32:54.357: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.357: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:32:54.357: INFO: kube-proxy-rgw7h started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.357: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:32:54.357: INFO: node-feature-discovery-worker-wp5n6 started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.357: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:32:54.357: INFO: node-exporter-4bcls started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.357: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:32:54.357: INFO: Container node-exporter ready: true, restart count 0 May 7 22:32:54.357: INFO: kube-flannel-htqkx started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:32:54.357: INFO: Init container install-cni ready: true, restart count 2 May 7 22:32:54.357: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:32:54.357: INFO: kube-multus-ds-amd64-g98hm started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.357: INFO: Container kube-multus ready: true, restart count 1 May 7 22:32:54.357: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f started at 2021-05-07 20:15:36 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.357: INFO: Container tas-controller ready: true, restart count 0 May 7 22:32:54.357: INFO: Container tas-extender ready: true, restart count 0 May 7 22:32:54.357: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.357: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:32:54.357: INFO: cmk-init-discover-node2-kd9gg started at 2021-05-07 20:11:26 +0000 UTC (0+3 container statuses recorded) May 7 22:32:54.357: INFO: Container discover ready: false, restart count 0 May 7 22:32:54.357: INFO: Container init ready: false, restart count 0 May 7 22:32:54.357: INFO: Container install ready: false, restart count 0 May 7 22:32:54.357: INFO: cmk-gvh7j started at 2021-05-07 20:11:49 +0000 UTC (0+2 container statuses recorded) May 7 22:32:54.357: INFO: Container nodereport ready: true, restart count 0 May 7 22:32:54.357: INFO: Container reconcile ready: true, restart count 0 May 7 22:32:54.357: INFO: cmk-webhook-6c9d5f8578-94s58 started at 2021-05-07 20:11:49 +0000 UTC (0+1 container statuses recorded) May 7 22:32:54.357: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:32:54.357: INFO: collectd-p5gbt started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:32:54.357: INFO: Container collectd ready: true, restart count 0 May 7 22:32:54.357: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:32:54.357: INFO: Container rbac-proxy ready: true, restart count 0 W0507 22:32:54.374763 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:32:54.416: INFO: Latency metrics for node node2 May 7 22:32:54.416: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-578" for this suite. • Failure [302.303 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should run and stop simple daemon [Conformance] [It] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:32:52.193: error waiting for daemon pod to start Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:163 ------------------------------ {"msg":"FAILED [sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","total":17,"completed":3,"skipped":1849,"failed":2,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-api-machinery] Namespaces [Serial] should patch a Namespace [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:32:54.433: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename namespaces STEP: Waiting for a default service account to be provisioned in namespace [It] should patch a Namespace [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: creating a Namespace STEP: patching the Namespace STEP: get the Namespace and ensuring it has the label [AfterEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:32:54.474: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "namespaces-7362" for this suite. STEP: Destroying namespace "nspatchtest-784c691a-c3ca-465d-bb5b-d4ef237574a4-3056" for this suite. •{"msg":"PASSED [sig-api-machinery] Namespaces [Serial] should patch a Namespace [Conformance]","total":17,"completed":4,"skipped":2454,"failed":2,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:32:54.498: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:134 [It] should update pod when spec was updated and update strategy is RollingUpdate [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:32:54.530: INFO: Creating simple daemon set daemon-set STEP: Check that daemon pods launch on every node of the cluster. May 7 22:32:54.539: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:54.539: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:54.539: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:54.541: INFO: Number of nodes with available pods: 0 May 7 22:32:54.541: INFO: Node node1 is running more than one daemon pod May 7 22:32:55.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:55.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:55.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:55.550: INFO: Number of nodes with available pods: 0 May 7 22:32:55.550: INFO: Node node1 is running more than one daemon pod May 7 22:32:56.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:56.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:56.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:56.550: INFO: Number of nodes with available pods: 0 May 7 22:32:56.550: INFO: Node node1 is running more than one daemon pod May 7 22:32:57.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:57.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:57.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:57.549: INFO: Number of nodes with available pods: 0 May 7 22:32:57.549: INFO: Node node1 is running more than one daemon pod May 7 22:32:58.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:58.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:58.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:58.550: INFO: Number of nodes with available pods: 0 May 7 22:32:58.550: INFO: Node node1 is running more than one daemon pod May 7 22:32:59.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:59.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:59.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:32:59.549: INFO: Number of nodes with available pods: 0 May 7 22:32:59.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:00.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:00.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:00.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:00.549: INFO: Number of nodes with available pods: 0 May 7 22:33:00.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:01.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:01.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:01.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:01.549: INFO: Number of nodes with available pods: 0 May 7 22:33:01.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:02.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:02.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:02.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:02.551: INFO: Number of nodes with available pods: 0 May 7 22:33:02.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:03.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:03.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:03.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:03.550: INFO: Number of nodes with available pods: 0 May 7 22:33:03.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:04.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:04.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:04.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:04.551: INFO: Number of nodes with available pods: 0 May 7 22:33:04.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:05.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:05.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:05.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:05.550: INFO: Number of nodes with available pods: 0 May 7 22:33:05.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:06.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:06.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:06.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:06.551: INFO: Number of nodes with available pods: 0 May 7 22:33:06.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:07.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:07.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:07.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:07.550: INFO: Number of nodes with available pods: 0 May 7 22:33:07.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:08.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:08.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:08.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:08.552: INFO: Number of nodes with available pods: 0 May 7 22:33:08.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:09.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:09.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:09.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:09.550: INFO: Number of nodes with available pods: 0 May 7 22:33:09.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:10.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:10.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:10.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:10.549: INFO: Number of nodes with available pods: 0 May 7 22:33:10.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:11.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:11.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:11.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:11.552: INFO: Number of nodes with available pods: 0 May 7 22:33:11.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:12.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:12.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:12.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:12.550: INFO: Number of nodes with available pods: 0 May 7 22:33:12.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:13.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:13.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:13.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:13.550: INFO: Number of nodes with available pods: 0 May 7 22:33:13.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:14.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:14.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:14.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:14.549: INFO: Number of nodes with available pods: 0 May 7 22:33:14.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:15.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:15.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:15.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:15.550: INFO: Number of nodes with available pods: 0 May 7 22:33:15.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:16.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:16.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:16.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:16.550: INFO: Number of nodes with available pods: 0 May 7 22:33:16.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:17.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:17.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:17.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:17.549: INFO: Number of nodes with available pods: 0 May 7 22:33:17.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:18.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:18.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:18.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:18.552: INFO: Number of nodes with available pods: 0 May 7 22:33:18.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:19.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:19.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:19.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:19.552: INFO: Number of nodes with available pods: 0 May 7 22:33:19.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:20.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:20.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:20.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:20.552: INFO: Number of nodes with available pods: 0 May 7 22:33:20.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:21.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:21.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:21.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:21.550: INFO: Number of nodes with available pods: 0 May 7 22:33:21.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:22.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:22.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:22.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:22.550: INFO: Number of nodes with available pods: 0 May 7 22:33:22.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:23.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:23.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:23.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:23.552: INFO: Number of nodes with available pods: 0 May 7 22:33:23.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:24.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:24.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:24.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:24.549: INFO: Number of nodes with available pods: 0 May 7 22:33:24.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:25.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:25.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:25.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:25.549: INFO: Number of nodes with available pods: 0 May 7 22:33:25.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:26.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:26.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:26.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:26.551: INFO: Number of nodes with available pods: 0 May 7 22:33:26.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:27.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:27.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:27.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:27.550: INFO: Number of nodes with available pods: 0 May 7 22:33:27.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:28.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:28.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:28.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:28.550: INFO: Number of nodes with available pods: 0 May 7 22:33:28.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:29.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:29.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:29.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:29.550: INFO: Number of nodes with available pods: 0 May 7 22:33:29.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:30.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:30.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:30.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:30.550: INFO: Number of nodes with available pods: 0 May 7 22:33:30.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:31.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:31.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:31.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:31.552: INFO: Number of nodes with available pods: 0 May 7 22:33:31.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:32.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:32.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:32.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:32.548: INFO: Number of nodes with available pods: 0 May 7 22:33:32.548: INFO: Node node1 is running more than one daemon pod May 7 22:33:33.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:33.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:33.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:33.550: INFO: Number of nodes with available pods: 0 May 7 22:33:33.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:34.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:34.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:34.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:34.551: INFO: Number of nodes with available pods: 0 May 7 22:33:34.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:35.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:35.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:35.550: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:35.552: INFO: Number of nodes with available pods: 0 May 7 22:33:35.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:36.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:36.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:36.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:36.549: INFO: Number of nodes with available pods: 0 May 7 22:33:36.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:37.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:37.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:37.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:37.549: INFO: Number of nodes with available pods: 0 May 7 22:33:37.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:38.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:38.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:38.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:38.551: INFO: Number of nodes with available pods: 0 May 7 22:33:38.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:39.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:39.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:39.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:39.551: INFO: Number of nodes with available pods: 0 May 7 22:33:39.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:40.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:40.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:40.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:40.549: INFO: Number of nodes with available pods: 0 May 7 22:33:40.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:41.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:41.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:41.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:41.549: INFO: Number of nodes with available pods: 0 May 7 22:33:41.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:42.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:42.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:42.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:42.549: INFO: Number of nodes with available pods: 0 May 7 22:33:42.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:43.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:43.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:43.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:43.549: INFO: Number of nodes with available pods: 0 May 7 22:33:43.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:44.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:44.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:44.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:44.550: INFO: Number of nodes with available pods: 0 May 7 22:33:44.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:45.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:45.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:45.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:45.551: INFO: Number of nodes with available pods: 0 May 7 22:33:45.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:46.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:46.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:46.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:46.551: INFO: Number of nodes with available pods: 0 May 7 22:33:46.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:47.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:47.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:47.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:47.548: INFO: Number of nodes with available pods: 0 May 7 22:33:47.548: INFO: Node node1 is running more than one daemon pod May 7 22:33:48.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:48.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:48.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:48.551: INFO: Number of nodes with available pods: 0 May 7 22:33:48.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:49.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:49.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:49.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:49.550: INFO: Number of nodes with available pods: 0 May 7 22:33:49.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:50.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:50.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:50.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:50.550: INFO: Number of nodes with available pods: 0 May 7 22:33:50.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:51.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:51.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:51.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:51.551: INFO: Number of nodes with available pods: 0 May 7 22:33:51.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:52.551: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:52.552: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:52.552: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:52.554: INFO: Number of nodes with available pods: 0 May 7 22:33:52.554: INFO: Node node1 is running more than one daemon pod May 7 22:33:53.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:53.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:53.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:53.549: INFO: Number of nodes with available pods: 0 May 7 22:33:53.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:54.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:54.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:54.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:54.552: INFO: Number of nodes with available pods: 0 May 7 22:33:54.552: INFO: Node node1 is running more than one daemon pod May 7 22:33:55.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:55.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:55.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:55.551: INFO: Number of nodes with available pods: 0 May 7 22:33:55.551: INFO: Node node1 is running more than one daemon pod May 7 22:33:56.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:56.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:56.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:56.549: INFO: Number of nodes with available pods: 0 May 7 22:33:56.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:57.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:57.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:57.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:57.549: INFO: Number of nodes with available pods: 0 May 7 22:33:57.549: INFO: Node node1 is running more than one daemon pod May 7 22:33:58.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:58.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:58.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:58.550: INFO: Number of nodes with available pods: 0 May 7 22:33:58.550: INFO: Node node1 is running more than one daemon pod May 7 22:33:59.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:59.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:59.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:33:59.550: INFO: Number of nodes with available pods: 0 May 7 22:33:59.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:00.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:00.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:00.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:00.552: INFO: Number of nodes with available pods: 0 May 7 22:34:00.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:01.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:01.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:01.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:01.550: INFO: Number of nodes with available pods: 0 May 7 22:34:01.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:02.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:02.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:02.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:02.549: INFO: Number of nodes with available pods: 0 May 7 22:34:02.549: INFO: Node node1 is running more than one daemon pod May 7 22:34:03.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:03.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:03.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:03.552: INFO: Number of nodes with available pods: 0 May 7 22:34:03.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:04.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:04.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:04.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:04.552: INFO: Number of nodes with available pods: 0 May 7 22:34:04.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:05.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:05.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:05.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:05.550: INFO: Number of nodes with available pods: 0 May 7 22:34:05.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:06.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:06.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:06.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:06.550: INFO: Number of nodes with available pods: 0 May 7 22:34:06.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:07.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:07.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:07.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:07.549: INFO: Number of nodes with available pods: 0 May 7 22:34:07.549: INFO: Node node1 is running more than one daemon pod May 7 22:34:08.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:08.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:08.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:08.552: INFO: Number of nodes with available pods: 0 May 7 22:34:08.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:09.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:09.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:09.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:09.551: INFO: Number of nodes with available pods: 0 May 7 22:34:09.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:10.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:10.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:10.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:10.552: INFO: Number of nodes with available pods: 0 May 7 22:34:10.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:11.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:11.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:11.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:11.552: INFO: Number of nodes with available pods: 0 May 7 22:34:11.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:12.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:12.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:12.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:12.550: INFO: Number of nodes with available pods: 0 May 7 22:34:12.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:13.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:13.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:13.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:13.551: INFO: Number of nodes with available pods: 0 May 7 22:34:13.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:14.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:14.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:14.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:14.551: INFO: Number of nodes with available pods: 0 May 7 22:34:14.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:15.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:15.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:15.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:15.551: INFO: Number of nodes with available pods: 0 May 7 22:34:15.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:16.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:16.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:16.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:16.551: INFO: Number of nodes with available pods: 0 May 7 22:34:16.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:17.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:17.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:17.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:17.549: INFO: Number of nodes with available pods: 0 May 7 22:34:17.549: INFO: Node node1 is running more than one daemon pod May 7 22:34:18.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:18.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:18.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:18.551: INFO: Number of nodes with available pods: 0 May 7 22:34:18.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:19.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:19.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:19.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:19.551: INFO: Number of nodes with available pods: 0 May 7 22:34:19.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:20.550: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:20.550: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:20.550: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:20.553: INFO: Number of nodes with available pods: 0 May 7 22:34:20.553: INFO: Node node1 is running more than one daemon pod May 7 22:34:21.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:21.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:21.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:21.550: INFO: Number of nodes with available pods: 0 May 7 22:34:21.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:22.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:22.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:22.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:22.550: INFO: Number of nodes with available pods: 0 May 7 22:34:22.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:23.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:23.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:23.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:23.550: INFO: Number of nodes with available pods: 0 May 7 22:34:23.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:24.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:24.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:24.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:24.551: INFO: Number of nodes with available pods: 0 May 7 22:34:24.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:25.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:25.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:25.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:25.550: INFO: Number of nodes with available pods: 0 May 7 22:34:25.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:26.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:26.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:26.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:26.548: INFO: Number of nodes with available pods: 0 May 7 22:34:26.548: INFO: Node node1 is running more than one daemon pod May 7 22:34:27.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:27.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:27.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:27.550: INFO: Number of nodes with available pods: 0 May 7 22:34:27.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:28.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:28.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:28.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:28.550: INFO: Number of nodes with available pods: 0 May 7 22:34:28.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:29.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:29.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:29.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:29.549: INFO: Number of nodes with available pods: 0 May 7 22:34:29.549: INFO: Node node1 is running more than one daemon pod May 7 22:34:30.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:30.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:30.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:30.549: INFO: Number of nodes with available pods: 0 May 7 22:34:30.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:31.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:31.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:31.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:31.550: INFO: Number of nodes with available pods: 0 May 7 22:34:31.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:32.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:32.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:32.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:32.549: INFO: Number of nodes with available pods: 0 May 7 22:34:32.549: INFO: Node node1 is running more than one daemon pod May 7 22:34:33.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:33.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:33.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:33.552: INFO: Number of nodes with available pods: 0 May 7 22:34:33.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:34.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:34.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:34.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:34.551: INFO: Number of nodes with available pods: 0 May 7 22:34:34.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:35.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:35.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:35.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:35.552: INFO: Number of nodes with available pods: 0 May 7 22:34:35.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:36.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:36.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:36.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:36.550: INFO: Number of nodes with available pods: 0 May 7 22:34:36.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:37.545: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:37.545: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:37.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:37.548: INFO: Number of nodes with available pods: 0 May 7 22:34:37.548: INFO: Node node1 is running more than one daemon pod May 7 22:34:38.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:38.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:38.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:38.550: INFO: Number of nodes with available pods: 0 May 7 22:34:38.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:39.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:39.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:39.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:39.551: INFO: Number of nodes with available pods: 0 May 7 22:34:39.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:40.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:40.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:40.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:40.551: INFO: Number of nodes with available pods: 0 May 7 22:34:40.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:41.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:41.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:41.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:41.551: INFO: Number of nodes with available pods: 0 May 7 22:34:41.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:42.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:42.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:42.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:42.549: INFO: Number of nodes with available pods: 0 May 7 22:34:42.549: INFO: Node node1 is running more than one daemon pod May 7 22:34:43.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:43.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:43.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:43.551: INFO: Number of nodes with available pods: 0 May 7 22:34:43.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:44.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:44.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:44.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:44.551: INFO: Number of nodes with available pods: 0 May 7 22:34:44.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:45.545: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:45.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:45.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:45.548: INFO: Number of nodes with available pods: 0 May 7 22:34:45.548: INFO: Node node1 is running more than one daemon pod May 7 22:34:46.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:46.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:46.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:46.551: INFO: Number of nodes with available pods: 0 May 7 22:34:46.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:47.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:47.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:47.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:47.552: INFO: Number of nodes with available pods: 0 May 7 22:34:47.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:48.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:48.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:48.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:48.550: INFO: Number of nodes with available pods: 0 May 7 22:34:48.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:49.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:49.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:49.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:49.551: INFO: Number of nodes with available pods: 0 May 7 22:34:49.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:50.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:50.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:50.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:50.551: INFO: Number of nodes with available pods: 0 May 7 22:34:50.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:51.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:51.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:51.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:51.549: INFO: Number of nodes with available pods: 0 May 7 22:34:51.549: INFO: Node node1 is running more than one daemon pod May 7 22:34:52.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:52.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:52.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:52.550: INFO: Number of nodes with available pods: 0 May 7 22:34:52.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:53.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:53.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:53.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:53.549: INFO: Number of nodes with available pods: 0 May 7 22:34:53.549: INFO: Node node1 is running more than one daemon pod May 7 22:34:54.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:54.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:54.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:54.550: INFO: Number of nodes with available pods: 0 May 7 22:34:54.550: INFO: Node node1 is running more than one daemon pod May 7 22:34:55.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:55.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:55.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:55.552: INFO: Number of nodes with available pods: 0 May 7 22:34:55.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:56.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:56.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:56.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:56.551: INFO: Number of nodes with available pods: 0 May 7 22:34:56.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:57.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:57.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:57.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:57.551: INFO: Number of nodes with available pods: 0 May 7 22:34:57.551: INFO: Node node1 is running more than one daemon pod May 7 22:34:58.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:58.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:58.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:58.552: INFO: Number of nodes with available pods: 0 May 7 22:34:58.552: INFO: Node node1 is running more than one daemon pod May 7 22:34:59.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:59.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:59.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:34:59.550: INFO: Number of nodes with available pods: 0 May 7 22:34:59.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:00.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:00.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:00.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:00.552: INFO: Number of nodes with available pods: 0 May 7 22:35:00.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:01.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:01.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:01.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:01.550: INFO: Number of nodes with available pods: 0 May 7 22:35:01.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:02.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:02.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:02.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:02.551: INFO: Number of nodes with available pods: 0 May 7 22:35:02.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:03.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:03.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:03.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:03.550: INFO: Number of nodes with available pods: 0 May 7 22:35:03.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:04.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:04.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:04.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:04.550: INFO: Number of nodes with available pods: 0 May 7 22:35:04.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:05.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:05.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:05.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:05.550: INFO: Number of nodes with available pods: 0 May 7 22:35:05.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:06.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:06.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:06.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:06.551: INFO: Number of nodes with available pods: 0 May 7 22:35:06.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:07.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:07.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:07.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:07.549: INFO: Number of nodes with available pods: 0 May 7 22:35:07.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:08.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:08.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:08.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:08.550: INFO: Number of nodes with available pods: 0 May 7 22:35:08.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:09.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:09.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:09.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:09.548: INFO: Number of nodes with available pods: 0 May 7 22:35:09.548: INFO: Node node1 is running more than one daemon pod May 7 22:35:10.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:10.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:10.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:10.552: INFO: Number of nodes with available pods: 0 May 7 22:35:10.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:11.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:11.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:11.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:11.550: INFO: Number of nodes with available pods: 0 May 7 22:35:11.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:12.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:12.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:12.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:12.550: INFO: Number of nodes with available pods: 0 May 7 22:35:12.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:13.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:13.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:13.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:13.550: INFO: Number of nodes with available pods: 0 May 7 22:35:13.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:14.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:14.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:14.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:14.550: INFO: Number of nodes with available pods: 0 May 7 22:35:14.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:15.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:15.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:15.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:15.552: INFO: Number of nodes with available pods: 0 May 7 22:35:15.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:16.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:16.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:16.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:16.549: INFO: Number of nodes with available pods: 0 May 7 22:35:16.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:17.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:17.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:17.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:17.550: INFO: Number of nodes with available pods: 0 May 7 22:35:17.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:18.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:18.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:18.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:18.550: INFO: Number of nodes with available pods: 0 May 7 22:35:18.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:19.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:19.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:19.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:19.551: INFO: Number of nodes with available pods: 0 May 7 22:35:19.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:20.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:20.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:20.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:20.549: INFO: Number of nodes with available pods: 0 May 7 22:35:20.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:21.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:21.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:21.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:21.549: INFO: Number of nodes with available pods: 0 May 7 22:35:21.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:22.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:22.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:22.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:22.549: INFO: Number of nodes with available pods: 0 May 7 22:35:22.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:23.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:23.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:23.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:23.551: INFO: Number of nodes with available pods: 0 May 7 22:35:23.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:24.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:24.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:24.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:24.550: INFO: Number of nodes with available pods: 0 May 7 22:35:24.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:25.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:25.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:25.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:25.551: INFO: Number of nodes with available pods: 0 May 7 22:35:25.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:26.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:26.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:26.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:26.552: INFO: Number of nodes with available pods: 0 May 7 22:35:26.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:27.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:27.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:27.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:27.549: INFO: Number of nodes with available pods: 0 May 7 22:35:27.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:28.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:28.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:28.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:28.552: INFO: Number of nodes with available pods: 0 May 7 22:35:28.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:29.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:29.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:29.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:29.551: INFO: Number of nodes with available pods: 0 May 7 22:35:29.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:30.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:30.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:30.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:30.551: INFO: Number of nodes with available pods: 0 May 7 22:35:30.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:31.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:31.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:31.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:31.550: INFO: Number of nodes with available pods: 0 May 7 22:35:31.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:32.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:32.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:32.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:32.550: INFO: Number of nodes with available pods: 0 May 7 22:35:32.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:33.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:33.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:33.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:33.550: INFO: Number of nodes with available pods: 0 May 7 22:35:33.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:34.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:34.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:34.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:34.552: INFO: Number of nodes with available pods: 0 May 7 22:35:34.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:35.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:35.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:35.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:35.551: INFO: Number of nodes with available pods: 0 May 7 22:35:35.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:36.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:36.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:36.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:36.552: INFO: Number of nodes with available pods: 0 May 7 22:35:36.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:37.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:37.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:37.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:37.549: INFO: Number of nodes with available pods: 0 May 7 22:35:37.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:38.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:38.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:38.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:38.550: INFO: Number of nodes with available pods: 0 May 7 22:35:38.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:39.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:39.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:39.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:39.551: INFO: Number of nodes with available pods: 0 May 7 22:35:39.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:40.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:40.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:40.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:40.551: INFO: Number of nodes with available pods: 0 May 7 22:35:40.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:41.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:41.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:41.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:41.549: INFO: Number of nodes with available pods: 0 May 7 22:35:41.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:42.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:42.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:42.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:42.550: INFO: Number of nodes with available pods: 0 May 7 22:35:42.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:43.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:43.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:43.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:43.551: INFO: Number of nodes with available pods: 0 May 7 22:35:43.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:44.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:44.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:44.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:44.552: INFO: Number of nodes with available pods: 0 May 7 22:35:44.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:45.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:45.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:45.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:45.550: INFO: Number of nodes with available pods: 0 May 7 22:35:45.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:46.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:46.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:46.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:46.549: INFO: Number of nodes with available pods: 0 May 7 22:35:46.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:47.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:47.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:47.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:47.549: INFO: Number of nodes with available pods: 0 May 7 22:35:47.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:48.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:48.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:48.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:48.551: INFO: Number of nodes with available pods: 0 May 7 22:35:48.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:49.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:49.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:49.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:49.549: INFO: Number of nodes with available pods: 0 May 7 22:35:49.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:50.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:50.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:50.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:50.552: INFO: Number of nodes with available pods: 0 May 7 22:35:50.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:51.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:51.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:51.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:51.551: INFO: Number of nodes with available pods: 0 May 7 22:35:51.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:52.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:52.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:52.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:52.550: INFO: Number of nodes with available pods: 0 May 7 22:35:52.550: INFO: Node node1 is running more than one daemon pod May 7 22:35:53.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:53.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:53.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:53.551: INFO: Number of nodes with available pods: 0 May 7 22:35:53.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:54.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:54.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:54.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:54.549: INFO: Number of nodes with available pods: 0 May 7 22:35:54.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:55.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:55.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:55.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:55.549: INFO: Number of nodes with available pods: 0 May 7 22:35:55.549: INFO: Node node1 is running more than one daemon pod May 7 22:35:56.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:56.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:56.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:56.552: INFO: Number of nodes with available pods: 0 May 7 22:35:56.552: INFO: Node node1 is running more than one daemon pod May 7 22:35:57.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:57.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:57.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:57.548: INFO: Number of nodes with available pods: 0 May 7 22:35:57.548: INFO: Node node1 is running more than one daemon pod May 7 22:35:58.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:58.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:58.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:58.551: INFO: Number of nodes with available pods: 0 May 7 22:35:58.551: INFO: Node node1 is running more than one daemon pod May 7 22:35:59.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:59.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:59.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:35:59.549: INFO: Number of nodes with available pods: 0 May 7 22:35:59.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:00.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:00.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:00.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:00.552: INFO: Number of nodes with available pods: 0 May 7 22:36:00.552: INFO: Node node1 is running more than one daemon pod May 7 22:36:01.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:01.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:01.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:01.551: INFO: Number of nodes with available pods: 0 May 7 22:36:01.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:02.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:02.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:02.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:02.550: INFO: Number of nodes with available pods: 0 May 7 22:36:02.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:03.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:03.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:03.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:03.551: INFO: Number of nodes with available pods: 0 May 7 22:36:03.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:04.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:04.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:04.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:04.551: INFO: Number of nodes with available pods: 0 May 7 22:36:04.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:05.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:05.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:05.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:05.550: INFO: Number of nodes with available pods: 0 May 7 22:36:05.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:06.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:06.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:06.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:06.549: INFO: Number of nodes with available pods: 0 May 7 22:36:06.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:07.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:07.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:07.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:07.550: INFO: Number of nodes with available pods: 0 May 7 22:36:07.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:08.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:08.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:08.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:08.551: INFO: Number of nodes with available pods: 0 May 7 22:36:08.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:09.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:09.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:09.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:09.549: INFO: Number of nodes with available pods: 0 May 7 22:36:09.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:10.550: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:10.550: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:10.550: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:10.553: INFO: Number of nodes with available pods: 0 May 7 22:36:10.553: INFO: Node node1 is running more than one daemon pod May 7 22:36:11.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:11.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:11.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:11.550: INFO: Number of nodes with available pods: 0 May 7 22:36:11.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:12.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:12.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:12.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:12.549: INFO: Number of nodes with available pods: 0 May 7 22:36:12.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:13.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:13.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:13.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:13.551: INFO: Number of nodes with available pods: 0 May 7 22:36:13.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:14.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:14.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:14.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:14.550: INFO: Number of nodes with available pods: 0 May 7 22:36:14.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:15.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:15.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:15.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:15.550: INFO: Number of nodes with available pods: 0 May 7 22:36:15.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:16.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:16.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:16.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:16.550: INFO: Number of nodes with available pods: 0 May 7 22:36:16.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:17.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:17.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:17.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:17.549: INFO: Number of nodes with available pods: 0 May 7 22:36:17.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:18.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:18.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:18.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:18.549: INFO: Number of nodes with available pods: 0 May 7 22:36:18.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:19.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:19.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:19.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:19.552: INFO: Number of nodes with available pods: 0 May 7 22:36:19.552: INFO: Node node1 is running more than one daemon pod May 7 22:36:20.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:20.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:20.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:20.551: INFO: Number of nodes with available pods: 0 May 7 22:36:20.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:21.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:21.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:21.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:21.549: INFO: Number of nodes with available pods: 0 May 7 22:36:21.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:22.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:22.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:22.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:22.549: INFO: Number of nodes with available pods: 0 May 7 22:36:22.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:23.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:23.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:23.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:23.551: INFO: Number of nodes with available pods: 0 May 7 22:36:23.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:24.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:24.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:24.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:24.552: INFO: Number of nodes with available pods: 0 May 7 22:36:24.552: INFO: Node node1 is running more than one daemon pod May 7 22:36:25.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:25.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:25.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:25.549: INFO: Number of nodes with available pods: 0 May 7 22:36:25.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:26.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:26.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:26.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:26.549: INFO: Number of nodes with available pods: 0 May 7 22:36:26.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:27.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:27.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:27.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:27.549: INFO: Number of nodes with available pods: 0 May 7 22:36:27.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:28.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:28.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:28.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:28.553: INFO: Number of nodes with available pods: 0 May 7 22:36:28.553: INFO: Node node1 is running more than one daemon pod May 7 22:36:29.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:29.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:29.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:29.550: INFO: Number of nodes with available pods: 0 May 7 22:36:29.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:30.550: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:30.550: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:30.550: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:30.553: INFO: Number of nodes with available pods: 0 May 7 22:36:30.553: INFO: Node node1 is running more than one daemon pod May 7 22:36:31.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:31.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:31.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:31.552: INFO: Number of nodes with available pods: 0 May 7 22:36:31.552: INFO: Node node1 is running more than one daemon pod May 7 22:36:32.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:32.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:32.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:32.549: INFO: Number of nodes with available pods: 0 May 7 22:36:32.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:33.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:33.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:33.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:33.550: INFO: Number of nodes with available pods: 0 May 7 22:36:33.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:34.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:34.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:34.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:34.549: INFO: Number of nodes with available pods: 0 May 7 22:36:34.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:35.550: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:35.550: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:35.550: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:35.552: INFO: Number of nodes with available pods: 0 May 7 22:36:35.552: INFO: Node node1 is running more than one daemon pod May 7 22:36:36.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:36.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:36.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:36.549: INFO: Number of nodes with available pods: 0 May 7 22:36:36.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:37.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:37.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:37.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:37.549: INFO: Number of nodes with available pods: 0 May 7 22:36:37.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:38.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:38.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:38.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:38.551: INFO: Number of nodes with available pods: 0 May 7 22:36:38.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:39.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:39.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:39.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:39.550: INFO: Number of nodes with available pods: 0 May 7 22:36:39.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:40.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:40.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:40.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:40.551: INFO: Number of nodes with available pods: 0 May 7 22:36:40.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:41.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:41.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:41.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:41.549: INFO: Number of nodes with available pods: 0 May 7 22:36:41.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:42.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:42.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:42.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:42.550: INFO: Number of nodes with available pods: 0 May 7 22:36:42.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:43.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:43.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:43.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:43.551: INFO: Number of nodes with available pods: 0 May 7 22:36:43.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:44.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:44.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:44.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:44.550: INFO: Number of nodes with available pods: 0 May 7 22:36:44.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:45.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:45.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:45.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:45.550: INFO: Number of nodes with available pods: 0 May 7 22:36:45.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:46.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:46.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:46.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:46.552: INFO: Number of nodes with available pods: 0 May 7 22:36:46.552: INFO: Node node1 is running more than one daemon pod May 7 22:36:47.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:47.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:47.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:47.549: INFO: Number of nodes with available pods: 0 May 7 22:36:47.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:48.550: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:48.550: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:48.550: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:48.553: INFO: Number of nodes with available pods: 0 May 7 22:36:48.553: INFO: Node node1 is running more than one daemon pod May 7 22:36:49.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:49.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:49.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:49.550: INFO: Number of nodes with available pods: 0 May 7 22:36:49.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:50.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:50.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:50.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:50.551: INFO: Number of nodes with available pods: 0 May 7 22:36:50.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:51.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:51.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:51.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:51.550: INFO: Number of nodes with available pods: 0 May 7 22:36:51.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:52.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:52.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:52.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:52.549: INFO: Number of nodes with available pods: 0 May 7 22:36:52.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:53.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:53.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:53.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:53.549: INFO: Number of nodes with available pods: 0 May 7 22:36:53.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:54.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:54.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:54.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:54.550: INFO: Number of nodes with available pods: 0 May 7 22:36:54.550: INFO: Node node1 is running more than one daemon pod May 7 22:36:55.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:55.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:55.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:55.551: INFO: Number of nodes with available pods: 0 May 7 22:36:55.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:56.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:56.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:56.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:56.551: INFO: Number of nodes with available pods: 0 May 7 22:36:56.551: INFO: Node node1 is running more than one daemon pod May 7 22:36:57.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:57.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:57.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:57.549: INFO: Number of nodes with available pods: 0 May 7 22:36:57.549: INFO: Node node1 is running more than one daemon pod May 7 22:36:58.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:58.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:58.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:58.548: INFO: Number of nodes with available pods: 0 May 7 22:36:58.548: INFO: Node node1 is running more than one daemon pod May 7 22:36:59.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:59.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:59.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:36:59.551: INFO: Number of nodes with available pods: 0 May 7 22:36:59.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:00.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:00.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:00.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:00.550: INFO: Number of nodes with available pods: 0 May 7 22:37:00.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:01.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:01.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:01.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:01.549: INFO: Number of nodes with available pods: 0 May 7 22:37:01.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:02.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:02.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:02.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:02.549: INFO: Number of nodes with available pods: 0 May 7 22:37:02.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:03.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:03.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:03.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:03.551: INFO: Number of nodes with available pods: 0 May 7 22:37:03.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:04.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:04.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:04.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:04.550: INFO: Number of nodes with available pods: 0 May 7 22:37:04.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:05.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:05.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:05.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:05.549: INFO: Number of nodes with available pods: 0 May 7 22:37:05.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:06.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:06.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:06.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:06.550: INFO: Number of nodes with available pods: 0 May 7 22:37:06.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:07.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:07.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:07.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:07.548: INFO: Number of nodes with available pods: 0 May 7 22:37:07.548: INFO: Node node1 is running more than one daemon pod May 7 22:37:08.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:08.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:08.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:08.552: INFO: Number of nodes with available pods: 0 May 7 22:37:08.552: INFO: Node node1 is running more than one daemon pod May 7 22:37:09.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:09.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:09.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:09.549: INFO: Number of nodes with available pods: 0 May 7 22:37:09.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:10.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:10.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:10.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:10.550: INFO: Number of nodes with available pods: 0 May 7 22:37:10.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:11.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:11.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:11.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:11.548: INFO: Number of nodes with available pods: 0 May 7 22:37:11.548: INFO: Node node1 is running more than one daemon pod May 7 22:37:12.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:12.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:12.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:12.550: INFO: Number of nodes with available pods: 0 May 7 22:37:12.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:13.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:13.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:13.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:13.550: INFO: Number of nodes with available pods: 0 May 7 22:37:13.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:14.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:14.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:14.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:14.550: INFO: Number of nodes with available pods: 0 May 7 22:37:14.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:15.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:15.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:15.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:15.551: INFO: Number of nodes with available pods: 0 May 7 22:37:15.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:16.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:16.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:16.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:16.549: INFO: Number of nodes with available pods: 0 May 7 22:37:16.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:17.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:17.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:17.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:17.549: INFO: Number of nodes with available pods: 0 May 7 22:37:17.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:18.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:18.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:18.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:18.551: INFO: Number of nodes with available pods: 0 May 7 22:37:18.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:19.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:19.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:19.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:19.550: INFO: Number of nodes with available pods: 0 May 7 22:37:19.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:20.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:20.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:20.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:20.548: INFO: Number of nodes with available pods: 0 May 7 22:37:20.548: INFO: Node node1 is running more than one daemon pod May 7 22:37:21.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:21.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:21.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:21.548: INFO: Number of nodes with available pods: 0 May 7 22:37:21.548: INFO: Node node1 is running more than one daemon pod May 7 22:37:22.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:22.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:22.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:22.551: INFO: Number of nodes with available pods: 0 May 7 22:37:22.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:23.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:23.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:23.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:23.549: INFO: Number of nodes with available pods: 0 May 7 22:37:23.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:24.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:24.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:24.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:24.550: INFO: Number of nodes with available pods: 0 May 7 22:37:24.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:25.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:25.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:25.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:25.549: INFO: Number of nodes with available pods: 0 May 7 22:37:25.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:26.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:26.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:26.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:26.550: INFO: Number of nodes with available pods: 0 May 7 22:37:26.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:27.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:27.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:27.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:27.550: INFO: Number of nodes with available pods: 0 May 7 22:37:27.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:28.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:28.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:28.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:28.551: INFO: Number of nodes with available pods: 0 May 7 22:37:28.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:29.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:29.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:29.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:29.549: INFO: Number of nodes with available pods: 0 May 7 22:37:29.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:30.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:30.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:30.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:30.552: INFO: Number of nodes with available pods: 0 May 7 22:37:30.552: INFO: Node node1 is running more than one daemon pod May 7 22:37:31.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:31.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:31.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:31.551: INFO: Number of nodes with available pods: 0 May 7 22:37:31.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:32.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:32.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:32.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:32.549: INFO: Number of nodes with available pods: 0 May 7 22:37:32.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:33.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:33.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:33.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:33.551: INFO: Number of nodes with available pods: 0 May 7 22:37:33.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:34.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:34.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:34.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:34.551: INFO: Number of nodes with available pods: 0 May 7 22:37:34.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:35.550: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:35.550: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:35.550: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:35.553: INFO: Number of nodes with available pods: 0 May 7 22:37:35.553: INFO: Node node1 is running more than one daemon pod May 7 22:37:36.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:36.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:36.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:36.552: INFO: Number of nodes with available pods: 0 May 7 22:37:36.552: INFO: Node node1 is running more than one daemon pod May 7 22:37:37.545: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:37.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:37.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:37.548: INFO: Number of nodes with available pods: 0 May 7 22:37:37.548: INFO: Node node1 is running more than one daemon pod May 7 22:37:38.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:38.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:38.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:38.550: INFO: Number of nodes with available pods: 0 May 7 22:37:38.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:39.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:39.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:39.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:39.550: INFO: Number of nodes with available pods: 0 May 7 22:37:39.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:40.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:40.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:40.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:40.551: INFO: Number of nodes with available pods: 0 May 7 22:37:40.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:41.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:41.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:41.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:41.549: INFO: Number of nodes with available pods: 0 May 7 22:37:41.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:42.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:42.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:42.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:42.549: INFO: Number of nodes with available pods: 0 May 7 22:37:42.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:43.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:43.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:43.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:43.550: INFO: Number of nodes with available pods: 0 May 7 22:37:43.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:44.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:44.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:44.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:44.550: INFO: Number of nodes with available pods: 0 May 7 22:37:44.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:45.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:45.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:45.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:45.550: INFO: Number of nodes with available pods: 0 May 7 22:37:45.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:46.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:46.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:46.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:46.551: INFO: Number of nodes with available pods: 0 May 7 22:37:46.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:47.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:47.548: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:47.548: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:47.553: INFO: Number of nodes with available pods: 0 May 7 22:37:47.553: INFO: Node node1 is running more than one daemon pod May 7 22:37:48.546: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:48.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:48.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:48.549: INFO: Number of nodes with available pods: 0 May 7 22:37:48.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:49.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:49.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:49.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:49.550: INFO: Number of nodes with available pods: 0 May 7 22:37:49.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:50.548: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:50.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:50.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:50.551: INFO: Number of nodes with available pods: 0 May 7 22:37:50.551: INFO: Node node1 is running more than one daemon pod May 7 22:37:51.549: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:51.549: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:51.549: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:51.552: INFO: Number of nodes with available pods: 0 May 7 22:37:51.552: INFO: Node node1 is running more than one daemon pod May 7 22:37:52.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:52.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:52.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:52.549: INFO: Number of nodes with available pods: 0 May 7 22:37:52.549: INFO: Node node1 is running more than one daemon pod May 7 22:37:53.545: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:53.546: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:53.546: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:53.548: INFO: Number of nodes with available pods: 0 May 7 22:37:53.548: INFO: Node node1 is running more than one daemon pod May 7 22:37:54.547: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:54.547: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:54.547: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:54.550: INFO: Number of nodes with available pods: 0 May 7 22:37:54.550: INFO: Node node1 is running more than one daemon pod May 7 22:37:54.554: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:54.554: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:54.554: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:37:54.557: INFO: Number of nodes with available pods: 0 May 7 22:37:54.557: INFO: Node node1 is running more than one daemon pod May 7 22:37:54.558: FAIL: error waiting for daemon pod to start Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/apps.glob..func3.8() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:373 +0x4d5 k8s.io/kubernetes/test/e2e.RunE2ETests(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x345 k8s.io/kubernetes/test/e2e.TestE2E(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:145 +0x2b testing.tRunner(0xc00211a180, 0x4de37a0) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:100 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-6608, will wait for the garbage collector to delete the pods May 7 22:37:54.621: INFO: Deleting DaemonSet.extensions daemon-set took: 5.820555ms May 7 22:37:55.322: INFO: Terminating DaemonSet.extensions daemon-set pods took: 700.457749ms May 7 22:37:58.326: INFO: Number of nodes with available pods: 0 May 7 22:37:58.326: INFO: Number of running nodes: 0, number of available pods: 0 May 7 22:37:58.329: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"selfLink":"/apis/apps/v1/namespaces/daemonsets-6608/daemonsets","resourceVersion":"55485"},"items":null} May 7 22:37:58.332: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"selfLink":"/api/v1/namespaces/daemonsets-6608/pods","resourceVersion":"55485"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 STEP: Collecting events from namespace "daemonsets-6608". STEP: Found 18 events. May 7 22:37:58.345: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-gxgd6: { } Scheduled: Successfully assigned daemonsets-6608/daemon-set-gxgd6 to node2 May 7 22:37:58.345: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-zvt26: { } Scheduled: Successfully assigned daemonsets-6608/daemon-set-zvt26 to node1 May 7 22:37:58.345: INFO: At 2021-05-07 22:32:54 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-zvt26 May 7 22:37:58.345: INFO: At 2021-05-07 22:32:54 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-gxgd6 May 7 22:37:58.345: INFO: At 2021-05-07 22:32:55 +0000 UTC - event for daemon-set-gxgd6: {kubelet node2} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:37:58.345: INFO: At 2021-05-07 22:32:55 +0000 UTC - event for daemon-set-gxgd6: {multus } AddedInterface: Add eth0 [10.244.4.2/24] May 7 22:37:58.345: INFO: At 2021-05-07 22:32:55 +0000 UTC - event for daemon-set-zvt26: {kubelet node1} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:37:58.345: INFO: At 2021-05-07 22:32:55 +0000 UTC - event for daemon-set-zvt26: {multus } AddedInterface: Add eth0 [10.244.3.214/24] May 7 22:37:58.345: INFO: At 2021-05-07 22:32:56 +0000 UTC - event for daemon-set-gxgd6: {kubelet node2} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:37:58.345: INFO: At 2021-05-07 22:32:56 +0000 UTC - event for daemon-set-gxgd6: {kubelet node2} Failed: Error: ErrImagePull May 7 22:37:58.345: INFO: At 2021-05-07 22:32:56 +0000 UTC - event for daemon-set-zvt26: {kubelet node1} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:37:58.345: INFO: At 2021-05-07 22:32:56 +0000 UTC - event for daemon-set-zvt26: {kubelet node1} Failed: Error: ErrImagePull May 7 22:37:58.345: INFO: At 2021-05-07 22:32:56 +0000 UTC - event for daemon-set-zvt26: {kubelet node1} SandboxChanged: Pod sandbox changed, it will be killed and re-created. May 7 22:37:58.345: INFO: At 2021-05-07 22:32:57 +0000 UTC - event for daemon-set-gxgd6: {kubelet node2} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:37:58.345: INFO: At 2021-05-07 22:32:57 +0000 UTC - event for daemon-set-gxgd6: {kubelet node2} Failed: Error: ImagePullBackOff May 7 22:37:58.345: INFO: At 2021-05-07 22:32:58 +0000 UTC - event for daemon-set-zvt26: {multus } AddedInterface: Add eth0 [10.244.3.215/24] May 7 22:37:58.345: INFO: At 2021-05-07 22:32:58 +0000 UTC - event for daemon-set-zvt26: {kubelet node1} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:37:58.345: INFO: At 2021-05-07 22:32:58 +0000 UTC - event for daemon-set-zvt26: {kubelet node1} Failed: Error: ImagePullBackOff May 7 22:37:58.348: INFO: POD NODE PHASE GRACE CONDITIONS May 7 22:37:58.348: INFO: May 7 22:37:58.352: INFO: Logging node info for node master1 May 7 22:37:58.354: INFO: Node Info: &Node{ObjectMeta:{master1 /api/v1/nodes/master1 7277f528-99fb-4be3-a928-27761a4599e8 55453 0 2021-05-07 19:59:27 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master1 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"a2:74:f5:d6:48:e4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.202 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/master.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 19:59:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 19:59:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.0.0/24\"":{}},"f:taints":{}}}} {nfd-master Update v1 2021-05-07 20:08:42 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/master.version":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.0.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.0.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:15 +0000 UTC,LastTransitionTime:2021-05-07 20:05:15 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:51 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:51 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:51 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:37:51 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.202,},NodeAddress{Type:Hostname,Address:master1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:44253340a37b4ed7bf5b3a3547b5f57d,SystemUUID:00ACFB60-0631-E711-906E-0017A4403562,BootID:2a44f9c3-2714-4b5c-975d-25d069f66483,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:9d07c391aeb1a9d02eb4343c113ed01825227c70c32b3cae861711f90191b0fd quay.io/coreos/kube-rbac-proxy:v0.4.1],SizeBytes:41317870,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[quay.io/coreos/prometheus-operator@sha256:a54e806fb27d2fb0251da4f3b2a3bb5320759af63a54a755788304775f2384a7 quay.io/coreos/prometheus-operator:v0.40.0],SizeBytes:38238457,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[registry@sha256:1cd9409a311350c3072fe510b52046f104416376c126a479cef9a4dfe692cf57 registry:2.7.0],SizeBytes:24191168,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 tas-controller:latest localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[nginx@sha256:a97eb9ecc708c8aa715ccfb5e9338f5456e4b65575daf304f108301f3b497314 nginx:1.19.2-alpine],SizeBytes:22052669,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 tas-extender:latest localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[@ :],SizeBytes:5577654,},ContainerImage{Names:[alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a alpine:3.12.1],SizeBytes:5573013,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:37:58.355: INFO: Logging kubelet events for node master1 May 7 22:37:58.357: INFO: Logging pods the kubelet thinks is on node master1 May 7 22:37:58.372: INFO: kube-apiserver-master1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.372: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:37:58.372: INFO: kube-controller-manager-master1 started at 2021-05-07 20:04:26 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.372: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:37:58.372: INFO: kube-scheduler-master1 started at 2021-05-07 20:15:37 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.372: INFO: Container kube-scheduler ready: true, restart count 0 May 7 22:37:58.372: INFO: kube-flannel-nj6vr started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:37:58.372: INFO: Init container install-cni ready: true, restart count 0 May 7 22:37:58.372: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:37:58.372: INFO: coredns-7677f9bb54-wvd65 started at 2021-05-07 20:02:30 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.372: INFO: Container coredns ready: true, restart count 2 May 7 22:37:58.373: INFO: node-feature-discovery-controller-5bf5c49849-z2bj7 started at 2021-05-07 20:08:34 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.373: INFO: Container nfd-controller ready: true, restart count 0 May 7 22:37:58.373: INFO: node-exporter-9sm5v started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.373: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:37:58.373: INFO: Container node-exporter ready: true, restart count 0 May 7 22:37:58.373: INFO: kube-proxy-qpvcb started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.373: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:37:58.373: INFO: kube-multus-ds-amd64-8tjh4 started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.373: INFO: Container kube-multus ready: true, restart count 1 May 7 22:37:58.373: INFO: docker-registry-docker-registry-56cbc7bc58-267wq started at 2021-05-07 20:05:51 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.373: INFO: Container docker-registry ready: true, restart count 0 May 7 22:37:58.373: INFO: Container nginx ready: true, restart count 0 May 7 22:37:58.373: INFO: prometheus-operator-5bb8cb9d8f-xqpnw started at 2021-05-07 20:12:35 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.373: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:37:58.373: INFO: Container prometheus-operator ready: true, restart count 0 W0507 22:37:58.386378 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:37:58.417: INFO: Latency metrics for node master1 May 7 22:37:58.417: INFO: Logging node info for node master2 May 7 22:37:58.420: INFO: Node Info: &Node{ObjectMeta:{master2 /api/v1/nodes/master2 8193aa97-7914-4d63-b6cf-a7ceb8fe519c 55481 0 2021-05-07 20:00:06 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master2 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"86:88:6a:bc:18:32"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.203 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {kube-controller-manager Update v1 2021-05-07 20:01:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.1.0/24\"":{}},"f:taints":{}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}}]},Spec:NodeSpec{PodCIDR:10.244.1.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234767872 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324603904 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:58 +0000 UTC,LastTransitionTime:2021-05-07 20:04:58 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:57 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:57 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:57 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:37:57 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.203,},NodeAddress{Type:Hostname,Address:master2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:cf652b4fb7284de2aaafc5f52f51e312,SystemUUID:00A0DE53-E51D-E711-906E-0017A4403562,BootID:df4da196-5a1c-4b40-aef7-034e79f7a8e2,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:37:58.420: INFO: Logging kubelet events for node master2 May 7 22:37:58.423: INFO: Logging pods the kubelet thinks is on node master2 May 7 22:37:58.436: INFO: kube-proxy-fg5dt started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.436: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:37:58.436: INFO: kube-flannel-wwlww started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:37:58.436: INFO: Init container install-cni ready: true, restart count 0 May 7 22:37:58.436: INFO: Container kube-flannel ready: true, restart count 1 May 7 22:37:58.436: INFO: kube-multus-ds-amd64-44vrh started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.436: INFO: Container kube-multus ready: true, restart count 1 May 7 22:37:58.436: INFO: dns-autoscaler-5b7b5c9b6f-flqh2 started at 2021-05-07 20:02:33 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.436: INFO: Container autoscaler ready: true, restart count 2 May 7 22:37:58.436: INFO: node-exporter-6nqvj started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.436: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:37:58.436: INFO: Container node-exporter ready: true, restart count 0 May 7 22:37:58.436: INFO: kube-apiserver-master2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.436: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:37:58.436: INFO: kube-controller-manager-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.436: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:37:58.436: INFO: kube-scheduler-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.436: INFO: Container kube-scheduler ready: true, restart count 2 W0507 22:37:58.447603 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:37:58.469: INFO: Latency metrics for node master2 May 7 22:37:58.469: INFO: Logging node info for node master3 May 7 22:37:58.472: INFO: Node Info: &Node{ObjectMeta:{master3 /api/v1/nodes/master3 27e1bfdf-bb8c-4924-9488-acacef172e76 55486 0 2021-05-07 20:00:17 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master3 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"de:31:a8:23:73:1a"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.204 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:18 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.2.0/24\"":{}},"f:taints":{}}}}]},Spec:NodeSpec{PodCIDR:10.244.2.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.2.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:10 +0000 UTC,LastTransitionTime:2021-05-07 20:04:10 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:58 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:58 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:58 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:37:58 +0000 UTC,LastTransitionTime:2021-05-07 20:03:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.204,},NodeAddress{Type:Hostname,Address:master3,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:01ba71adbf0d4ef79a9af064c18faf21,SystemUUID:008B1444-141E-E711-906E-0017A4403562,BootID:1692e58d-c13c-425c-b11a-62d901f965ec,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:37:58.472: INFO: Logging kubelet events for node master3 May 7 22:37:58.474: INFO: Logging pods the kubelet thinks is on node master3 May 7 22:37:58.488: INFO: kube-multus-ds-amd64-hhqgw started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.488: INFO: Container kube-multus ready: true, restart count 1 May 7 22:37:58.488: INFO: coredns-7677f9bb54-pj7xl started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.488: INFO: Container coredns ready: true, restart count 2 May 7 22:37:58.488: INFO: node-exporter-tsk7w started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.488: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:37:58.488: INFO: Container node-exporter ready: true, restart count 0 May 7 22:37:58.488: INFO: kube-apiserver-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.488: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:37:58.488: INFO: kube-controller-manager-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.488: INFO: Container kube-controller-manager ready: true, restart count 3 May 7 22:37:58.488: INFO: kube-scheduler-master3 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.488: INFO: Container kube-scheduler ready: true, restart count 2 May 7 22:37:58.488: INFO: kube-proxy-lvj72 started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.488: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:37:58.488: INFO: kube-flannel-j2xn4 started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:37:58.488: INFO: Init container install-cni ready: true, restart count 1 May 7 22:37:58.488: INFO: Container kube-flannel ready: true, restart count 2 W0507 22:37:58.501469 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:37:58.530: INFO: Latency metrics for node master3 May 7 22:37:58.530: INFO: Logging node info for node node1 May 7 22:37:58.532: INFO: Node Info: &Node{ObjectMeta:{node1 /api/v1/nodes/node1 24d047f7-eb29-4f1d-96d0-63b225220bd5 55459 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node1 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"da:1d:6f:d2:a8:b4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.207 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.3.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:09 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {kubelet Update v1 2021-05-07 22:22:09 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:example.com/fakecpu":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {e2e.test Update v1 2021-05-07 22:22:48 +0000 UTC FieldsV1 {"f:status":{"f:capacity":{"f:example.com/fakecpu":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.3.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},example.com/fakecpu: {{1 3} {} 1k DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},example.com/fakecpu: {{1 3} {} 1k DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:03:55 +0000 UTC,LastTransitionTime:2021-05-07 20:03:55 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:53 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:53 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:53 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:37:53 +0000 UTC,LastTransitionTime:2021-05-07 20:03:44 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.207,},NodeAddress{Type:Hostname,Address:node1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:d79c3a817fbd4f03a173930e545bb174,SystemUUID:00CDA902-D022-E711-906E-0017A4403562,BootID:53771151-d654-4c88-80fe-48032d3317a5,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[@ :],SizeBytes:1002488002,},ContainerImage{Names:[opnfv/barometer-collectd@sha256:ed5c574f653e2a39e784ff322033a2319aafde7366c803a88f20f7a2a8bc1efb opnfv/barometer-collectd:stable],SizeBytes:825413035,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[golang@sha256:1636899c10870ab66c48d960a9df620f4f9e86a0c72fbacf36032d27404e7e6c golang:alpine3.12],SizeBytes:301156062,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[grafana/grafana@sha256:89304bc2335f4976618548d7b93d165ed67369d3a051d2f627fc4e0aa3d0aff1 grafana/grafana:7.1.0],SizeBytes:179601493,},ContainerImage{Names:[quay.io/prometheus/prometheus@sha256:d4ba4dd1a9ebb90916d0bfed3c204adcb118ed24546bf8dd2e6b30fc0fd2009e quay.io/prometheus/prometheus:v2.20.0],SizeBytes:144886595,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[directxman12/k8s-prometheus-adapter-amd64@sha256:b63dc612e3cb73f79d2401a4516f794f9f0a83002600ca72e675e41baecff437 directxman12/k8s-prometheus-adapter-amd64:v0.6.0],SizeBytes:53267842,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d nfvpe/sriov-device-plugin:latest localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[quay.io/coreos/prometheus-config-reloader@sha256:c679a143b24b7731ad1577a9865aa3805426cbf1b25e30807b951dff68466ffd quay.io/coreos/prometheus-config-reloader:v0.40.0],SizeBytes:10131705,},ContainerImage{Names:[jimmidyson/configmap-reload@sha256:d107c7a235c266273b1c3502a391fec374430e5625539403d0de797fa9c556a2 jimmidyson/configmap-reload:v0.3.0],SizeBytes:9700438,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[appropriate/curl@sha256:027a0ad3c69d085fea765afca9984787b780c172cead6502fec989198b98d8bb appropriate/curl:edge],SizeBytes:5654234,},ContainerImage{Names:[alpine@sha256:36553b10a4947067b9fbb7d532951066293a68eae893beba1d9235f7d11a20ad alpine:3.12],SizeBytes:5581415,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[gcr.io/authenticated-image-pulling/alpine@sha256:7ff177862cb50c602bfe81f805969412e619c054a2bbead977d0c276988aa4a0 gcr.io/authenticated-image-pulling/alpine:3.7],SizeBytes:4206620,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:37:58.533: INFO: Logging kubelet events for node node1 May 7 22:37:58.535: INFO: Logging pods the kubelet thinks is on node node1 May 7 22:37:58.554: INFO: kube-proxy-bms7z started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.554: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:37:58.554: INFO: cmk-init-discover-node1-krbjn started at 2021-05-07 20:11:05 +0000 UTC (0+3 container statuses recorded) May 7 22:37:58.554: INFO: Container discover ready: false, restart count 0 May 7 22:37:58.554: INFO: Container init ready: false, restart count 0 May 7 22:37:58.554: INFO: Container install ready: false, restart count 0 May 7 22:37:58.554: INFO: cmk-gjhf2 started at 2021-05-07 20:11:48 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.554: INFO: Container nodereport ready: true, restart count 0 May 7 22:37:58.554: INFO: Container reconcile ready: true, restart count 0 May 7 22:37:58.554: INFO: kube-multus-ds-amd64-fxgdb started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.554: INFO: Container kube-multus ready: true, restart count 1 May 7 22:37:58.554: INFO: prometheus-k8s-0 started at 2021-05-07 20:12:50 +0000 UTC (0+5 container statuses recorded) May 7 22:37:58.554: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:37:58.554: INFO: Container grafana ready: true, restart count 0 May 7 22:37:58.554: INFO: Container prometheus ready: true, restart count 1 May 7 22:37:58.554: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:37:58.554: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:37:58.554: INFO: kube-flannel-qm7lv started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:37:58.554: INFO: Init container install-cni ready: true, restart count 2 May 7 22:37:58.554: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:37:58.554: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.554: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:37:58.554: INFO: node-exporter-mpq58 started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.554: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:37:58.554: INFO: Container node-exporter ready: true, restart count 0 May 7 22:37:58.554: INFO: collectd-tmjfs started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:37:58.554: INFO: Container collectd ready: true, restart count 0 May 7 22:37:58.554: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:37:58.554: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:37:58.554: INFO: nginx-proxy-node1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.554: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:37:58.554: INFO: kubernetes-metrics-scraper-678c97765c-g7srv started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.554: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:37:58.554: INFO: node-feature-discovery-worker-xvbpd started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.554: INFO: Container nfd-worker ready: true, restart count 0 W0507 22:37:58.567374 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:37:58.612: INFO: Latency metrics for node node1 May 7 22:37:58.612: INFO: Logging node info for node node2 May 7 22:37:58.615: INFO: Node Info: &Node{ObjectMeta:{node2 /api/v1/nodes/node2 eae422ac-f6f0-4e9a-961d-e133dffc36be 55458 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node2 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"22:df:da:84:9b:00"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.208 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.4.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:31 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {kubelet Update v1 2021-05-07 20:11:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.4.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:02 +0000 UTC,LastTransitionTime:2021-05-07 20:05:02 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:52 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:52 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:37:52 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:37:52 +0000 UTC,LastTransitionTime:2021-05-07 20:02:07 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.208,},NodeAddress{Type:Hostname,Address:node2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:6f56c5a750d0441dba0ffa6273fb1a17,SystemUUID:80B3CD56-852F-E711-906E-0017A4403562,BootID:98b263e9-3136-45ed-9b07-5f5b6b9d69b8,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[k8s.gcr.io/etcd@sha256:4ad90a11b55313b182afc186b9876c8e891531b8db4c9bf1541953021618d0e2 k8s.gcr.io/etcd:3.4.13-0],SizeBytes:253392289,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/sample-apiserver@sha256:ff02aacd9766d597883fabafc7ad604c719a57611db1bcc1564c69a45b000a55 gcr.io/kubernetes-e2e-test-images/sample-apiserver:1.17],SizeBytes:60684726,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:37:58.615: INFO: Logging kubelet events for node node2 May 7 22:37:58.617: INFO: Logging pods the kubelet thinks is on node node2 May 7 22:37:58.634: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.634: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:37:58.634: INFO: cmk-init-discover-node2-kd9gg started at 2021-05-07 20:11:26 +0000 UTC (0+3 container statuses recorded) May 7 22:37:58.634: INFO: Container discover ready: false, restart count 0 May 7 22:37:58.634: INFO: Container init ready: false, restart count 0 May 7 22:37:58.634: INFO: Container install ready: false, restart count 0 May 7 22:37:58.634: INFO: cmk-gvh7j started at 2021-05-07 20:11:49 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.634: INFO: Container nodereport ready: true, restart count 0 May 7 22:37:58.634: INFO: Container reconcile ready: true, restart count 0 May 7 22:37:58.634: INFO: cmk-webhook-6c9d5f8578-94s58 started at 2021-05-07 20:11:49 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.634: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:37:58.634: INFO: collectd-p5gbt started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:37:58.634: INFO: Container collectd ready: true, restart count 0 May 7 22:37:58.634: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:37:58.634: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:37:58.634: INFO: nginx-proxy-node2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.634: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:37:58.634: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.634: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:37:58.634: INFO: kube-proxy-rgw7h started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.634: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:37:58.634: INFO: node-feature-discovery-worker-wp5n6 started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.634: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:37:58.634: INFO: node-exporter-4bcls started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.634: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:37:58.634: INFO: Container node-exporter ready: true, restart count 0 May 7 22:37:58.634: INFO: kube-flannel-htqkx started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:37:58.634: INFO: Init container install-cni ready: true, restart count 2 May 7 22:37:58.634: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:37:58.634: INFO: kube-multus-ds-amd64-g98hm started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:37:58.634: INFO: Container kube-multus ready: true, restart count 1 May 7 22:37:58.634: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f started at 2021-05-07 20:15:36 +0000 UTC (0+2 container statuses recorded) May 7 22:37:58.634: INFO: Container tas-controller ready: true, restart count 0 May 7 22:37:58.634: INFO: Container tas-extender ready: true, restart count 0 W0507 22:37:58.645288 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:37:58.682: INFO: Latency metrics for node node2 May 7 22:37:58.682: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-6608" for this suite. • Failure [304.192 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should update pod when spec was updated and update strategy is RollingUpdate [Conformance] [It] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:37:54.558: error waiting for daemon pod to start Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:373 ------------------------------ {"msg":"FAILED [sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","total":17,"completed":4,"skipped":2813,"failed":3,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:37:58.691: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:89 May 7 22:37:58.717: INFO: Waiting up to 1m0s for all nodes to be ready May 7 22:38:58.768: INFO: Waiting for terminating namespaces to be deleted... [It] validates lower priority pod preemption by critical pod [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Create pods that use 2/3 of node resources. May 7 22:38:58.794: INFO: Created pod: pod0-sched-preemption-low-priority May 7 22:38:58.813: INFO: Created pod: pod1-sched-preemption-medium-priority STEP: Wait for pods to be scheduled. STEP: Run a critical pod that use same resources as that of a lower priority pod [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:39:28.861: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-2146" for this suite. [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:77 • [SLOW TEST:90.209 seconds] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates lower priority pod preemption by critical pod [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod [Conformance]","total":17,"completed":5,"skipped":2841,"failed":3,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:39:28.908: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:134 [It] should rollback without unnecessary restarts [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:39:28.946: INFO: Create a RollingUpdate DaemonSet May 7 22:39:28.951: INFO: Check that daemon pods launch on every node of the cluster May 7 22:39:28.955: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:28.956: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:28.956: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:28.957: INFO: Number of nodes with available pods: 0 May 7 22:39:28.957: INFO: Node node1 is running more than one daemon pod May 7 22:39:29.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:29.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:29.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:29.966: INFO: Number of nodes with available pods: 0 May 7 22:39:29.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:30.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:30.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:30.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:30.967: INFO: Number of nodes with available pods: 0 May 7 22:39:30.967: INFO: Node node1 is running more than one daemon pod May 7 22:39:31.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:31.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:31.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:31.966: INFO: Number of nodes with available pods: 0 May 7 22:39:31.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:32.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:32.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:32.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:32.966: INFO: Number of nodes with available pods: 0 May 7 22:39:32.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:33.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:33.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:33.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:33.965: INFO: Number of nodes with available pods: 0 May 7 22:39:33.965: INFO: Node node1 is running more than one daemon pod May 7 22:39:34.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:34.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:34.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:34.967: INFO: Number of nodes with available pods: 0 May 7 22:39:34.967: INFO: Node node1 is running more than one daemon pod May 7 22:39:35.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:35.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:35.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:35.967: INFO: Number of nodes with available pods: 0 May 7 22:39:35.967: INFO: Node node1 is running more than one daemon pod May 7 22:39:36.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:36.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:36.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:36.966: INFO: Number of nodes with available pods: 0 May 7 22:39:36.967: INFO: Node node1 is running more than one daemon pod May 7 22:39:37.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:37.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:37.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:37.965: INFO: Number of nodes with available pods: 0 May 7 22:39:37.965: INFO: Node node1 is running more than one daemon pod May 7 22:39:38.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:38.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:38.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:38.965: INFO: Number of nodes with available pods: 0 May 7 22:39:38.965: INFO: Node node1 is running more than one daemon pod May 7 22:39:39.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:39.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:39.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:39.968: INFO: Number of nodes with available pods: 0 May 7 22:39:39.968: INFO: Node node1 is running more than one daemon pod May 7 22:39:40.966: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:40.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:40.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:40.969: INFO: Number of nodes with available pods: 0 May 7 22:39:40.969: INFO: Node node1 is running more than one daemon pod May 7 22:39:41.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:41.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:41.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:41.965: INFO: Number of nodes with available pods: 0 May 7 22:39:41.965: INFO: Node node1 is running more than one daemon pod May 7 22:39:42.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:42.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:42.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:42.966: INFO: Number of nodes with available pods: 0 May 7 22:39:42.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:43.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:43.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:43.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:43.966: INFO: Number of nodes with available pods: 0 May 7 22:39:43.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:44.966: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:44.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:44.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:44.970: INFO: Number of nodes with available pods: 0 May 7 22:39:44.970: INFO: Node node1 is running more than one daemon pod May 7 22:39:45.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:45.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:45.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:45.964: INFO: Number of nodes with available pods: 0 May 7 22:39:45.964: INFO: Node node1 is running more than one daemon pod May 7 22:39:46.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:46.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:46.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:46.965: INFO: Number of nodes with available pods: 0 May 7 22:39:46.965: INFO: Node node1 is running more than one daemon pod May 7 22:39:47.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:47.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:47.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:47.966: INFO: Number of nodes with available pods: 0 May 7 22:39:47.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:48.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:48.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:48.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:48.966: INFO: Number of nodes with available pods: 0 May 7 22:39:48.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:49.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:49.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:49.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:49.966: INFO: Number of nodes with available pods: 0 May 7 22:39:49.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:50.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:50.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:50.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:50.966: INFO: Number of nodes with available pods: 0 May 7 22:39:50.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:51.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:51.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:51.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:51.966: INFO: Number of nodes with available pods: 0 May 7 22:39:51.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:52.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:52.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:52.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:52.968: INFO: Number of nodes with available pods: 0 May 7 22:39:52.968: INFO: Node node1 is running more than one daemon pod May 7 22:39:53.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:53.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:53.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:53.965: INFO: Number of nodes with available pods: 0 May 7 22:39:53.965: INFO: Node node1 is running more than one daemon pod May 7 22:39:54.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:54.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:54.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:54.966: INFO: Number of nodes with available pods: 0 May 7 22:39:54.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:55.966: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:55.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:55.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:55.968: INFO: Number of nodes with available pods: 0 May 7 22:39:55.968: INFO: Node node1 is running more than one daemon pod May 7 22:39:56.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:56.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:56.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:56.966: INFO: Number of nodes with available pods: 0 May 7 22:39:56.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:57.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:57.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:57.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:57.969: INFO: Number of nodes with available pods: 0 May 7 22:39:57.970: INFO: Node node1 is running more than one daemon pod May 7 22:39:58.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:58.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:58.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:58.966: INFO: Number of nodes with available pods: 0 May 7 22:39:58.966: INFO: Node node1 is running more than one daemon pod May 7 22:39:59.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:59.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:59.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:39:59.966: INFO: Number of nodes with available pods: 0 May 7 22:39:59.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:00.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:00.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:00.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:00.968: INFO: Number of nodes with available pods: 0 May 7 22:40:00.968: INFO: Node node1 is running more than one daemon pod May 7 22:40:01.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:01.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:01.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:01.967: INFO: Number of nodes with available pods: 0 May 7 22:40:01.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:02.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:02.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:02.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:02.966: INFO: Number of nodes with available pods: 0 May 7 22:40:02.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:03.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:03.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:03.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:03.966: INFO: Number of nodes with available pods: 0 May 7 22:40:03.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:04.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:04.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:04.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:04.967: INFO: Number of nodes with available pods: 0 May 7 22:40:04.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:05.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:05.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:05.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:05.965: INFO: Number of nodes with available pods: 0 May 7 22:40:05.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:06.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:06.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:06.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:06.965: INFO: Number of nodes with available pods: 0 May 7 22:40:06.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:07.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:07.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:07.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:07.966: INFO: Number of nodes with available pods: 0 May 7 22:40:07.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:08.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:08.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:08.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:08.966: INFO: Number of nodes with available pods: 0 May 7 22:40:08.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:09.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:09.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:09.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:09.967: INFO: Number of nodes with available pods: 0 May 7 22:40:09.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:10.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:10.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:10.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:10.966: INFO: Number of nodes with available pods: 0 May 7 22:40:10.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:11.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:11.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:11.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:11.967: INFO: Number of nodes with available pods: 0 May 7 22:40:11.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:12.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:12.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:12.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:12.966: INFO: Number of nodes with available pods: 0 May 7 22:40:12.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:13.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:13.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:13.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:13.967: INFO: Number of nodes with available pods: 0 May 7 22:40:13.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:14.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:14.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:14.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:14.965: INFO: Number of nodes with available pods: 0 May 7 22:40:14.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:15.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:15.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:15.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:15.966: INFO: Number of nodes with available pods: 0 May 7 22:40:15.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:16.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:16.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:16.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:16.967: INFO: Number of nodes with available pods: 0 May 7 22:40:16.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:17.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:17.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:17.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:17.966: INFO: Number of nodes with available pods: 0 May 7 22:40:17.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:18.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:18.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:18.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:18.965: INFO: Number of nodes with available pods: 0 May 7 22:40:18.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:19.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:19.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:19.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:19.966: INFO: Number of nodes with available pods: 0 May 7 22:40:19.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:20.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:20.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:20.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:20.965: INFO: Number of nodes with available pods: 0 May 7 22:40:20.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:21.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:21.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:21.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:21.966: INFO: Number of nodes with available pods: 0 May 7 22:40:21.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:22.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:22.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:22.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:22.966: INFO: Number of nodes with available pods: 0 May 7 22:40:22.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:23.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:23.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:23.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:23.966: INFO: Number of nodes with available pods: 0 May 7 22:40:23.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:24.966: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:24.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:24.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:24.969: INFO: Number of nodes with available pods: 0 May 7 22:40:24.969: INFO: Node node1 is running more than one daemon pod May 7 22:40:25.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:25.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:25.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:25.965: INFO: Number of nodes with available pods: 0 May 7 22:40:25.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:26.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:26.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:26.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:26.966: INFO: Number of nodes with available pods: 0 May 7 22:40:26.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:27.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:27.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:27.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:27.966: INFO: Number of nodes with available pods: 0 May 7 22:40:27.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:28.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:28.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:28.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:28.966: INFO: Number of nodes with available pods: 0 May 7 22:40:28.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:29.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:29.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:29.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:29.966: INFO: Number of nodes with available pods: 0 May 7 22:40:29.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:30.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:30.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:30.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:30.965: INFO: Number of nodes with available pods: 0 May 7 22:40:30.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:31.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:31.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:31.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:31.965: INFO: Number of nodes with available pods: 0 May 7 22:40:31.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:32.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:32.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:32.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:32.968: INFO: Number of nodes with available pods: 0 May 7 22:40:32.968: INFO: Node node1 is running more than one daemon pod May 7 22:40:33.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:33.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:33.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:33.965: INFO: Number of nodes with available pods: 0 May 7 22:40:33.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:34.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:34.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:34.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:34.968: INFO: Number of nodes with available pods: 0 May 7 22:40:34.968: INFO: Node node1 is running more than one daemon pod May 7 22:40:35.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:35.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:35.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:35.966: INFO: Number of nodes with available pods: 0 May 7 22:40:35.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:36.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:36.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:36.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:36.965: INFO: Number of nodes with available pods: 0 May 7 22:40:36.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:37.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:37.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:37.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:37.966: INFO: Number of nodes with available pods: 0 May 7 22:40:37.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:38.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:38.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:38.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:38.967: INFO: Number of nodes with available pods: 0 May 7 22:40:38.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:39.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:39.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:39.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:39.968: INFO: Number of nodes with available pods: 0 May 7 22:40:39.968: INFO: Node node1 is running more than one daemon pod May 7 22:40:40.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:40.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:40.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:40.967: INFO: Number of nodes with available pods: 0 May 7 22:40:40.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:41.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:41.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:41.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:41.967: INFO: Number of nodes with available pods: 0 May 7 22:40:41.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:42.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:42.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:42.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:42.966: INFO: Number of nodes with available pods: 0 May 7 22:40:42.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:43.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:43.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:43.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:43.966: INFO: Number of nodes with available pods: 0 May 7 22:40:43.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:44.966: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:44.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:44.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:44.968: INFO: Number of nodes with available pods: 0 May 7 22:40:44.968: INFO: Node node1 is running more than one daemon pod May 7 22:40:45.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:45.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:45.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:45.967: INFO: Number of nodes with available pods: 0 May 7 22:40:45.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:46.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:46.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:46.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:46.968: INFO: Number of nodes with available pods: 0 May 7 22:40:46.968: INFO: Node node1 is running more than one daemon pod May 7 22:40:47.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:47.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:47.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:47.967: INFO: Number of nodes with available pods: 0 May 7 22:40:47.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:48.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:48.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:48.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:48.965: INFO: Number of nodes with available pods: 0 May 7 22:40:48.965: INFO: Node node1 is running more than one daemon pod May 7 22:40:49.967: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:49.967: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:49.967: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:49.969: INFO: Number of nodes with available pods: 0 May 7 22:40:49.969: INFO: Node node1 is running more than one daemon pod May 7 22:40:50.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:50.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:50.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:50.968: INFO: Number of nodes with available pods: 0 May 7 22:40:50.968: INFO: Node node1 is running more than one daemon pod May 7 22:40:51.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:51.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:51.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:51.966: INFO: Number of nodes with available pods: 0 May 7 22:40:51.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:52.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:52.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:52.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:52.966: INFO: Number of nodes with available pods: 0 May 7 22:40:52.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:53.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:53.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:53.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:53.966: INFO: Number of nodes with available pods: 0 May 7 22:40:53.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:54.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:54.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:54.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:54.968: INFO: Number of nodes with available pods: 0 May 7 22:40:54.968: INFO: Node node1 is running more than one daemon pod May 7 22:40:55.966: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:55.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:55.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:55.969: INFO: Number of nodes with available pods: 0 May 7 22:40:55.969: INFO: Node node1 is running more than one daemon pod May 7 22:40:56.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:56.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:56.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:56.966: INFO: Number of nodes with available pods: 0 May 7 22:40:56.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:57.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:57.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:57.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:57.966: INFO: Number of nodes with available pods: 0 May 7 22:40:57.966: INFO: Node node1 is running more than one daemon pod May 7 22:40:58.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:58.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:58.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:58.967: INFO: Number of nodes with available pods: 0 May 7 22:40:58.967: INFO: Node node1 is running more than one daemon pod May 7 22:40:59.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:59.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:59.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:40:59.968: INFO: Number of nodes with available pods: 0 May 7 22:40:59.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:00.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:00.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:00.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:00.968: INFO: Number of nodes with available pods: 0 May 7 22:41:00.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:01.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:01.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:01.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:01.966: INFO: Number of nodes with available pods: 0 May 7 22:41:01.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:02.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:02.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:02.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:02.967: INFO: Number of nodes with available pods: 0 May 7 22:41:02.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:03.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:03.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:03.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:03.964: INFO: Number of nodes with available pods: 0 May 7 22:41:03.964: INFO: Node node1 is running more than one daemon pod May 7 22:41:04.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:04.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:04.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:04.967: INFO: Number of nodes with available pods: 0 May 7 22:41:04.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:05.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:05.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:05.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:05.968: INFO: Number of nodes with available pods: 0 May 7 22:41:05.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:06.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:06.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:06.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:06.969: INFO: Number of nodes with available pods: 0 May 7 22:41:06.969: INFO: Node node1 is running more than one daemon pod May 7 22:41:07.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:07.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:07.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:07.968: INFO: Number of nodes with available pods: 0 May 7 22:41:07.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:08.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:08.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:08.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:08.965: INFO: Number of nodes with available pods: 0 May 7 22:41:08.965: INFO: Node node1 is running more than one daemon pod May 7 22:41:09.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:09.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:09.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:09.968: INFO: Number of nodes with available pods: 0 May 7 22:41:09.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:10.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:10.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:10.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:10.968: INFO: Number of nodes with available pods: 0 May 7 22:41:10.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:11.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:11.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:11.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:11.966: INFO: Number of nodes with available pods: 0 May 7 22:41:11.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:12.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:12.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:12.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:12.966: INFO: Number of nodes with available pods: 0 May 7 22:41:12.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:13.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:13.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:13.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:13.966: INFO: Number of nodes with available pods: 0 May 7 22:41:13.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:14.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:14.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:14.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:14.967: INFO: Number of nodes with available pods: 0 May 7 22:41:14.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:15.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:15.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:15.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:15.968: INFO: Number of nodes with available pods: 0 May 7 22:41:15.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:16.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:16.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:16.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:16.966: INFO: Number of nodes with available pods: 0 May 7 22:41:16.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:17.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:17.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:17.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:17.967: INFO: Number of nodes with available pods: 0 May 7 22:41:17.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:18.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:18.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:18.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:18.969: INFO: Number of nodes with available pods: 0 May 7 22:41:18.969: INFO: Node node1 is running more than one daemon pod May 7 22:41:19.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:19.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:19.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:19.966: INFO: Number of nodes with available pods: 0 May 7 22:41:19.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:20.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:20.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:20.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:20.965: INFO: Number of nodes with available pods: 0 May 7 22:41:20.965: INFO: Node node1 is running more than one daemon pod May 7 22:41:21.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:21.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:21.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:21.968: INFO: Number of nodes with available pods: 0 May 7 22:41:21.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:22.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:22.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:22.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:22.966: INFO: Number of nodes with available pods: 0 May 7 22:41:22.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:23.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:23.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:23.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:23.966: INFO: Number of nodes with available pods: 0 May 7 22:41:23.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:24.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:24.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:24.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:24.966: INFO: Number of nodes with available pods: 0 May 7 22:41:24.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:25.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:25.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:25.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:25.966: INFO: Number of nodes with available pods: 0 May 7 22:41:25.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:26.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:26.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:26.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:26.968: INFO: Number of nodes with available pods: 0 May 7 22:41:26.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:27.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:27.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:27.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:27.966: INFO: Number of nodes with available pods: 0 May 7 22:41:27.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:28.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:28.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:28.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:28.964: INFO: Number of nodes with available pods: 0 May 7 22:41:28.964: INFO: Node node1 is running more than one daemon pod May 7 22:41:29.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:29.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:29.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:29.966: INFO: Number of nodes with available pods: 0 May 7 22:41:29.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:30.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:30.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:30.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:30.969: INFO: Number of nodes with available pods: 0 May 7 22:41:30.969: INFO: Node node1 is running more than one daemon pod May 7 22:41:31.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:31.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:31.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:31.968: INFO: Number of nodes with available pods: 0 May 7 22:41:31.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:32.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:32.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:32.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:32.967: INFO: Number of nodes with available pods: 0 May 7 22:41:32.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:33.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:33.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:33.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:33.966: INFO: Number of nodes with available pods: 0 May 7 22:41:33.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:34.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:34.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:34.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:34.967: INFO: Number of nodes with available pods: 0 May 7 22:41:34.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:35.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:35.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:35.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:35.966: INFO: Number of nodes with available pods: 0 May 7 22:41:35.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:36.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:36.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:36.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:36.967: INFO: Number of nodes with available pods: 0 May 7 22:41:36.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:37.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:37.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:37.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:37.967: INFO: Number of nodes with available pods: 0 May 7 22:41:37.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:38.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:38.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:38.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:38.964: INFO: Number of nodes with available pods: 0 May 7 22:41:38.964: INFO: Node node1 is running more than one daemon pod May 7 22:41:39.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:39.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:39.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:39.968: INFO: Number of nodes with available pods: 0 May 7 22:41:39.968: INFO: Node node1 is running more than one daemon pod May 7 22:41:40.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:40.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:40.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:40.967: INFO: Number of nodes with available pods: 0 May 7 22:41:40.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:41.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:41.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:41.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:41.966: INFO: Number of nodes with available pods: 0 May 7 22:41:41.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:42.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:42.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:42.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:42.966: INFO: Number of nodes with available pods: 0 May 7 22:41:42.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:43.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:43.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:43.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:43.965: INFO: Number of nodes with available pods: 0 May 7 22:41:43.965: INFO: Node node1 is running more than one daemon pod May 7 22:41:44.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:44.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:44.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:44.967: INFO: Number of nodes with available pods: 0 May 7 22:41:44.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:45.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:45.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:45.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:45.966: INFO: Number of nodes with available pods: 0 May 7 22:41:45.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:46.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:46.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:46.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:46.967: INFO: Number of nodes with available pods: 0 May 7 22:41:46.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:47.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:47.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:47.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:47.966: INFO: Number of nodes with available pods: 0 May 7 22:41:47.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:48.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:48.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:48.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:48.965: INFO: Number of nodes with available pods: 0 May 7 22:41:48.965: INFO: Node node1 is running more than one daemon pod May 7 22:41:49.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:49.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:49.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:49.966: INFO: Number of nodes with available pods: 0 May 7 22:41:49.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:50.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:50.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:50.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:50.966: INFO: Number of nodes with available pods: 0 May 7 22:41:50.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:51.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:51.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:51.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:51.966: INFO: Number of nodes with available pods: 0 May 7 22:41:51.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:52.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:52.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:52.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:52.967: INFO: Number of nodes with available pods: 0 May 7 22:41:52.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:53.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:53.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:53.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:53.967: INFO: Number of nodes with available pods: 0 May 7 22:41:53.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:54.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:54.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:54.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:54.965: INFO: Number of nodes with available pods: 0 May 7 22:41:54.965: INFO: Node node1 is running more than one daemon pod May 7 22:41:55.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:55.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:55.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:55.965: INFO: Number of nodes with available pods: 0 May 7 22:41:55.965: INFO: Node node1 is running more than one daemon pod May 7 22:41:56.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:56.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:56.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:56.966: INFO: Number of nodes with available pods: 0 May 7 22:41:56.967: INFO: Node node1 is running more than one daemon pod May 7 22:41:57.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:57.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:57.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:57.966: INFO: Number of nodes with available pods: 0 May 7 22:41:57.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:58.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:58.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:58.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:58.966: INFO: Number of nodes with available pods: 0 May 7 22:41:58.966: INFO: Node node1 is running more than one daemon pod May 7 22:41:59.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:59.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:59.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:41:59.966: INFO: Number of nodes with available pods: 0 May 7 22:41:59.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:00.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:00.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:00.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:00.965: INFO: Number of nodes with available pods: 0 May 7 22:42:00.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:01.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:01.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:01.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:01.967: INFO: Number of nodes with available pods: 0 May 7 22:42:01.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:02.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:02.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:02.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:02.966: INFO: Number of nodes with available pods: 0 May 7 22:42:02.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:03.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:03.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:03.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:03.966: INFO: Number of nodes with available pods: 0 May 7 22:42:03.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:04.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:04.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:04.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:04.967: INFO: Number of nodes with available pods: 0 May 7 22:42:04.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:05.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:05.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:05.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:05.967: INFO: Number of nodes with available pods: 0 May 7 22:42:05.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:06.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:06.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:06.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:06.967: INFO: Number of nodes with available pods: 0 May 7 22:42:06.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:07.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:07.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:07.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:07.967: INFO: Number of nodes with available pods: 0 May 7 22:42:07.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:08.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:08.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:08.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:08.965: INFO: Number of nodes with available pods: 0 May 7 22:42:08.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:09.966: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:09.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:09.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:09.969: INFO: Number of nodes with available pods: 0 May 7 22:42:09.969: INFO: Node node1 is running more than one daemon pod May 7 22:42:10.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:10.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:10.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:10.968: INFO: Number of nodes with available pods: 0 May 7 22:42:10.968: INFO: Node node1 is running more than one daemon pod May 7 22:42:11.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:11.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:11.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:11.964: INFO: Number of nodes with available pods: 0 May 7 22:42:11.964: INFO: Node node1 is running more than one daemon pod May 7 22:42:12.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:12.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:12.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:12.966: INFO: Number of nodes with available pods: 0 May 7 22:42:12.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:13.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:13.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:13.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:13.965: INFO: Number of nodes with available pods: 0 May 7 22:42:13.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:14.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:14.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:14.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:14.966: INFO: Number of nodes with available pods: 0 May 7 22:42:14.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:15.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:15.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:15.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:15.967: INFO: Number of nodes with available pods: 0 May 7 22:42:15.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:16.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:16.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:16.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:16.968: INFO: Number of nodes with available pods: 0 May 7 22:42:16.968: INFO: Node node1 is running more than one daemon pod May 7 22:42:17.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:17.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:17.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:17.969: INFO: Number of nodes with available pods: 0 May 7 22:42:17.969: INFO: Node node1 is running more than one daemon pod May 7 22:42:18.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:18.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:18.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:18.965: INFO: Number of nodes with available pods: 0 May 7 22:42:18.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:19.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:19.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:19.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:19.966: INFO: Number of nodes with available pods: 0 May 7 22:42:19.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:20.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:20.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:20.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:20.968: INFO: Number of nodes with available pods: 0 May 7 22:42:20.968: INFO: Node node1 is running more than one daemon pod May 7 22:42:21.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:21.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:21.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:21.968: INFO: Number of nodes with available pods: 0 May 7 22:42:21.968: INFO: Node node1 is running more than one daemon pod May 7 22:42:22.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:22.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:22.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:22.966: INFO: Number of nodes with available pods: 0 May 7 22:42:22.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:23.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:23.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:23.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:23.966: INFO: Number of nodes with available pods: 0 May 7 22:42:23.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:24.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:24.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:24.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:24.966: INFO: Number of nodes with available pods: 0 May 7 22:42:24.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:25.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:25.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:25.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:25.966: INFO: Number of nodes with available pods: 0 May 7 22:42:25.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:26.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:26.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:26.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:26.967: INFO: Number of nodes with available pods: 0 May 7 22:42:26.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:27.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:27.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:27.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:27.966: INFO: Number of nodes with available pods: 0 May 7 22:42:27.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:28.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:28.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:28.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:28.967: INFO: Number of nodes with available pods: 0 May 7 22:42:28.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:29.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:29.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:29.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:29.967: INFO: Number of nodes with available pods: 0 May 7 22:42:29.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:30.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:30.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:30.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:30.967: INFO: Number of nodes with available pods: 0 May 7 22:42:30.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:31.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:31.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:31.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:31.968: INFO: Number of nodes with available pods: 0 May 7 22:42:31.968: INFO: Node node1 is running more than one daemon pod May 7 22:42:32.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:32.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:32.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:32.965: INFO: Number of nodes with available pods: 0 May 7 22:42:32.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:33.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:33.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:33.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:33.967: INFO: Number of nodes with available pods: 0 May 7 22:42:33.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:34.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:34.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:34.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:34.968: INFO: Number of nodes with available pods: 0 May 7 22:42:34.968: INFO: Node node1 is running more than one daemon pod May 7 22:42:35.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:35.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:35.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:35.966: INFO: Number of nodes with available pods: 0 May 7 22:42:35.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:36.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:36.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:36.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:36.967: INFO: Number of nodes with available pods: 0 May 7 22:42:36.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:37.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:37.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:37.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:37.967: INFO: Number of nodes with available pods: 0 May 7 22:42:37.967: INFO: Node node1 is running more than one daemon pod May 7 22:42:38.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:38.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:38.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:38.969: INFO: Number of nodes with available pods: 0 May 7 22:42:38.969: INFO: Node node1 is running more than one daemon pod May 7 22:42:39.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:39.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:39.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:39.966: INFO: Number of nodes with available pods: 0 May 7 22:42:39.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:40.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:40.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:40.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:40.968: INFO: Number of nodes with available pods: 0 May 7 22:42:40.968: INFO: Node node1 is running more than one daemon pod May 7 22:42:41.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:41.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:41.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:41.964: INFO: Number of nodes with available pods: 0 May 7 22:42:41.964: INFO: Node node1 is running more than one daemon pod May 7 22:42:42.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:42.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:42.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:42.965: INFO: Number of nodes with available pods: 0 May 7 22:42:42.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:43.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:43.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:43.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:43.966: INFO: Number of nodes with available pods: 0 May 7 22:42:43.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:44.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:44.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:44.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:44.966: INFO: Number of nodes with available pods: 0 May 7 22:42:44.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:45.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:45.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:45.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:45.965: INFO: Number of nodes with available pods: 0 May 7 22:42:45.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:46.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:46.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:46.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:46.966: INFO: Number of nodes with available pods: 0 May 7 22:42:46.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:47.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:47.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:47.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:47.966: INFO: Number of nodes with available pods: 0 May 7 22:42:47.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:48.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:48.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:48.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:48.965: INFO: Number of nodes with available pods: 0 May 7 22:42:48.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:49.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:49.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:49.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:49.965: INFO: Number of nodes with available pods: 0 May 7 22:42:49.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:50.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:50.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:50.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:50.967: INFO: Number of nodes with available pods: 0 May 7 22:42:50.968: INFO: Node node1 is running more than one daemon pod May 7 22:42:51.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:51.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:51.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:51.966: INFO: Number of nodes with available pods: 0 May 7 22:42:51.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:52.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:52.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:52.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:52.966: INFO: Number of nodes with available pods: 0 May 7 22:42:52.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:53.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:53.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:53.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:53.965: INFO: Number of nodes with available pods: 0 May 7 22:42:53.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:54.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:54.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:54.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:54.965: INFO: Number of nodes with available pods: 0 May 7 22:42:54.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:55.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:55.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:55.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:55.965: INFO: Number of nodes with available pods: 0 May 7 22:42:55.965: INFO: Node node1 is running more than one daemon pod May 7 22:42:56.961: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:56.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:56.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:56.964: INFO: Number of nodes with available pods: 0 May 7 22:42:56.964: INFO: Node node1 is running more than one daemon pod May 7 22:42:57.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:57.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:57.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:57.966: INFO: Number of nodes with available pods: 0 May 7 22:42:57.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:58.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:58.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:58.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:58.966: INFO: Number of nodes with available pods: 0 May 7 22:42:58.966: INFO: Node node1 is running more than one daemon pod May 7 22:42:59.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:59.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:59.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:42:59.965: INFO: Number of nodes with available pods: 0 May 7 22:42:59.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:00.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:00.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:00.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:00.966: INFO: Number of nodes with available pods: 0 May 7 22:43:00.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:01.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:01.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:01.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:01.965: INFO: Number of nodes with available pods: 0 May 7 22:43:01.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:02.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:02.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:02.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:02.965: INFO: Number of nodes with available pods: 0 May 7 22:43:02.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:03.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:03.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:03.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:03.965: INFO: Number of nodes with available pods: 0 May 7 22:43:03.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:04.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:04.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:04.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:04.965: INFO: Number of nodes with available pods: 0 May 7 22:43:04.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:05.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:05.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:05.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:05.966: INFO: Number of nodes with available pods: 0 May 7 22:43:05.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:06.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:06.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:06.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:06.965: INFO: Number of nodes with available pods: 0 May 7 22:43:06.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:07.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:07.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:07.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:07.965: INFO: Number of nodes with available pods: 0 May 7 22:43:07.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:08.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:08.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:08.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:08.967: INFO: Number of nodes with available pods: 0 May 7 22:43:08.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:09.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:09.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:09.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:09.967: INFO: Number of nodes with available pods: 0 May 7 22:43:09.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:10.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:10.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:10.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:10.967: INFO: Number of nodes with available pods: 0 May 7 22:43:10.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:11.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:11.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:11.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:11.968: INFO: Number of nodes with available pods: 0 May 7 22:43:11.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:12.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:12.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:12.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:12.966: INFO: Number of nodes with available pods: 0 May 7 22:43:12.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:13.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:13.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:13.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:13.966: INFO: Number of nodes with available pods: 0 May 7 22:43:13.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:14.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:14.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:14.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:14.969: INFO: Number of nodes with available pods: 0 May 7 22:43:14.969: INFO: Node node1 is running more than one daemon pod May 7 22:43:15.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:15.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:15.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:15.968: INFO: Number of nodes with available pods: 0 May 7 22:43:15.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:16.966: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:16.966: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:16.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:16.968: INFO: Number of nodes with available pods: 0 May 7 22:43:16.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:17.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:17.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:17.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:17.966: INFO: Number of nodes with available pods: 0 May 7 22:43:17.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:18.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:18.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:18.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:18.966: INFO: Number of nodes with available pods: 0 May 7 22:43:18.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:19.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:19.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:19.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:19.966: INFO: Number of nodes with available pods: 0 May 7 22:43:19.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:20.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:20.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:20.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:20.965: INFO: Number of nodes with available pods: 0 May 7 22:43:20.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:21.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:21.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:21.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:21.966: INFO: Number of nodes with available pods: 0 May 7 22:43:21.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:22.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:22.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:22.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:22.966: INFO: Number of nodes with available pods: 0 May 7 22:43:22.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:23.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:23.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:23.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:23.966: INFO: Number of nodes with available pods: 0 May 7 22:43:23.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:24.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:24.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:24.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:24.966: INFO: Number of nodes with available pods: 0 May 7 22:43:24.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:25.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:25.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:25.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:25.965: INFO: Number of nodes with available pods: 0 May 7 22:43:25.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:26.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:26.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:26.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:26.968: INFO: Number of nodes with available pods: 0 May 7 22:43:26.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:27.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:27.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:27.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:27.966: INFO: Number of nodes with available pods: 0 May 7 22:43:27.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:28.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:28.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:28.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:28.964: INFO: Number of nodes with available pods: 0 May 7 22:43:28.964: INFO: Node node1 is running more than one daemon pod May 7 22:43:29.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:29.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:29.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:29.967: INFO: Number of nodes with available pods: 0 May 7 22:43:29.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:30.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:30.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:30.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:30.966: INFO: Number of nodes with available pods: 0 May 7 22:43:30.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:31.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:31.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:31.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:31.967: INFO: Number of nodes with available pods: 0 May 7 22:43:31.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:32.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:32.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:32.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:32.966: INFO: Number of nodes with available pods: 0 May 7 22:43:32.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:33.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:33.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:33.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:33.966: INFO: Number of nodes with available pods: 0 May 7 22:43:33.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:34.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:34.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:34.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:34.968: INFO: Number of nodes with available pods: 0 May 7 22:43:34.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:35.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:35.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:35.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:35.968: INFO: Number of nodes with available pods: 0 May 7 22:43:35.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:36.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:36.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:36.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:36.967: INFO: Number of nodes with available pods: 0 May 7 22:43:36.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:37.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:37.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:37.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:37.967: INFO: Number of nodes with available pods: 0 May 7 22:43:37.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:38.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:38.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:38.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:38.966: INFO: Number of nodes with available pods: 0 May 7 22:43:38.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:39.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:39.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:39.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:39.966: INFO: Number of nodes with available pods: 0 May 7 22:43:39.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:40.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:40.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:40.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:40.968: INFO: Number of nodes with available pods: 0 May 7 22:43:40.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:41.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:41.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:41.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:41.968: INFO: Number of nodes with available pods: 0 May 7 22:43:41.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:42.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:42.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:42.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:42.965: INFO: Number of nodes with available pods: 0 May 7 22:43:42.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:43.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:43.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:43.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:43.967: INFO: Number of nodes with available pods: 0 May 7 22:43:43.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:44.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:44.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:44.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:44.968: INFO: Number of nodes with available pods: 0 May 7 22:43:44.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:45.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:45.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:45.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:45.967: INFO: Number of nodes with available pods: 0 May 7 22:43:45.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:46.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:46.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:46.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:46.966: INFO: Number of nodes with available pods: 0 May 7 22:43:46.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:47.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:47.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:47.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:47.966: INFO: Number of nodes with available pods: 0 May 7 22:43:47.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:48.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:48.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:48.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:48.965: INFO: Number of nodes with available pods: 0 May 7 22:43:48.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:49.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:49.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:49.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:49.966: INFO: Number of nodes with available pods: 0 May 7 22:43:49.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:50.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:50.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:50.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:50.965: INFO: Number of nodes with available pods: 0 May 7 22:43:50.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:51.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:51.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:51.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:51.968: INFO: Number of nodes with available pods: 0 May 7 22:43:51.968: INFO: Node node1 is running more than one daemon pod May 7 22:43:52.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:52.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:52.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:52.966: INFO: Number of nodes with available pods: 0 May 7 22:43:52.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:53.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:53.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:53.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:53.966: INFO: Number of nodes with available pods: 0 May 7 22:43:53.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:54.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:54.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:54.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:54.966: INFO: Number of nodes with available pods: 0 May 7 22:43:54.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:55.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:55.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:55.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:55.967: INFO: Number of nodes with available pods: 0 May 7 22:43:55.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:56.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:56.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:56.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:56.966: INFO: Number of nodes with available pods: 0 May 7 22:43:56.966: INFO: Node node1 is running more than one daemon pod May 7 22:43:57.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:57.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:57.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:57.967: INFO: Number of nodes with available pods: 0 May 7 22:43:57.967: INFO: Node node1 is running more than one daemon pod May 7 22:43:58.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:58.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:58.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:58.965: INFO: Number of nodes with available pods: 0 May 7 22:43:58.965: INFO: Node node1 is running more than one daemon pod May 7 22:43:59.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:59.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:59.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:43:59.967: INFO: Number of nodes with available pods: 0 May 7 22:43:59.967: INFO: Node node1 is running more than one daemon pod May 7 22:44:00.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:00.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:00.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:00.965: INFO: Number of nodes with available pods: 0 May 7 22:44:00.965: INFO: Node node1 is running more than one daemon pod May 7 22:44:01.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:01.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:01.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:01.965: INFO: Number of nodes with available pods: 0 May 7 22:44:01.965: INFO: Node node1 is running more than one daemon pod May 7 22:44:02.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:02.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:02.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:02.966: INFO: Number of nodes with available pods: 0 May 7 22:44:02.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:03.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:03.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:03.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:03.966: INFO: Number of nodes with available pods: 0 May 7 22:44:03.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:04.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:04.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:04.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:04.968: INFO: Number of nodes with available pods: 0 May 7 22:44:04.968: INFO: Node node1 is running more than one daemon pod May 7 22:44:05.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:05.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:05.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:05.966: INFO: Number of nodes with available pods: 0 May 7 22:44:05.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:06.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:06.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:06.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:06.966: INFO: Number of nodes with available pods: 0 May 7 22:44:06.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:07.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:07.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:07.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:07.967: INFO: Number of nodes with available pods: 0 May 7 22:44:07.967: INFO: Node node1 is running more than one daemon pod May 7 22:44:08.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:08.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:08.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:08.966: INFO: Number of nodes with available pods: 0 May 7 22:44:08.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:09.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:09.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:09.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:09.966: INFO: Number of nodes with available pods: 0 May 7 22:44:09.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:10.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:10.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:10.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:10.967: INFO: Number of nodes with available pods: 0 May 7 22:44:10.967: INFO: Node node1 is running more than one daemon pod May 7 22:44:11.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:11.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:11.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:11.965: INFO: Number of nodes with available pods: 0 May 7 22:44:11.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:12.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:12.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:12.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:12.966: INFO: Number of nodes with available pods: 0 May 7 22:44:12.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:13.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:13.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:13.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:13.966: INFO: Number of nodes with available pods: 0 May 7 22:44:13.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:14.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:14.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:14.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:14.966: INFO: Number of nodes with available pods: 0 May 7 22:44:14.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:15.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:15.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:15.966: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:15.968: INFO: Number of nodes with available pods: 0 May 7 22:44:15.968: INFO: Node node1 is running more than one daemon pod May 7 22:44:16.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:16.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:16.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:16.965: INFO: Number of nodes with available pods: 0 May 7 22:44:16.965: INFO: Node node1 is running more than one daemon pod May 7 22:44:17.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:17.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:17.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:17.966: INFO: Number of nodes with available pods: 0 May 7 22:44:17.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:18.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:18.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:18.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:18.965: INFO: Number of nodes with available pods: 0 May 7 22:44:18.965: INFO: Node node1 is running more than one daemon pod May 7 22:44:19.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:19.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:19.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:19.966: INFO: Number of nodes with available pods: 0 May 7 22:44:19.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:20.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:20.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:20.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:20.968: INFO: Number of nodes with available pods: 0 May 7 22:44:20.968: INFO: Node node1 is running more than one daemon pod May 7 22:44:21.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:21.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:21.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:21.966: INFO: Number of nodes with available pods: 0 May 7 22:44:21.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:22.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:22.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:22.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:22.966: INFO: Number of nodes with available pods: 0 May 7 22:44:22.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:23.964: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:23.964: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:23.964: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:23.967: INFO: Number of nodes with available pods: 0 May 7 22:44:23.967: INFO: Node node1 is running more than one daemon pod May 7 22:44:24.965: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:24.965: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:24.965: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:24.968: INFO: Number of nodes with available pods: 0 May 7 22:44:24.968: INFO: Node node1 is running more than one daemon pod May 7 22:44:25.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:25.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:25.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:25.966: INFO: Number of nodes with available pods: 0 May 7 22:44:25.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:26.963: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:26.963: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:26.963: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:26.966: INFO: Number of nodes with available pods: 0 May 7 22:44:26.966: INFO: Node node1 is running more than one daemon pod May 7 22:44:27.961: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:27.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:27.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:27.964: INFO: Number of nodes with available pods: 0 May 7 22:44:27.964: INFO: Node node1 is running more than one daemon pod May 7 22:44:28.962: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:28.962: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:28.962: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:28.965: INFO: Number of nodes with available pods: 0 May 7 22:44:28.965: INFO: Node node1 is running more than one daemon pod May 7 22:44:28.970: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:28.970: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:28.970: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:44:28.973: INFO: Number of nodes with available pods: 0 May 7 22:44:28.973: INFO: Node node1 is running more than one daemon pod May 7 22:44:28.973: FAIL: error waiting for daemon pod to start Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/apps.glob..func3.9() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:433 +0x6a7 k8s.io/kubernetes/test/e2e.RunE2ETests(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x345 k8s.io/kubernetes/test/e2e.TestE2E(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:145 +0x2b testing.tRunner(0xc00211a180, 0x4de37a0) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:100 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-5091, will wait for the garbage collector to delete the pods May 7 22:44:29.036: INFO: Deleting DaemonSet.extensions daemon-set took: 6.147752ms May 7 22:44:29.736: INFO: Terminating DaemonSet.extensions daemon-set pods took: 700.159526ms May 7 22:44:32.639: INFO: Number of nodes with available pods: 0 May 7 22:44:32.639: INFO: Number of running nodes: 0, number of available pods: 0 May 7 22:44:32.641: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"selfLink":"/apis/apps/v1/namespaces/daemonsets-5091/daemonsets","resourceVersion":"57091"},"items":null} May 7 22:44:32.644: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"selfLink":"/api/v1/namespaces/daemonsets-5091/pods","resourceVersion":"57091"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 STEP: Collecting events from namespace "daemonsets-5091". STEP: Found 18 events. May 7 22:44:32.657: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-65tzr: { } Scheduled: Successfully assigned daemonsets-5091/daemon-set-65tzr to node2 May 7 22:44:32.657: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-rg82g: { } Scheduled: Successfully assigned daemonsets-5091/daemon-set-rg82g to node1 May 7 22:44:32.657: INFO: At 2021-05-07 22:39:28 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-rg82g May 7 22:44:32.657: INFO: At 2021-05-07 22:39:28 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-65tzr May 7 22:44:32.657: INFO: At 2021-05-07 22:39:30 +0000 UTC - event for daemon-set-65tzr: {multus } AddedInterface: Add eth0 [10.244.4.8/24] May 7 22:44:32.657: INFO: At 2021-05-07 22:39:30 +0000 UTC - event for daemon-set-65tzr: {kubelet node2} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:44:32.657: INFO: At 2021-05-07 22:39:30 +0000 UTC - event for daemon-set-rg82g: {kubelet node1} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:44:32.657: INFO: At 2021-05-07 22:39:30 +0000 UTC - event for daemon-set-rg82g: {multus } AddedInterface: Add eth0 [10.244.3.218/24] May 7 22:44:32.657: INFO: At 2021-05-07 22:39:31 +0000 UTC - event for daemon-set-65tzr: {kubelet node2} Failed: Error: ErrImagePull May 7 22:44:32.657: INFO: At 2021-05-07 22:39:31 +0000 UTC - event for daemon-set-65tzr: {kubelet node2} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:44:32.657: INFO: At 2021-05-07 22:39:31 +0000 UTC - event for daemon-set-rg82g: {kubelet node1} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:44:32.657: INFO: At 2021-05-07 22:39:31 +0000 UTC - event for daemon-set-rg82g: {kubelet node1} Failed: Error: ErrImagePull May 7 22:44:32.657: INFO: At 2021-05-07 22:39:32 +0000 UTC - event for daemon-set-65tzr: {kubelet node2} SandboxChanged: Pod sandbox changed, it will be killed and re-created. May 7 22:44:32.657: INFO: At 2021-05-07 22:39:32 +0000 UTC - event for daemon-set-rg82g: {kubelet node1} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:44:32.657: INFO: At 2021-05-07 22:39:32 +0000 UTC - event for daemon-set-rg82g: {kubelet node1} Failed: Error: ImagePullBackOff May 7 22:44:32.657: INFO: At 2021-05-07 22:39:33 +0000 UTC - event for daemon-set-65tzr: {multus } AddedInterface: Add eth0 [10.244.4.9/24] May 7 22:44:32.657: INFO: At 2021-05-07 22:39:33 +0000 UTC - event for daemon-set-65tzr: {kubelet node2} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:44:32.657: INFO: At 2021-05-07 22:39:33 +0000 UTC - event for daemon-set-65tzr: {kubelet node2} Failed: Error: ImagePullBackOff May 7 22:44:32.659: INFO: POD NODE PHASE GRACE CONDITIONS May 7 22:44:32.659: INFO: May 7 22:44:32.663: INFO: Logging node info for node master1 May 7 22:44:32.665: INFO: Node Info: &Node{ObjectMeta:{master1 /api/v1/nodes/master1 7277f528-99fb-4be3-a928-27761a4599e8 57043 0 2021-05-07 19:59:27 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master1 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"a2:74:f5:d6:48:e4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.202 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/master.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 19:59:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 19:59:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.0.0/24\"":{}},"f:taints":{}}}} {nfd-master Update v1 2021-05-07 20:08:42 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/master.version":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.0.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.0.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:15 +0000 UTC,LastTransitionTime:2021-05-07 20:05:15 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:23 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:23 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:23 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:44:23 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.202,},NodeAddress{Type:Hostname,Address:master1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:44253340a37b4ed7bf5b3a3547b5f57d,SystemUUID:00ACFB60-0631-E711-906E-0017A4403562,BootID:2a44f9c3-2714-4b5c-975d-25d069f66483,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:9d07c391aeb1a9d02eb4343c113ed01825227c70c32b3cae861711f90191b0fd quay.io/coreos/kube-rbac-proxy:v0.4.1],SizeBytes:41317870,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[quay.io/coreos/prometheus-operator@sha256:a54e806fb27d2fb0251da4f3b2a3bb5320759af63a54a755788304775f2384a7 quay.io/coreos/prometheus-operator:v0.40.0],SizeBytes:38238457,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[registry@sha256:1cd9409a311350c3072fe510b52046f104416376c126a479cef9a4dfe692cf57 registry:2.7.0],SizeBytes:24191168,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 tas-controller:latest localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[nginx@sha256:a97eb9ecc708c8aa715ccfb5e9338f5456e4b65575daf304f108301f3b497314 nginx:1.19.2-alpine],SizeBytes:22052669,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 tas-extender:latest localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[@ :],SizeBytes:5577654,},ContainerImage{Names:[alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a alpine:3.12.1],SizeBytes:5573013,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:44:32.666: INFO: Logging kubelet events for node master1 May 7 22:44:32.668: INFO: Logging pods the kubelet thinks is on node master1 May 7 22:44:32.685: INFO: kube-proxy-qpvcb started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.685: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:44:32.685: INFO: kube-multus-ds-amd64-8tjh4 started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.685: INFO: Container kube-multus ready: true, restart count 1 May 7 22:44:32.685: INFO: docker-registry-docker-registry-56cbc7bc58-267wq started at 2021-05-07 20:05:51 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.685: INFO: Container docker-registry ready: true, restart count 0 May 7 22:44:32.685: INFO: Container nginx ready: true, restart count 0 May 7 22:44:32.685: INFO: prometheus-operator-5bb8cb9d8f-xqpnw started at 2021-05-07 20:12:35 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.685: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:32.685: INFO: Container prometheus-operator ready: true, restart count 0 May 7 22:44:32.685: INFO: coredns-7677f9bb54-wvd65 started at 2021-05-07 20:02:30 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.685: INFO: Container coredns ready: true, restart count 2 May 7 22:44:32.686: INFO: node-feature-discovery-controller-5bf5c49849-z2bj7 started at 2021-05-07 20:08:34 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.686: INFO: Container nfd-controller ready: true, restart count 0 May 7 22:44:32.686: INFO: node-exporter-9sm5v started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.686: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:32.686: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:32.686: INFO: kube-apiserver-master1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.686: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:44:32.686: INFO: kube-controller-manager-master1 started at 2021-05-07 20:04:26 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.686: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:44:32.686: INFO: kube-scheduler-master1 started at 2021-05-07 20:15:37 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.686: INFO: Container kube-scheduler ready: true, restart count 0 May 7 22:44:32.686: INFO: kube-flannel-nj6vr started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:44:32.686: INFO: Init container install-cni ready: true, restart count 0 May 7 22:44:32.686: INFO: Container kube-flannel ready: true, restart count 2 W0507 22:44:32.697385 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:44:32.724: INFO: Latency metrics for node master1 May 7 22:44:32.724: INFO: Logging node info for node master2 May 7 22:44:32.727: INFO: Node Info: &Node{ObjectMeta:{master2 /api/v1/nodes/master2 8193aa97-7914-4d63-b6cf-a7ceb8fe519c 57072 0 2021-05-07 20:00:06 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master2 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"86:88:6a:bc:18:32"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.203 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {kube-controller-manager Update v1 2021-05-07 20:01:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.1.0/24\"":{}},"f:taints":{}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}}]},Spec:NodeSpec{PodCIDR:10.244.1.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234767872 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324603904 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:58 +0000 UTC,LastTransitionTime:2021-05-07 20:04:58 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:29 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:29 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:29 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:44:29 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.203,},NodeAddress{Type:Hostname,Address:master2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:cf652b4fb7284de2aaafc5f52f51e312,SystemUUID:00A0DE53-E51D-E711-906E-0017A4403562,BootID:df4da196-5a1c-4b40-aef7-034e79f7a8e2,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:44:32.728: INFO: Logging kubelet events for node master2 May 7 22:44:32.729: INFO: Logging pods the kubelet thinks is on node master2 May 7 22:44:32.744: INFO: node-exporter-6nqvj started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.744: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:32.744: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:32.744: INFO: kube-apiserver-master2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.744: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:44:32.744: INFO: kube-controller-manager-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.744: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:44:32.744: INFO: kube-scheduler-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.744: INFO: Container kube-scheduler ready: true, restart count 2 May 7 22:44:32.744: INFO: kube-proxy-fg5dt started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.744: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:44:32.744: INFO: kube-flannel-wwlww started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:44:32.744: INFO: Init container install-cni ready: true, restart count 0 May 7 22:44:32.744: INFO: Container kube-flannel ready: true, restart count 1 May 7 22:44:32.744: INFO: kube-multus-ds-amd64-44vrh started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.744: INFO: Container kube-multus ready: true, restart count 1 May 7 22:44:32.744: INFO: dns-autoscaler-5b7b5c9b6f-flqh2 started at 2021-05-07 20:02:33 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.744: INFO: Container autoscaler ready: true, restart count 2 W0507 22:44:32.757049 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:44:32.781: INFO: Latency metrics for node master2 May 7 22:44:32.781: INFO: Logging node info for node master3 May 7 22:44:32.784: INFO: Node Info: &Node{ObjectMeta:{master3 /api/v1/nodes/master3 27e1bfdf-bb8c-4924-9488-acacef172e76 57080 0 2021-05-07 20:00:17 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master3 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"de:31:a8:23:73:1a"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.204 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:18 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.2.0/24\"":{}},"f:taints":{}}}}]},Spec:NodeSpec{PodCIDR:10.244.2.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.2.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:10 +0000 UTC,LastTransitionTime:2021-05-07 20:04:10 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:29 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:29 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:29 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:44:29 +0000 UTC,LastTransitionTime:2021-05-07 20:03:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.204,},NodeAddress{Type:Hostname,Address:master3,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:01ba71adbf0d4ef79a9af064c18faf21,SystemUUID:008B1444-141E-E711-906E-0017A4403562,BootID:1692e58d-c13c-425c-b11a-62d901f965ec,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:44:32.784: INFO: Logging kubelet events for node master3 May 7 22:44:32.787: INFO: Logging pods the kubelet thinks is on node master3 May 7 22:44:32.802: INFO: coredns-7677f9bb54-pj7xl started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.802: INFO: Container coredns ready: true, restart count 2 May 7 22:44:32.802: INFO: node-exporter-tsk7w started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.802: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:32.802: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:32.802: INFO: kube-apiserver-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.802: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:44:32.802: INFO: kube-controller-manager-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.802: INFO: Container kube-controller-manager ready: true, restart count 3 May 7 22:44:32.802: INFO: kube-scheduler-master3 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.802: INFO: Container kube-scheduler ready: true, restart count 2 May 7 22:44:32.802: INFO: kube-proxy-lvj72 started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.802: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:44:32.802: INFO: kube-flannel-j2xn4 started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:44:32.802: INFO: Init container install-cni ready: true, restart count 1 May 7 22:44:32.802: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:44:32.802: INFO: kube-multus-ds-amd64-hhqgw started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.802: INFO: Container kube-multus ready: true, restart count 1 W0507 22:44:32.815806 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:44:32.839: INFO: Latency metrics for node master3 May 7 22:44:32.839: INFO: Logging node info for node node1 May 7 22:44:32.841: INFO: Node Info: &Node{ObjectMeta:{node1 /api/v1/nodes/node1 24d047f7-eb29-4f1d-96d0-63b225220bd5 57057 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node1 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"da:1d:6f:d2:a8:b4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.207 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.3.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:09 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {e2e.test Update v1 2021-05-07 22:38:58 +0000 UTC FieldsV1 {"f:status":{"f:capacity":{"f:example.com/fakecpu":{},"f:scheduling.k8s.io/foo":{}}}}} {kubelet Update v1 2021-05-07 22:39:03 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:example.com/fakecpu":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{},"f:scheduling.k8s.io/foo":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.3.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},example.com/fakecpu: {{1 3} {} 1k DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},scheduling.k8s.io/foo: {{3 0} {} 3 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},example.com/fakecpu: {{1 3} {} 1k DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},scheduling.k8s.io/foo: {{3 0} {} 3 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:03:55 +0000 UTC,LastTransitionTime:2021-05-07 20:03:55 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:25 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:25 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:25 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:44:25 +0000 UTC,LastTransitionTime:2021-05-07 20:03:44 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.207,},NodeAddress{Type:Hostname,Address:node1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:d79c3a817fbd4f03a173930e545bb174,SystemUUID:00CDA902-D022-E711-906E-0017A4403562,BootID:53771151-d654-4c88-80fe-48032d3317a5,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[@ :],SizeBytes:1002488002,},ContainerImage{Names:[opnfv/barometer-collectd@sha256:ed5c574f653e2a39e784ff322033a2319aafde7366c803a88f20f7a2a8bc1efb opnfv/barometer-collectd:stable],SizeBytes:825413035,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[golang@sha256:1636899c10870ab66c48d960a9df620f4f9e86a0c72fbacf36032d27404e7e6c golang:alpine3.12],SizeBytes:301156062,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[grafana/grafana@sha256:89304bc2335f4976618548d7b93d165ed67369d3a051d2f627fc4e0aa3d0aff1 grafana/grafana:7.1.0],SizeBytes:179601493,},ContainerImage{Names:[quay.io/prometheus/prometheus@sha256:d4ba4dd1a9ebb90916d0bfed3c204adcb118ed24546bf8dd2e6b30fc0fd2009e quay.io/prometheus/prometheus:v2.20.0],SizeBytes:144886595,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[directxman12/k8s-prometheus-adapter-amd64@sha256:b63dc612e3cb73f79d2401a4516f794f9f0a83002600ca72e675e41baecff437 directxman12/k8s-prometheus-adapter-amd64:v0.6.0],SizeBytes:53267842,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d nfvpe/sriov-device-plugin:latest localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[quay.io/coreos/prometheus-config-reloader@sha256:c679a143b24b7731ad1577a9865aa3805426cbf1b25e30807b951dff68466ffd quay.io/coreos/prometheus-config-reloader:v0.40.0],SizeBytes:10131705,},ContainerImage{Names:[jimmidyson/configmap-reload@sha256:d107c7a235c266273b1c3502a391fec374430e5625539403d0de797fa9c556a2 jimmidyson/configmap-reload:v0.3.0],SizeBytes:9700438,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[appropriate/curl@sha256:027a0ad3c69d085fea765afca9984787b780c172cead6502fec989198b98d8bb appropriate/curl:edge],SizeBytes:5654234,},ContainerImage{Names:[alpine@sha256:36553b10a4947067b9fbb7d532951066293a68eae893beba1d9235f7d11a20ad alpine:3.12],SizeBytes:5581415,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[gcr.io/authenticated-image-pulling/alpine@sha256:7ff177862cb50c602bfe81f805969412e619c054a2bbead977d0c276988aa4a0 gcr.io/authenticated-image-pulling/alpine:3.7],SizeBytes:4206620,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:44:32.842: INFO: Logging kubelet events for node node1 May 7 22:44:32.845: INFO: Logging pods the kubelet thinks is on node node1 May 7 22:44:32.864: INFO: node-feature-discovery-worker-xvbpd started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.864: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:44:32.864: INFO: kube-proxy-bms7z started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.864: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:44:32.864: INFO: cmk-init-discover-node1-krbjn started at 2021-05-07 20:11:05 +0000 UTC (0+3 container statuses recorded) May 7 22:44:32.864: INFO: Container discover ready: false, restart count 0 May 7 22:44:32.864: INFO: Container init ready: false, restart count 0 May 7 22:44:32.864: INFO: Container install ready: false, restart count 0 May 7 22:44:32.864: INFO: cmk-gjhf2 started at 2021-05-07 20:11:48 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.864: INFO: Container nodereport ready: true, restart count 0 May 7 22:44:32.864: INFO: Container reconcile ready: true, restart count 0 May 7 22:44:32.864: INFO: kube-multus-ds-amd64-fxgdb started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.864: INFO: Container kube-multus ready: true, restart count 1 May 7 22:44:32.864: INFO: prometheus-k8s-0 started at 2021-05-07 20:12:50 +0000 UTC (0+5 container statuses recorded) May 7 22:44:32.864: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:44:32.864: INFO: Container grafana ready: true, restart count 0 May 7 22:44:32.864: INFO: Container prometheus ready: true, restart count 1 May 7 22:44:32.864: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:44:32.865: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:44:32.865: INFO: kube-flannel-qm7lv started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:44:32.865: INFO: Init container install-cni ready: true, restart count 2 May 7 22:44:32.865: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:44:32.865: INFO: node-exporter-mpq58 started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.865: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:32.865: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:32.865: INFO: collectd-tmjfs started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:44:32.865: INFO: Container collectd ready: true, restart count 0 May 7 22:44:32.865: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:44:32.865: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:44:32.865: INFO: nginx-proxy-node1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.865: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:44:32.865: INFO: kubernetes-metrics-scraper-678c97765c-g7srv started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.865: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:44:32.865: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.865: INFO: Container kube-sriovdp ready: true, restart count 0 W0507 22:44:32.875946 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:44:32.913: INFO: Latency metrics for node node1 May 7 22:44:32.913: INFO: Logging node info for node node2 May 7 22:44:32.917: INFO: Node Info: &Node{ObjectMeta:{node2 /api/v1/nodes/node2 eae422ac-f6f0-4e9a-961d-e133dffc36be 57052 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node2 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"22:df:da:84:9b:00"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.208 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.4.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:31 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {e2e.test Update v1 2021-05-07 22:38:58 +0000 UTC FieldsV1 {"f:status":{"f:capacity":{"f:scheduling.k8s.io/foo":{}}}}} {kubelet Update v1 2021-05-07 22:39:03 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{},"f:scheduling.k8s.io/foo":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.4.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},scheduling.k8s.io/foo: {{3 0} {} 3 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},scheduling.k8s.io/foo: {{3 0} {} 3 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:02 +0000 UTC,LastTransitionTime:2021-05-07 20:05:02 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:24 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:24 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:44:24 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:44:24 +0000 UTC,LastTransitionTime:2021-05-07 20:02:07 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.208,},NodeAddress{Type:Hostname,Address:node2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:6f56c5a750d0441dba0ffa6273fb1a17,SystemUUID:80B3CD56-852F-E711-906E-0017A4403562,BootID:98b263e9-3136-45ed-9b07-5f5b6b9d69b8,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[k8s.gcr.io/etcd@sha256:4ad90a11b55313b182afc186b9876c8e891531b8db4c9bf1541953021618d0e2 k8s.gcr.io/etcd:3.4.13-0],SizeBytes:253392289,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/sample-apiserver@sha256:ff02aacd9766d597883fabafc7ad604c719a57611db1bcc1564c69a45b000a55 gcr.io/kubernetes-e2e-test-images/sample-apiserver:1.17],SizeBytes:60684726,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:44:32.917: INFO: Logging kubelet events for node node2 May 7 22:44:32.919: INFO: Logging pods the kubelet thinks is on node node2 May 7 22:44:32.944: INFO: node-feature-discovery-worker-wp5n6 started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.944: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:44:32.944: INFO: node-exporter-4bcls started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.944: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:32.944: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:32.944: INFO: kube-flannel-htqkx started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:44:32.944: INFO: Init container install-cni ready: true, restart count 2 May 7 22:44:32.944: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:44:32.944: INFO: kube-multus-ds-amd64-g98hm started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.944: INFO: Container kube-multus ready: true, restart count 1 May 7 22:44:32.944: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f started at 2021-05-07 20:15:36 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.944: INFO: Container tas-controller ready: true, restart count 0 May 7 22:44:32.944: INFO: Container tas-extender ready: true, restart count 0 May 7 22:44:32.944: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.944: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:44:32.944: INFO: cmk-init-discover-node2-kd9gg started at 2021-05-07 20:11:26 +0000 UTC (0+3 container statuses recorded) May 7 22:44:32.944: INFO: Container discover ready: false, restart count 0 May 7 22:44:32.944: INFO: Container init ready: false, restart count 0 May 7 22:44:32.944: INFO: Container install ready: false, restart count 0 May 7 22:44:32.944: INFO: cmk-gvh7j started at 2021-05-07 20:11:49 +0000 UTC (0+2 container statuses recorded) May 7 22:44:32.944: INFO: Container nodereport ready: true, restart count 0 May 7 22:44:32.944: INFO: Container reconcile ready: true, restart count 0 May 7 22:44:32.944: INFO: cmk-webhook-6c9d5f8578-94s58 started at 2021-05-07 20:11:49 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.944: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:44:32.944: INFO: collectd-p5gbt started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:44:32.944: INFO: Container collectd ready: true, restart count 0 May 7 22:44:32.944: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:44:32.944: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:44:32.944: INFO: nginx-proxy-node2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.944: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:44:32.944: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.944: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:44:32.944: INFO: kube-proxy-rgw7h started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:44:32.944: INFO: Container kube-proxy ready: true, restart count 1 W0507 22:44:32.957188 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:44:32.989: INFO: Latency metrics for node node2 May 7 22:44:32.989: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-5091" for this suite. • Failure [304.089 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should rollback without unnecessary restarts [Conformance] [It] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:44:28.973: error waiting for daemon pod to start Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:433 ------------------------------ {"msg":"FAILED [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]","total":17,"completed":5,"skipped":3366,"failed":4,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:44:33.001: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 May 7 22:44:33.021: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready May 7 22:44:33.028: INFO: Waiting for terminating namespaces to be deleted... May 7 22:44:33.030: INFO: Logging pods the apiserver thinks is on node node1 before test May 7 22:44:33.042: INFO: cmk-gjhf2 from kube-system started at 2021-05-07 20:11:48 +0000 UTC (2 container statuses recorded) May 7 22:44:33.042: INFO: Container nodereport ready: true, restart count 0 May 7 22:44:33.042: INFO: Container reconcile ready: true, restart count 0 May 7 22:44:33.042: INFO: cmk-init-discover-node1-krbjn from kube-system started at 2021-05-07 20:11:05 +0000 UTC (3 container statuses recorded) May 7 22:44:33.042: INFO: Container discover ready: false, restart count 0 May 7 22:44:33.042: INFO: Container init ready: false, restart count 0 May 7 22:44:33.042: INFO: Container install ready: false, restart count 0 May 7 22:44:33.042: INFO: kube-flannel-qm7lv from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:44:33.042: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:44:33.042: INFO: kube-multus-ds-amd64-fxgdb from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:44:33.042: INFO: Container kube-multus ready: true, restart count 1 May 7 22:44:33.042: INFO: kube-proxy-bms7z from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:44:33.042: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:44:33.042: INFO: kubernetes-metrics-scraper-678c97765c-g7srv from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:44:33.042: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:44:33.042: INFO: nginx-proxy-node1 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:44:33.042: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:44:33.042: INFO: node-feature-discovery-worker-xvbpd from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:44:33.042: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:44:33.042: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:44:33.042: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:44:33.042: INFO: collectd-tmjfs from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:44:33.042: INFO: Container collectd ready: true, restart count 0 May 7 22:44:33.042: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:44:33.042: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:44:33.042: INFO: node-exporter-mpq58 from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:44:33.042: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:33.042: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:33.042: INFO: prometheus-k8s-0 from monitoring started at 2021-05-07 20:12:50 +0000 UTC (5 container statuses recorded) May 7 22:44:33.042: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:44:33.042: INFO: Container grafana ready: true, restart count 0 May 7 22:44:33.042: INFO: Container prometheus ready: true, restart count 1 May 7 22:44:33.042: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:44:33.042: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:44:33.042: INFO: Logging pods the apiserver thinks is on node node2 before test May 7 22:44:33.053: INFO: cmk-gvh7j from kube-system started at 2021-05-07 20:11:49 +0000 UTC (2 container statuses recorded) May 7 22:44:33.053: INFO: Container nodereport ready: true, restart count 0 May 7 22:44:33.053: INFO: Container reconcile ready: true, restart count 0 May 7 22:44:33.053: INFO: cmk-init-discover-node2-kd9gg from kube-system started at 2021-05-07 20:11:26 +0000 UTC (3 container statuses recorded) May 7 22:44:33.053: INFO: Container discover ready: false, restart count 0 May 7 22:44:33.053: INFO: Container init ready: false, restart count 0 May 7 22:44:33.053: INFO: Container install ready: false, restart count 0 May 7 22:44:33.053: INFO: cmk-webhook-6c9d5f8578-94s58 from kube-system started at 2021-05-07 20:11:49 +0000 UTC (1 container statuses recorded) May 7 22:44:33.053: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:44:33.053: INFO: kube-flannel-htqkx from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:44:33.053: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:44:33.053: INFO: kube-multus-ds-amd64-g98hm from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:44:33.053: INFO: Container kube-multus ready: true, restart count 1 May 7 22:44:33.053: INFO: kube-proxy-rgw7h from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:44:33.053: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:44:33.053: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:44:33.053: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:44:33.053: INFO: nginx-proxy-node2 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:44:33.053: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:44:33.053: INFO: node-feature-discovery-worker-wp5n6 from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:44:33.053: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:44:33.053: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:44:33.053: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:44:33.053: INFO: collectd-p5gbt from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:44:33.053: INFO: Container collectd ready: true, restart count 0 May 7 22:44:33.053: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:44:33.053: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:44:33.053: INFO: node-exporter-4bcls from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:44:33.053: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:33.053: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:33.053: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f from monitoring started at 2021-05-07 20:15:36 +0000 UTC (2 container statuses recorded) May 7 22:44:33.053: INFO: Container tas-controller ready: true, restart count 0 May 7 22:44:33.053: INFO: Container tas-extender ready: true, restart count 0 [It] validates that NodeSelector is respected if matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Trying to launch a pod without a label to get a node which can launch it. STEP: Explicitly delete pod here to free the resource it takes. STEP: Trying to apply a random label on the found node. STEP: verifying the node has the label kubernetes.io/e2e-9731328b-0ad2-4322-8d0d-aa0488c25935 42 STEP: Trying to relaunch the pod, now with labels. STEP: removing the label kubernetes.io/e2e-9731328b-0ad2-4322-8d0d-aa0488c25935 off the node node1 STEP: verifying the node doesn't have the label kubernetes.io/e2e-9731328b-0ad2-4322-8d0d-aa0488c25935 [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:44:41.131: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-5381" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 • [SLOW TEST:8.137 seconds] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates that NodeSelector is respected if matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance]","total":17,"completed":6,"skipped":3634,"failed":4,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:44:41.138: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 May 7 22:44:41.156: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready May 7 22:44:41.165: INFO: Waiting for terminating namespaces to be deleted... May 7 22:44:41.167: INFO: Logging pods the apiserver thinks is on node node1 before test May 7 22:44:41.177: INFO: cmk-gjhf2 from kube-system started at 2021-05-07 20:11:48 +0000 UTC (2 container statuses recorded) May 7 22:44:41.177: INFO: Container nodereport ready: true, restart count 0 May 7 22:44:41.177: INFO: Container reconcile ready: true, restart count 0 May 7 22:44:41.177: INFO: cmk-init-discover-node1-krbjn from kube-system started at 2021-05-07 20:11:05 +0000 UTC (3 container statuses recorded) May 7 22:44:41.177: INFO: Container discover ready: false, restart count 0 May 7 22:44:41.177: INFO: Container init ready: false, restart count 0 May 7 22:44:41.177: INFO: Container install ready: false, restart count 0 May 7 22:44:41.177: INFO: kube-flannel-qm7lv from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:44:41.177: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:44:41.177: INFO: kube-multus-ds-amd64-fxgdb from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:44:41.177: INFO: Container kube-multus ready: true, restart count 1 May 7 22:44:41.177: INFO: kube-proxy-bms7z from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:44:41.177: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:44:41.177: INFO: kubernetes-metrics-scraper-678c97765c-g7srv from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:44:41.177: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:44:41.177: INFO: nginx-proxy-node1 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:44:41.177: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:44:41.177: INFO: node-feature-discovery-worker-xvbpd from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:44:41.177: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:44:41.177: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:44:41.177: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:44:41.177: INFO: collectd-tmjfs from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:44:41.177: INFO: Container collectd ready: true, restart count 0 May 7 22:44:41.177: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:44:41.177: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:44:41.177: INFO: node-exporter-mpq58 from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:44:41.177: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:41.177: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:41.177: INFO: prometheus-k8s-0 from monitoring started at 2021-05-07 20:12:50 +0000 UTC (5 container statuses recorded) May 7 22:44:41.177: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:44:41.177: INFO: Container grafana ready: true, restart count 0 May 7 22:44:41.177: INFO: Container prometheus ready: true, restart count 1 May 7 22:44:41.177: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:44:41.177: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:44:41.177: INFO: with-labels from sched-pred-5381 started at 2021-05-07 22:44:37 +0000 UTC (1 container statuses recorded) May 7 22:44:41.177: INFO: Container with-labels ready: true, restart count 0 May 7 22:44:41.177: INFO: Logging pods the apiserver thinks is on node node2 before test May 7 22:44:41.194: INFO: cmk-gvh7j from kube-system started at 2021-05-07 20:11:49 +0000 UTC (2 container statuses recorded) May 7 22:44:41.194: INFO: Container nodereport ready: true, restart count 0 May 7 22:44:41.194: INFO: Container reconcile ready: true, restart count 0 May 7 22:44:41.194: INFO: cmk-init-discover-node2-kd9gg from kube-system started at 2021-05-07 20:11:26 +0000 UTC (3 container statuses recorded) May 7 22:44:41.194: INFO: Container discover ready: false, restart count 0 May 7 22:44:41.194: INFO: Container init ready: false, restart count 0 May 7 22:44:41.194: INFO: Container install ready: false, restart count 0 May 7 22:44:41.194: INFO: cmk-webhook-6c9d5f8578-94s58 from kube-system started at 2021-05-07 20:11:49 +0000 UTC (1 container statuses recorded) May 7 22:44:41.194: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:44:41.194: INFO: kube-flannel-htqkx from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:44:41.194: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:44:41.194: INFO: kube-multus-ds-amd64-g98hm from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:44:41.194: INFO: Container kube-multus ready: true, restart count 1 May 7 22:44:41.194: INFO: kube-proxy-rgw7h from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:44:41.194: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:44:41.194: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:44:41.194: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:44:41.194: INFO: nginx-proxy-node2 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:44:41.194: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:44:41.194: INFO: node-feature-discovery-worker-wp5n6 from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:44:41.194: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:44:41.194: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:44:41.194: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:44:41.194: INFO: collectd-p5gbt from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:44:41.194: INFO: Container collectd ready: true, restart count 0 May 7 22:44:41.194: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:44:41.194: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:44:41.194: INFO: node-exporter-4bcls from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:44:41.194: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:44:41.194: INFO: Container node-exporter ready: true, restart count 0 May 7 22:44:41.194: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f from monitoring started at 2021-05-07 20:15:36 +0000 UTC (2 container statuses recorded) May 7 22:44:41.194: INFO: Container tas-controller ready: true, restart count 0 May 7 22:44:41.194: INFO: Container tas-extender ready: true, restart count 0 [It] validates that NodeSelector is respected if not matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Trying to schedule Pod with nonempty NodeSelector. STEP: Considering event: Type = [Warning], Name = [restricted-pod.167cea3572c68a7f], Reason = [FailedScheduling], Message = [0/5 nodes are available: 5 node(s) didn't match node selector.] STEP: Considering event: Type = [Warning], Name = [restricted-pod.167cea35730bb7ac], Reason = [FailedScheduling], Message = [0/5 nodes are available: 5 node(s) didn't match node selector.] [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:44:42.231: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-9587" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 •{"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance]","total":17,"completed":7,"skipped":3669,"failed":4,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-storage] EmptyDir wrapper volumes should not cause race condition when used for configmaps [Serial] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-storage] EmptyDir wrapper volumes /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:44:42.240: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename emptydir-wrapper STEP: Waiting for a default service account to be provisioned in namespace [It] should not cause race condition when used for configmaps [Serial] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Creating 50 configmaps STEP: Creating RC which spawns configmap-volume pods May 7 22:44:42.547: INFO: Pod name wrapped-volume-race-ba2afb4f-4c7c-4c1f-b763-6329850585fc: Found 3 pods out of 5 May 7 22:44:47.552: INFO: Pod name wrapped-volume-race-ba2afb4f-4c7c-4c1f-b763-6329850585fc: Found 5 pods out of 5 STEP: Ensuring each pod is running STEP: deleting ReplicationController wrapped-volume-race-ba2afb4f-4c7c-4c1f-b763-6329850585fc in namespace emptydir-wrapper-265, will wait for the garbage collector to delete the pods May 7 22:45:03.634: INFO: Deleting ReplicationController wrapped-volume-race-ba2afb4f-4c7c-4c1f-b763-6329850585fc took: 5.56722ms May 7 22:45:04.334: INFO: Terminating ReplicationController wrapped-volume-race-ba2afb4f-4c7c-4c1f-b763-6329850585fc pods took: 700.23036ms STEP: Creating RC which spawns configmap-volume pods May 7 22:45:15.351: INFO: Pod name wrapped-volume-race-7c4b51f1-8145-41e6-84aa-c0d9c87fba0c: Found 0 pods out of 5 May 7 22:45:20.361: INFO: Pod name wrapped-volume-race-7c4b51f1-8145-41e6-84aa-c0d9c87fba0c: Found 5 pods out of 5 STEP: Ensuring each pod is running STEP: deleting ReplicationController wrapped-volume-race-7c4b51f1-8145-41e6-84aa-c0d9c87fba0c in namespace emptydir-wrapper-265, will wait for the garbage collector to delete the pods May 7 22:45:34.439: INFO: Deleting ReplicationController wrapped-volume-race-7c4b51f1-8145-41e6-84aa-c0d9c87fba0c took: 7.61945ms May 7 22:45:35.139: INFO: Terminating ReplicationController wrapped-volume-race-7c4b51f1-8145-41e6-84aa-c0d9c87fba0c pods took: 700.400085ms STEP: Creating RC which spawns configmap-volume pods May 7 22:45:45.356: INFO: Pod name wrapped-volume-race-ec117155-2061-4dd4-89f6-d451e7c2ab2d: Found 0 pods out of 5 May 7 22:45:50.362: INFO: Pod name wrapped-volume-race-ec117155-2061-4dd4-89f6-d451e7c2ab2d: Found 5 pods out of 5 STEP: Ensuring each pod is running STEP: deleting ReplicationController wrapped-volume-race-ec117155-2061-4dd4-89f6-d451e7c2ab2d in namespace emptydir-wrapper-265, will wait for the garbage collector to delete the pods May 7 22:46:04.445: INFO: Deleting ReplicationController wrapped-volume-race-ec117155-2061-4dd4-89f6-d451e7c2ab2d took: 7.876375ms May 7 22:46:05.145: INFO: Terminating ReplicationController wrapped-volume-race-ec117155-2061-4dd4-89f6-d451e7c2ab2d pods took: 700.306694ms STEP: Cleaning up the configMaps [AfterEach] [sig-storage] EmptyDir wrapper volumes /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:46:15.570: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "emptydir-wrapper-265" for this suite. • [SLOW TEST:93.338 seconds] [sig-storage] EmptyDir wrapper volumes /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23 should not cause race condition when used for configmaps [Serial] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-storage] EmptyDir wrapper volumes should not cause race condition when used for configmaps [Serial] [Conformance]","total":17,"completed":8,"skipped":3724,"failed":4,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:46:15.589: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 May 7 22:46:15.608: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready May 7 22:46:15.616: INFO: Waiting for terminating namespaces to be deleted... May 7 22:46:15.618: INFO: Logging pods the apiserver thinks is on node node1 before test May 7 22:46:15.633: INFO: cmk-gjhf2 from kube-system started at 2021-05-07 20:11:48 +0000 UTC (2 container statuses recorded) May 7 22:46:15.633: INFO: Container nodereport ready: true, restart count 0 May 7 22:46:15.633: INFO: Container reconcile ready: true, restart count 0 May 7 22:46:15.633: INFO: cmk-init-discover-node1-krbjn from kube-system started at 2021-05-07 20:11:05 +0000 UTC (3 container statuses recorded) May 7 22:46:15.633: INFO: Container discover ready: false, restart count 0 May 7 22:46:15.633: INFO: Container init ready: false, restart count 0 May 7 22:46:15.633: INFO: Container install ready: false, restart count 0 May 7 22:46:15.633: INFO: kube-flannel-qm7lv from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:46:15.633: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:46:15.633: INFO: kube-multus-ds-amd64-fxgdb from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:46:15.633: INFO: Container kube-multus ready: true, restart count 1 May 7 22:46:15.633: INFO: kube-proxy-bms7z from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:46:15.633: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:46:15.633: INFO: kubernetes-metrics-scraper-678c97765c-g7srv from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:46:15.633: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:46:15.633: INFO: nginx-proxy-node1 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:46:15.633: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:46:15.633: INFO: node-feature-discovery-worker-xvbpd from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:46:15.633: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:46:15.633: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:46:15.633: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:46:15.633: INFO: collectd-tmjfs from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:46:15.633: INFO: Container collectd ready: true, restart count 0 May 7 22:46:15.633: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:46:15.633: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:46:15.633: INFO: node-exporter-mpq58 from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:46:15.633: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:46:15.633: INFO: Container node-exporter ready: true, restart count 0 May 7 22:46:15.633: INFO: prometheus-k8s-0 from monitoring started at 2021-05-07 20:12:50 +0000 UTC (5 container statuses recorded) May 7 22:46:15.633: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:46:15.633: INFO: Container grafana ready: true, restart count 0 May 7 22:46:15.633: INFO: Container prometheus ready: true, restart count 1 May 7 22:46:15.633: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:46:15.633: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:46:15.633: INFO: Logging pods the apiserver thinks is on node node2 before test May 7 22:46:15.649: INFO: cmk-gvh7j from kube-system started at 2021-05-07 20:11:49 +0000 UTC (2 container statuses recorded) May 7 22:46:15.649: INFO: Container nodereport ready: true, restart count 0 May 7 22:46:15.649: INFO: Container reconcile ready: true, restart count 0 May 7 22:46:15.649: INFO: cmk-init-discover-node2-kd9gg from kube-system started at 2021-05-07 20:11:26 +0000 UTC (3 container statuses recorded) May 7 22:46:15.649: INFO: Container discover ready: false, restart count 0 May 7 22:46:15.649: INFO: Container init ready: false, restart count 0 May 7 22:46:15.649: INFO: Container install ready: false, restart count 0 May 7 22:46:15.649: INFO: cmk-webhook-6c9d5f8578-94s58 from kube-system started at 2021-05-07 20:11:49 +0000 UTC (1 container statuses recorded) May 7 22:46:15.649: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:46:15.649: INFO: kube-flannel-htqkx from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:46:15.649: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:46:15.649: INFO: kube-multus-ds-amd64-g98hm from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:46:15.649: INFO: Container kube-multus ready: true, restart count 1 May 7 22:46:15.649: INFO: kube-proxy-rgw7h from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:46:15.649: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:46:15.649: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:46:15.649: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:46:15.649: INFO: nginx-proxy-node2 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:46:15.649: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:46:15.649: INFO: node-feature-discovery-worker-wp5n6 from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:46:15.649: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:46:15.649: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:46:15.649: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:46:15.649: INFO: collectd-p5gbt from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:46:15.649: INFO: Container collectd ready: true, restart count 0 May 7 22:46:15.649: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:46:15.649: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:46:15.649: INFO: node-exporter-4bcls from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:46:15.649: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:46:15.649: INFO: Container node-exporter ready: true, restart count 0 May 7 22:46:15.649: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f from monitoring started at 2021-05-07 20:15:36 +0000 UTC (2 container statuses recorded) May 7 22:46:15.649: INFO: Container tas-controller ready: true, restart count 0 May 7 22:46:15.649: INFO: Container tas-extender ready: true, restart count 0 [It] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Trying to launch a pod without a label to get a node which can launch it. STEP: Explicitly delete pod here to free the resource it takes. STEP: Trying to apply a random label on the found node. STEP: verifying the node has the label kubernetes.io/e2e-842a3a59-779f-4cc3-ad2d-989cd4a3dc4a 90 STEP: Trying to create a pod(pod1) with hostport 54321 and hostIP 127.0.0.1 and expect scheduled STEP: Trying to create another pod(pod2) with hostport 54321 but hostIP 127.0.0.2 on the node which pod1 resides and expect scheduled STEP: Trying to create a third pod(pod3) with hostport 54321, hostIP 127.0.0.2 but use UDP protocol on the node which pod2 resides STEP: removing the label kubernetes.io/e2e-842a3a59-779f-4cc3-ad2d-989cd4a3dc4a off the node node2 STEP: verifying the node doesn't have the label kubernetes.io/e2e-842a3a59-779f-4cc3-ad2d-989cd4a3dc4a [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:46:31.750: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-8213" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 • [SLOW TEST:16.167 seconds] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates that there is no conflict between pods with same hostPort but different hostIP and protocol [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [Conformance]","total":17,"completed":9,"skipped":4540,"failed":4,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:46:31.760: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:89 May 7 22:46:31.787: INFO: Waiting up to 1m0s for all nodes to be ready May 7 22:47:31.838: INFO: Waiting for terminating namespaces to be deleted... [It] validates basic preemption works [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Create pods that use 2/3 of node resources. May 7 22:47:31.865: INFO: Created pod: pod0-sched-preemption-low-priority May 7 22:47:31.885: INFO: Created pod: pod1-sched-preemption-medium-priority STEP: Wait for pods to be scheduled. STEP: Run a high priority pod that has same requirements as that of lower priority pod [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:47:47.922: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-8280" for this suite. [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:77 • [SLOW TEST:76.205 seconds] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates basic preemption works [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works [Conformance]","total":17,"completed":10,"skipped":4803,"failed":4,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:47:47.969: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:134 [It] should retry creating failed daemon pods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Creating a simple DaemonSet "daemon-set" STEP: Check that daemon pods launch on every node of the cluster. May 7 22:47:48.016: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:48.016: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:48.016: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:48.018: INFO: Number of nodes with available pods: 0 May 7 22:47:48.018: INFO: Node node1 is running more than one daemon pod May 7 22:47:49.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:49.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:49.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:49.025: INFO: Number of nodes with available pods: 0 May 7 22:47:49.025: INFO: Node node1 is running more than one daemon pod May 7 22:47:50.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:50.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:50.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:50.025: INFO: Number of nodes with available pods: 0 May 7 22:47:50.026: INFO: Node node1 is running more than one daemon pod May 7 22:47:51.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:51.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:51.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:51.025: INFO: Number of nodes with available pods: 0 May 7 22:47:51.025: INFO: Node node1 is running more than one daemon pod May 7 22:47:52.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:52.027: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:52.027: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:52.030: INFO: Number of nodes with available pods: 0 May 7 22:47:52.030: INFO: Node node1 is running more than one daemon pod May 7 22:47:53.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:53.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:53.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:53.025: INFO: Number of nodes with available pods: 0 May 7 22:47:53.025: INFO: Node node1 is running more than one daemon pod May 7 22:47:54.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:54.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:54.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:54.026: INFO: Number of nodes with available pods: 0 May 7 22:47:54.026: INFO: Node node1 is running more than one daemon pod May 7 22:47:55.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:55.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:55.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:55.027: INFO: Number of nodes with available pods: 0 May 7 22:47:55.027: INFO: Node node1 is running more than one daemon pod May 7 22:47:56.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:56.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:56.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:56.026: INFO: Number of nodes with available pods: 0 May 7 22:47:56.027: INFO: Node node1 is running more than one daemon pod May 7 22:47:57.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:57.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:57.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:57.026: INFO: Number of nodes with available pods: 0 May 7 22:47:57.026: INFO: Node node1 is running more than one daemon pod May 7 22:47:58.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:58.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:58.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:58.027: INFO: Number of nodes with available pods: 0 May 7 22:47:58.027: INFO: Node node1 is running more than one daemon pod May 7 22:47:59.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:59.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:59.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:47:59.026: INFO: Number of nodes with available pods: 0 May 7 22:47:59.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:00.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:00.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:00.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:00.028: INFO: Number of nodes with available pods: 0 May 7 22:48:00.028: INFO: Node node1 is running more than one daemon pod May 7 22:48:01.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:01.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:01.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:01.029: INFO: Number of nodes with available pods: 0 May 7 22:48:01.029: INFO: Node node1 is running more than one daemon pod May 7 22:48:02.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:02.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:02.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:02.029: INFO: Number of nodes with available pods: 0 May 7 22:48:02.029: INFO: Node node1 is running more than one daemon pod May 7 22:48:03.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:03.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:03.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:03.026: INFO: Number of nodes with available pods: 0 May 7 22:48:03.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:04.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:04.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:04.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:04.026: INFO: Number of nodes with available pods: 0 May 7 22:48:04.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:05.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:05.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:05.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:05.027: INFO: Number of nodes with available pods: 0 May 7 22:48:05.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:06.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:06.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:06.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:06.026: INFO: Number of nodes with available pods: 0 May 7 22:48:06.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:07.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:07.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:07.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:07.029: INFO: Number of nodes with available pods: 0 May 7 22:48:07.029: INFO: Node node1 is running more than one daemon pod May 7 22:48:08.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:08.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:08.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:08.026: INFO: Number of nodes with available pods: 0 May 7 22:48:08.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:09.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:09.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:09.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:09.025: INFO: Number of nodes with available pods: 0 May 7 22:48:09.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:10.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:10.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:10.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:10.027: INFO: Number of nodes with available pods: 0 May 7 22:48:10.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:11.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:11.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:11.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:11.027: INFO: Number of nodes with available pods: 0 May 7 22:48:11.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:12.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:12.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:12.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:12.027: INFO: Number of nodes with available pods: 0 May 7 22:48:12.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:13.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:13.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:13.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:13.025: INFO: Number of nodes with available pods: 0 May 7 22:48:13.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:14.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:14.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:14.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:14.026: INFO: Number of nodes with available pods: 0 May 7 22:48:14.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:15.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:15.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:15.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:15.024: INFO: Number of nodes with available pods: 0 May 7 22:48:15.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:16.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:16.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:16.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:16.026: INFO: Number of nodes with available pods: 0 May 7 22:48:16.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:17.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:17.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:17.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:17.028: INFO: Number of nodes with available pods: 0 May 7 22:48:17.028: INFO: Node node1 is running more than one daemon pod May 7 22:48:18.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:18.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:18.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:18.027: INFO: Number of nodes with available pods: 0 May 7 22:48:18.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:19.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:19.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:19.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:19.025: INFO: Number of nodes with available pods: 0 May 7 22:48:19.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:20.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:20.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:20.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:20.029: INFO: Number of nodes with available pods: 0 May 7 22:48:20.029: INFO: Node node1 is running more than one daemon pod May 7 22:48:21.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:21.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:21.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:21.027: INFO: Number of nodes with available pods: 0 May 7 22:48:21.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:22.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:22.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:22.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:22.026: INFO: Number of nodes with available pods: 0 May 7 22:48:22.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:23.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:23.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:23.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:23.027: INFO: Number of nodes with available pods: 0 May 7 22:48:23.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:24.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:24.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:24.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:24.025: INFO: Number of nodes with available pods: 0 May 7 22:48:24.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:25.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:25.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:25.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:25.026: INFO: Number of nodes with available pods: 0 May 7 22:48:25.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:26.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:26.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:26.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:26.026: INFO: Number of nodes with available pods: 0 May 7 22:48:26.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:27.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:27.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:27.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:27.028: INFO: Number of nodes with available pods: 0 May 7 22:48:27.028: INFO: Node node1 is running more than one daemon pod May 7 22:48:28.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:28.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:28.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:28.027: INFO: Number of nodes with available pods: 0 May 7 22:48:28.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:29.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:29.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:29.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:29.025: INFO: Number of nodes with available pods: 0 May 7 22:48:29.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:30.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:30.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:30.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:30.026: INFO: Number of nodes with available pods: 0 May 7 22:48:30.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:31.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:31.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:31.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:31.028: INFO: Number of nodes with available pods: 0 May 7 22:48:31.028: INFO: Node node1 is running more than one daemon pod May 7 22:48:32.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:32.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:32.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:32.027: INFO: Number of nodes with available pods: 0 May 7 22:48:32.028: INFO: Node node1 is running more than one daemon pod May 7 22:48:33.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:33.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:33.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:33.027: INFO: Number of nodes with available pods: 0 May 7 22:48:33.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:34.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:34.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:34.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:34.028: INFO: Number of nodes with available pods: 0 May 7 22:48:34.028: INFO: Node node1 is running more than one daemon pod May 7 22:48:35.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:35.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:35.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:35.025: INFO: Number of nodes with available pods: 0 May 7 22:48:35.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:36.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:36.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:36.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:36.026: INFO: Number of nodes with available pods: 0 May 7 22:48:36.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:37.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:37.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:37.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:37.026: INFO: Number of nodes with available pods: 0 May 7 22:48:37.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:38.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:38.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:38.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:38.027: INFO: Number of nodes with available pods: 0 May 7 22:48:38.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:39.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:39.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:39.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:39.027: INFO: Number of nodes with available pods: 0 May 7 22:48:39.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:40.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:40.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:40.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:40.027: INFO: Number of nodes with available pods: 0 May 7 22:48:40.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:41.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:41.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:41.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:41.027: INFO: Number of nodes with available pods: 0 May 7 22:48:41.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:42.028: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:42.028: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:42.028: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:42.031: INFO: Number of nodes with available pods: 0 May 7 22:48:42.031: INFO: Node node1 is running more than one daemon pod May 7 22:48:43.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:43.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:43.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:43.026: INFO: Number of nodes with available pods: 0 May 7 22:48:43.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:44.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:44.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:44.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:44.026: INFO: Number of nodes with available pods: 0 May 7 22:48:44.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:45.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:45.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:45.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:45.025: INFO: Number of nodes with available pods: 0 May 7 22:48:45.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:46.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:46.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:46.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:46.027: INFO: Number of nodes with available pods: 0 May 7 22:48:46.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:47.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:47.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:47.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:47.026: INFO: Number of nodes with available pods: 0 May 7 22:48:47.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:48.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:48.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:48.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:48.028: INFO: Number of nodes with available pods: 0 May 7 22:48:48.028: INFO: Node node1 is running more than one daemon pod May 7 22:48:49.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:49.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:49.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:49.025: INFO: Number of nodes with available pods: 0 May 7 22:48:49.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:50.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:50.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:50.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:50.027: INFO: Number of nodes with available pods: 0 May 7 22:48:50.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:51.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:51.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:51.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:51.025: INFO: Number of nodes with available pods: 0 May 7 22:48:51.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:52.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:52.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:52.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:52.027: INFO: Number of nodes with available pods: 0 May 7 22:48:52.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:53.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:53.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:53.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:53.026: INFO: Number of nodes with available pods: 0 May 7 22:48:53.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:54.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:54.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:54.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:54.026: INFO: Number of nodes with available pods: 0 May 7 22:48:54.026: INFO: Node node1 is running more than one daemon pod May 7 22:48:55.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:55.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:55.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:55.028: INFO: Number of nodes with available pods: 0 May 7 22:48:55.028: INFO: Node node1 is running more than one daemon pod May 7 22:48:56.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:56.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:56.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:56.025: INFO: Number of nodes with available pods: 0 May 7 22:48:56.025: INFO: Node node1 is running more than one daemon pod May 7 22:48:57.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:57.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:57.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:57.027: INFO: Number of nodes with available pods: 0 May 7 22:48:57.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:58.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:58.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:58.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:58.027: INFO: Number of nodes with available pods: 0 May 7 22:48:58.027: INFO: Node node1 is running more than one daemon pod May 7 22:48:59.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:59.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:59.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:48:59.025: INFO: Number of nodes with available pods: 0 May 7 22:48:59.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:00.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:00.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:00.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:00.026: INFO: Number of nodes with available pods: 0 May 7 22:49:00.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:01.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:01.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:01.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:01.025: INFO: Number of nodes with available pods: 0 May 7 22:49:01.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:02.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:02.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:02.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:02.025: INFO: Number of nodes with available pods: 0 May 7 22:49:02.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:03.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:03.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:03.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:03.027: INFO: Number of nodes with available pods: 0 May 7 22:49:03.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:04.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:04.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:04.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:04.027: INFO: Number of nodes with available pods: 0 May 7 22:49:04.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:05.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:05.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:05.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:05.026: INFO: Number of nodes with available pods: 0 May 7 22:49:05.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:06.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:06.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:06.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:06.027: INFO: Number of nodes with available pods: 0 May 7 22:49:06.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:07.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:07.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:07.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:07.026: INFO: Number of nodes with available pods: 0 May 7 22:49:07.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:08.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:08.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:08.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:08.027: INFO: Number of nodes with available pods: 0 May 7 22:49:08.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:09.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:09.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:09.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:09.027: INFO: Number of nodes with available pods: 0 May 7 22:49:09.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:10.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:10.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:10.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:10.025: INFO: Number of nodes with available pods: 0 May 7 22:49:10.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:11.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:11.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:11.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:11.026: INFO: Number of nodes with available pods: 0 May 7 22:49:11.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:12.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:12.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:12.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:12.027: INFO: Number of nodes with available pods: 0 May 7 22:49:12.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:13.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:13.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:13.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:13.026: INFO: Number of nodes with available pods: 0 May 7 22:49:13.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:14.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:14.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:14.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:14.025: INFO: Number of nodes with available pods: 0 May 7 22:49:14.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:15.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:15.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:15.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:15.025: INFO: Number of nodes with available pods: 0 May 7 22:49:15.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:16.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:16.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:16.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:16.025: INFO: Number of nodes with available pods: 0 May 7 22:49:16.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:17.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:17.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:17.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:17.030: INFO: Number of nodes with available pods: 0 May 7 22:49:17.030: INFO: Node node1 is running more than one daemon pod May 7 22:49:18.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:18.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:18.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:18.026: INFO: Number of nodes with available pods: 0 May 7 22:49:18.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:19.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:19.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:19.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:19.027: INFO: Number of nodes with available pods: 0 May 7 22:49:19.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:20.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:20.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:20.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:20.025: INFO: Number of nodes with available pods: 0 May 7 22:49:20.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:21.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:21.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:21.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:21.026: INFO: Number of nodes with available pods: 0 May 7 22:49:21.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:22.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:22.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:22.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:22.026: INFO: Number of nodes with available pods: 0 May 7 22:49:22.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:23.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:23.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:23.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:23.026: INFO: Number of nodes with available pods: 0 May 7 22:49:23.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:24.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:24.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:24.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:24.024: INFO: Number of nodes with available pods: 0 May 7 22:49:24.024: INFO: Node node1 is running more than one daemon pod May 7 22:49:25.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:25.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:25.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:25.027: INFO: Number of nodes with available pods: 0 May 7 22:49:25.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:26.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:26.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:26.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:26.026: INFO: Number of nodes with available pods: 0 May 7 22:49:26.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:27.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:27.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:27.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:27.025: INFO: Number of nodes with available pods: 0 May 7 22:49:27.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:28.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:28.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:28.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:28.027: INFO: Number of nodes with available pods: 0 May 7 22:49:28.028: INFO: Node node1 is running more than one daemon pod May 7 22:49:29.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:29.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:29.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:29.025: INFO: Number of nodes with available pods: 0 May 7 22:49:29.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:30.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:30.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:30.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:30.027: INFO: Number of nodes with available pods: 0 May 7 22:49:30.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:31.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:31.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:31.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:31.026: INFO: Number of nodes with available pods: 0 May 7 22:49:31.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:32.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:32.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:32.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:32.025: INFO: Number of nodes with available pods: 0 May 7 22:49:32.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:33.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:33.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:33.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:33.026: INFO: Number of nodes with available pods: 0 May 7 22:49:33.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:34.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:34.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:34.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:34.025: INFO: Number of nodes with available pods: 0 May 7 22:49:34.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:35.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:35.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:35.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:35.025: INFO: Number of nodes with available pods: 0 May 7 22:49:35.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:36.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:36.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:36.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:36.027: INFO: Number of nodes with available pods: 0 May 7 22:49:36.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:37.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:37.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:37.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:37.025: INFO: Number of nodes with available pods: 0 May 7 22:49:37.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:38.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:38.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:38.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:38.026: INFO: Number of nodes with available pods: 0 May 7 22:49:38.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:39.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:39.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:39.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:39.025: INFO: Number of nodes with available pods: 0 May 7 22:49:39.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:40.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:40.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:40.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:40.027: INFO: Number of nodes with available pods: 0 May 7 22:49:40.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:41.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:41.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:41.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:41.027: INFO: Number of nodes with available pods: 0 May 7 22:49:41.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:42.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:42.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:42.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:42.027: INFO: Number of nodes with available pods: 0 May 7 22:49:42.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:43.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:43.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:43.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:43.025: INFO: Number of nodes with available pods: 0 May 7 22:49:43.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:44.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:44.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:44.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:44.026: INFO: Number of nodes with available pods: 0 May 7 22:49:44.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:45.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:45.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:45.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:45.027: INFO: Number of nodes with available pods: 0 May 7 22:49:45.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:46.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:46.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:46.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:46.026: INFO: Number of nodes with available pods: 0 May 7 22:49:46.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:47.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:47.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:47.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:47.026: INFO: Number of nodes with available pods: 0 May 7 22:49:47.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:48.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:48.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:48.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:48.026: INFO: Number of nodes with available pods: 0 May 7 22:49:48.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:49.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:49.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:49.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:49.025: INFO: Number of nodes with available pods: 0 May 7 22:49:49.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:50.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:50.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:50.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:50.027: INFO: Number of nodes with available pods: 0 May 7 22:49:50.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:51.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:51.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:51.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:51.026: INFO: Number of nodes with available pods: 0 May 7 22:49:51.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:52.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:52.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:52.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:52.027: INFO: Number of nodes with available pods: 0 May 7 22:49:52.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:53.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:53.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:53.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:53.026: INFO: Number of nodes with available pods: 0 May 7 22:49:53.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:54.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:54.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:54.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:54.025: INFO: Number of nodes with available pods: 0 May 7 22:49:54.025: INFO: Node node1 is running more than one daemon pod May 7 22:49:55.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:55.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:55.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:55.026: INFO: Number of nodes with available pods: 0 May 7 22:49:55.026: INFO: Node node1 is running more than one daemon pod May 7 22:49:56.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:56.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:56.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:56.027: INFO: Number of nodes with available pods: 0 May 7 22:49:56.027: INFO: Node node1 is running more than one daemon pod May 7 22:49:57.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:57.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:57.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:57.028: INFO: Number of nodes with available pods: 0 May 7 22:49:57.028: INFO: Node node1 is running more than one daemon pod May 7 22:49:58.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:58.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:58.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:58.024: INFO: Number of nodes with available pods: 0 May 7 22:49:58.024: INFO: Node node1 is running more than one daemon pod May 7 22:49:59.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:59.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:59.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:49:59.026: INFO: Number of nodes with available pods: 0 May 7 22:49:59.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:00.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:00.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:00.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:00.026: INFO: Number of nodes with available pods: 0 May 7 22:50:00.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:01.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:01.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:01.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:01.026: INFO: Number of nodes with available pods: 0 May 7 22:50:01.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:02.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:02.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:02.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:02.027: INFO: Number of nodes with available pods: 0 May 7 22:50:02.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:03.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:03.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:03.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:03.025: INFO: Number of nodes with available pods: 0 May 7 22:50:03.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:04.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:04.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:04.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:04.026: INFO: Number of nodes with available pods: 0 May 7 22:50:04.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:05.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:05.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:05.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:05.028: INFO: Number of nodes with available pods: 0 May 7 22:50:05.028: INFO: Node node1 is running more than one daemon pod May 7 22:50:06.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:06.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:06.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:06.027: INFO: Number of nodes with available pods: 0 May 7 22:50:06.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:07.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:07.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:07.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:07.029: INFO: Number of nodes with available pods: 0 May 7 22:50:07.029: INFO: Node node1 is running more than one daemon pod May 7 22:50:08.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:08.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:08.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:08.025: INFO: Number of nodes with available pods: 0 May 7 22:50:08.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:09.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:09.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:09.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:09.025: INFO: Number of nodes with available pods: 0 May 7 22:50:09.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:10.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:10.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:10.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:10.027: INFO: Number of nodes with available pods: 0 May 7 22:50:10.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:11.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:11.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:11.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:11.025: INFO: Number of nodes with available pods: 0 May 7 22:50:11.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:12.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:12.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:12.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:12.025: INFO: Number of nodes with available pods: 0 May 7 22:50:12.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:13.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:13.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:13.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:13.026: INFO: Number of nodes with available pods: 0 May 7 22:50:13.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:14.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:14.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:14.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:14.026: INFO: Number of nodes with available pods: 0 May 7 22:50:14.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:15.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:15.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:15.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:15.026: INFO: Number of nodes with available pods: 0 May 7 22:50:15.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:16.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:16.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:16.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:16.026: INFO: Number of nodes with available pods: 0 May 7 22:50:16.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:17.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:17.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:17.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:17.026: INFO: Number of nodes with available pods: 0 May 7 22:50:17.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:18.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:18.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:18.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:18.027: INFO: Number of nodes with available pods: 0 May 7 22:50:18.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:19.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:19.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:19.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:19.026: INFO: Number of nodes with available pods: 0 May 7 22:50:19.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:20.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:20.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:20.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:20.026: INFO: Number of nodes with available pods: 0 May 7 22:50:20.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:21.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:21.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:21.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:21.026: INFO: Number of nodes with available pods: 0 May 7 22:50:21.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:22.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:22.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:22.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:22.025: INFO: Number of nodes with available pods: 0 May 7 22:50:22.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:23.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:23.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:23.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:23.026: INFO: Number of nodes with available pods: 0 May 7 22:50:23.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:24.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:24.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:24.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:24.027: INFO: Number of nodes with available pods: 0 May 7 22:50:24.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:25.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:25.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:25.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:25.026: INFO: Number of nodes with available pods: 0 May 7 22:50:25.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:26.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:26.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:26.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:26.026: INFO: Number of nodes with available pods: 0 May 7 22:50:26.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:27.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:27.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:27.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:27.028: INFO: Number of nodes with available pods: 0 May 7 22:50:27.028: INFO: Node node1 is running more than one daemon pod May 7 22:50:28.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:28.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:28.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:28.027: INFO: Number of nodes with available pods: 0 May 7 22:50:28.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:29.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:29.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:29.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:29.025: INFO: Number of nodes with available pods: 0 May 7 22:50:29.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:30.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:30.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:30.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:30.026: INFO: Number of nodes with available pods: 0 May 7 22:50:30.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:31.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:31.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:31.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:31.025: INFO: Number of nodes with available pods: 0 May 7 22:50:31.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:32.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:32.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:32.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:32.026: INFO: Number of nodes with available pods: 0 May 7 22:50:32.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:33.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:33.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:33.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:33.026: INFO: Number of nodes with available pods: 0 May 7 22:50:33.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:34.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:34.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:34.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:34.025: INFO: Number of nodes with available pods: 0 May 7 22:50:34.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:35.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:35.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:35.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:35.027: INFO: Number of nodes with available pods: 0 May 7 22:50:35.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:36.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:36.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:36.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:36.025: INFO: Number of nodes with available pods: 0 May 7 22:50:36.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:37.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:37.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:37.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:37.026: INFO: Number of nodes with available pods: 0 May 7 22:50:37.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:38.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:38.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:38.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:38.027: INFO: Number of nodes with available pods: 0 May 7 22:50:38.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:39.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:39.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:39.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:39.025: INFO: Number of nodes with available pods: 0 May 7 22:50:39.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:40.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:40.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:40.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:40.025: INFO: Number of nodes with available pods: 0 May 7 22:50:40.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:41.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:41.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:41.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:41.028: INFO: Number of nodes with available pods: 0 May 7 22:50:41.028: INFO: Node node1 is running more than one daemon pod May 7 22:50:42.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:42.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:42.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:42.028: INFO: Number of nodes with available pods: 0 May 7 22:50:42.028: INFO: Node node1 is running more than one daemon pod May 7 22:50:43.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:43.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:43.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:43.025: INFO: Number of nodes with available pods: 0 May 7 22:50:43.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:44.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:44.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:44.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:44.026: INFO: Number of nodes with available pods: 0 May 7 22:50:44.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:45.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:45.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:45.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:45.029: INFO: Number of nodes with available pods: 0 May 7 22:50:45.029: INFO: Node node1 is running more than one daemon pod May 7 22:50:46.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:46.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:46.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:46.027: INFO: Number of nodes with available pods: 0 May 7 22:50:46.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:47.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:47.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:47.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:47.026: INFO: Number of nodes with available pods: 0 May 7 22:50:47.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:48.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:48.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:48.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:48.027: INFO: Number of nodes with available pods: 0 May 7 22:50:48.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:49.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:49.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:49.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:49.025: INFO: Number of nodes with available pods: 0 May 7 22:50:49.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:50.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:50.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:50.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:50.027: INFO: Number of nodes with available pods: 0 May 7 22:50:50.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:51.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:51.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:51.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:51.028: INFO: Number of nodes with available pods: 0 May 7 22:50:51.028: INFO: Node node1 is running more than one daemon pod May 7 22:50:52.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:52.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:52.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:52.027: INFO: Number of nodes with available pods: 0 May 7 22:50:52.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:53.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:53.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:53.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:53.027: INFO: Number of nodes with available pods: 0 May 7 22:50:53.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:54.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:54.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:54.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:54.025: INFO: Number of nodes with available pods: 0 May 7 22:50:54.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:55.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:55.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:55.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:55.025: INFO: Number of nodes with available pods: 0 May 7 22:50:55.025: INFO: Node node1 is running more than one daemon pod May 7 22:50:56.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:56.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:56.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:56.028: INFO: Number of nodes with available pods: 0 May 7 22:50:56.028: INFO: Node node1 is running more than one daemon pod May 7 22:50:57.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:57.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:57.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:57.027: INFO: Number of nodes with available pods: 0 May 7 22:50:57.027: INFO: Node node1 is running more than one daemon pod May 7 22:50:58.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:58.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:58.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:58.026: INFO: Number of nodes with available pods: 0 May 7 22:50:58.026: INFO: Node node1 is running more than one daemon pod May 7 22:50:59.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:59.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:59.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:50:59.027: INFO: Number of nodes with available pods: 0 May 7 22:50:59.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:00.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:00.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:00.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:00.027: INFO: Number of nodes with available pods: 0 May 7 22:51:00.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:01.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:01.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:01.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:01.026: INFO: Number of nodes with available pods: 0 May 7 22:51:01.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:02.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:02.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:02.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:02.026: INFO: Number of nodes with available pods: 0 May 7 22:51:02.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:03.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:03.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:03.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:03.028: INFO: Number of nodes with available pods: 0 May 7 22:51:03.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:04.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:04.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:04.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:04.026: INFO: Number of nodes with available pods: 0 May 7 22:51:04.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:05.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:05.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:05.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:05.025: INFO: Number of nodes with available pods: 0 May 7 22:51:05.025: INFO: Node node1 is running more than one daemon pod May 7 22:51:06.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:06.022: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:06.022: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:06.025: INFO: Number of nodes with available pods: 0 May 7 22:51:06.025: INFO: Node node1 is running more than one daemon pod May 7 22:51:07.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:07.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:07.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:07.027: INFO: Number of nodes with available pods: 0 May 7 22:51:07.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:08.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:08.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:08.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:08.026: INFO: Number of nodes with available pods: 0 May 7 22:51:08.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:09.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:09.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:09.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:09.025: INFO: Number of nodes with available pods: 0 May 7 22:51:09.025: INFO: Node node1 is running more than one daemon pod May 7 22:51:10.022: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:10.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:10.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:10.025: INFO: Number of nodes with available pods: 0 May 7 22:51:10.025: INFO: Node node1 is running more than one daemon pod May 7 22:51:11.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:11.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:11.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:11.026: INFO: Number of nodes with available pods: 0 May 7 22:51:11.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:12.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:12.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:12.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:12.028: INFO: Number of nodes with available pods: 0 May 7 22:51:12.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:13.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:13.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:13.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:13.027: INFO: Number of nodes with available pods: 0 May 7 22:51:13.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:14.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:14.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:14.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:14.027: INFO: Number of nodes with available pods: 0 May 7 22:51:14.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:15.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:15.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:15.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:15.028: INFO: Number of nodes with available pods: 0 May 7 22:51:15.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:16.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:16.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:16.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:16.028: INFO: Number of nodes with available pods: 0 May 7 22:51:16.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:17.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:17.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:17.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:17.029: INFO: Number of nodes with available pods: 0 May 7 22:51:17.029: INFO: Node node1 is running more than one daemon pod May 7 22:51:18.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:18.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:18.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:18.025: INFO: Number of nodes with available pods: 0 May 7 22:51:18.025: INFO: Node node1 is running more than one daemon pod May 7 22:51:19.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:19.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:19.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:19.026: INFO: Number of nodes with available pods: 0 May 7 22:51:19.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:20.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:20.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:20.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:20.028: INFO: Number of nodes with available pods: 0 May 7 22:51:20.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:21.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:21.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:21.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:21.025: INFO: Number of nodes with available pods: 0 May 7 22:51:21.025: INFO: Node node1 is running more than one daemon pod May 7 22:51:22.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:22.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:22.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:22.026: INFO: Number of nodes with available pods: 0 May 7 22:51:22.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:23.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:23.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:23.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:23.027: INFO: Number of nodes with available pods: 0 May 7 22:51:23.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:24.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:24.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:24.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:24.027: INFO: Number of nodes with available pods: 0 May 7 22:51:24.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:25.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:25.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:25.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:25.028: INFO: Number of nodes with available pods: 0 May 7 22:51:25.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:26.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:26.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:26.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:26.027: INFO: Number of nodes with available pods: 0 May 7 22:51:26.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:27.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:27.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:27.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:27.028: INFO: Number of nodes with available pods: 0 May 7 22:51:27.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:28.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:28.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:28.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:28.027: INFO: Number of nodes with available pods: 0 May 7 22:51:28.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:29.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:29.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:29.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:29.029: INFO: Number of nodes with available pods: 0 May 7 22:51:29.029: INFO: Node node1 is running more than one daemon pod May 7 22:51:30.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:30.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:30.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:30.027: INFO: Number of nodes with available pods: 0 May 7 22:51:30.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:31.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:31.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:31.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:31.028: INFO: Number of nodes with available pods: 0 May 7 22:51:31.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:32.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:32.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:32.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:32.028: INFO: Number of nodes with available pods: 0 May 7 22:51:32.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:33.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:33.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:33.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:33.027: INFO: Number of nodes with available pods: 0 May 7 22:51:33.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:34.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:34.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:34.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:34.027: INFO: Number of nodes with available pods: 0 May 7 22:51:34.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:35.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:35.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:35.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:35.028: INFO: Number of nodes with available pods: 0 May 7 22:51:35.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:36.027: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:36.027: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:36.027: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:36.030: INFO: Number of nodes with available pods: 0 May 7 22:51:36.030: INFO: Node node1 is running more than one daemon pod May 7 22:51:37.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:37.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:37.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:37.028: INFO: Number of nodes with available pods: 0 May 7 22:51:37.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:38.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:38.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:38.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:38.027: INFO: Number of nodes with available pods: 0 May 7 22:51:38.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:39.027: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:39.027: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:39.027: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:39.030: INFO: Number of nodes with available pods: 0 May 7 22:51:39.030: INFO: Node node1 is running more than one daemon pod May 7 22:51:40.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:40.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:40.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:40.027: INFO: Number of nodes with available pods: 0 May 7 22:51:40.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:41.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:41.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:41.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:41.028: INFO: Number of nodes with available pods: 0 May 7 22:51:41.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:42.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:42.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:42.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:42.028: INFO: Number of nodes with available pods: 0 May 7 22:51:42.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:43.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:43.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:43.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:43.027: INFO: Number of nodes with available pods: 0 May 7 22:51:43.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:44.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:44.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:44.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:44.027: INFO: Number of nodes with available pods: 0 May 7 22:51:44.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:45.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:45.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:45.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:45.028: INFO: Number of nodes with available pods: 0 May 7 22:51:45.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:46.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:46.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:46.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:46.026: INFO: Number of nodes with available pods: 0 May 7 22:51:46.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:47.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:47.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:47.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:47.028: INFO: Number of nodes with available pods: 0 May 7 22:51:47.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:48.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:48.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:48.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:48.028: INFO: Number of nodes with available pods: 0 May 7 22:51:48.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:49.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:49.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:49.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:49.028: INFO: Number of nodes with available pods: 0 May 7 22:51:49.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:50.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:50.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:50.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:50.029: INFO: Number of nodes with available pods: 0 May 7 22:51:50.029: INFO: Node node1 is running more than one daemon pod May 7 22:51:51.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:51.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:51.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:51.028: INFO: Number of nodes with available pods: 0 May 7 22:51:51.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:52.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:52.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:52.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:52.026: INFO: Number of nodes with available pods: 0 May 7 22:51:52.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:53.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:53.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:53.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:53.027: INFO: Number of nodes with available pods: 0 May 7 22:51:53.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:54.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:54.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:54.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:54.027: INFO: Number of nodes with available pods: 0 May 7 22:51:54.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:55.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:55.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:55.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:55.026: INFO: Number of nodes with available pods: 0 May 7 22:51:55.026: INFO: Node node1 is running more than one daemon pod May 7 22:51:56.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:56.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:56.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:56.027: INFO: Number of nodes with available pods: 0 May 7 22:51:56.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:57.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:57.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:57.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:57.028: INFO: Number of nodes with available pods: 0 May 7 22:51:57.028: INFO: Node node1 is running more than one daemon pod May 7 22:51:58.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:58.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:58.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:58.027: INFO: Number of nodes with available pods: 0 May 7 22:51:58.027: INFO: Node node1 is running more than one daemon pod May 7 22:51:59.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:59.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:59.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:51:59.029: INFO: Number of nodes with available pods: 0 May 7 22:51:59.029: INFO: Node node1 is running more than one daemon pod May 7 22:52:00.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:00.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:00.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:00.030: INFO: Number of nodes with available pods: 0 May 7 22:52:00.030: INFO: Node node1 is running more than one daemon pod May 7 22:52:01.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:01.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:01.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:01.027: INFO: Number of nodes with available pods: 0 May 7 22:52:01.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:02.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:02.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:02.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:02.029: INFO: Number of nodes with available pods: 0 May 7 22:52:02.029: INFO: Node node1 is running more than one daemon pod May 7 22:52:03.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:03.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:03.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:03.026: INFO: Number of nodes with available pods: 0 May 7 22:52:03.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:04.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:04.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:04.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:04.028: INFO: Number of nodes with available pods: 0 May 7 22:52:04.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:05.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:05.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:05.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:05.027: INFO: Number of nodes with available pods: 0 May 7 22:52:05.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:06.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:06.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:06.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:06.027: INFO: Number of nodes with available pods: 0 May 7 22:52:06.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:07.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:07.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:07.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:07.033: INFO: Number of nodes with available pods: 0 May 7 22:52:07.033: INFO: Node node1 is running more than one daemon pod May 7 22:52:08.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:08.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:08.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:08.027: INFO: Number of nodes with available pods: 0 May 7 22:52:08.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:09.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:09.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:09.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:09.028: INFO: Number of nodes with available pods: 0 May 7 22:52:09.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:10.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:10.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:10.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:10.028: INFO: Number of nodes with available pods: 0 May 7 22:52:10.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:11.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:11.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:11.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:11.025: INFO: Number of nodes with available pods: 0 May 7 22:52:11.025: INFO: Node node1 is running more than one daemon pod May 7 22:52:12.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:12.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:12.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:12.028: INFO: Number of nodes with available pods: 0 May 7 22:52:12.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:13.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:13.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:13.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:13.028: INFO: Number of nodes with available pods: 0 May 7 22:52:13.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:14.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:14.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:14.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:14.027: INFO: Number of nodes with available pods: 0 May 7 22:52:14.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:15.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:15.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:15.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:15.028: INFO: Number of nodes with available pods: 0 May 7 22:52:15.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:16.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:16.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:16.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:16.026: INFO: Number of nodes with available pods: 0 May 7 22:52:16.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:17.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:17.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:17.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:17.028: INFO: Number of nodes with available pods: 0 May 7 22:52:17.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:18.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:18.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:18.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:18.026: INFO: Number of nodes with available pods: 0 May 7 22:52:18.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:19.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:19.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:19.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:19.028: INFO: Number of nodes with available pods: 0 May 7 22:52:19.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:20.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:20.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:20.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:20.027: INFO: Number of nodes with available pods: 0 May 7 22:52:20.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:21.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:21.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:21.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:21.026: INFO: Number of nodes with available pods: 0 May 7 22:52:21.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:22.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:22.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:22.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:22.026: INFO: Number of nodes with available pods: 0 May 7 22:52:22.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:23.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:23.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:23.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:23.026: INFO: Number of nodes with available pods: 0 May 7 22:52:23.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:24.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:24.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:24.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:24.027: INFO: Number of nodes with available pods: 0 May 7 22:52:24.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:25.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:25.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:25.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:25.026: INFO: Number of nodes with available pods: 0 May 7 22:52:25.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:26.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:26.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:26.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:26.029: INFO: Number of nodes with available pods: 0 May 7 22:52:26.029: INFO: Node node1 is running more than one daemon pod May 7 22:52:27.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:27.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:27.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:27.027: INFO: Number of nodes with available pods: 0 May 7 22:52:27.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:28.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:28.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:28.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:28.027: INFO: Number of nodes with available pods: 0 May 7 22:52:28.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:29.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:29.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:29.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:29.025: INFO: Number of nodes with available pods: 0 May 7 22:52:29.025: INFO: Node node1 is running more than one daemon pod May 7 22:52:30.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:30.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:30.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:30.026: INFO: Number of nodes with available pods: 0 May 7 22:52:30.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:31.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:31.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:31.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:31.025: INFO: Number of nodes with available pods: 0 May 7 22:52:31.025: INFO: Node node1 is running more than one daemon pod May 7 22:52:32.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:32.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:32.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:32.026: INFO: Number of nodes with available pods: 0 May 7 22:52:32.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:33.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:33.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:33.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:33.026: INFO: Number of nodes with available pods: 0 May 7 22:52:33.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:34.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:34.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:34.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:34.027: INFO: Number of nodes with available pods: 0 May 7 22:52:34.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:35.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:35.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:35.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:35.028: INFO: Number of nodes with available pods: 0 May 7 22:52:35.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:36.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:36.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:36.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:36.028: INFO: Number of nodes with available pods: 0 May 7 22:52:36.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:37.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:37.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:37.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:37.028: INFO: Number of nodes with available pods: 0 May 7 22:52:37.028: INFO: Node node1 is running more than one daemon pod May 7 22:52:38.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:38.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:38.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:38.026: INFO: Number of nodes with available pods: 0 May 7 22:52:38.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:39.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:39.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:39.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:39.029: INFO: Number of nodes with available pods: 0 May 7 22:52:39.029: INFO: Node node1 is running more than one daemon pod May 7 22:52:40.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:40.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:40.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:40.027: INFO: Number of nodes with available pods: 0 May 7 22:52:40.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:41.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:41.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:41.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:41.026: INFO: Number of nodes with available pods: 0 May 7 22:52:41.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:42.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:42.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:42.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:42.026: INFO: Number of nodes with available pods: 0 May 7 22:52:42.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:43.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:43.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:43.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:43.026: INFO: Number of nodes with available pods: 0 May 7 22:52:43.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:44.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:44.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:44.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:44.027: INFO: Number of nodes with available pods: 0 May 7 22:52:44.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:45.025: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:45.025: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:45.025: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:45.027: INFO: Number of nodes with available pods: 0 May 7 22:52:45.027: INFO: Node node1 is running more than one daemon pod May 7 22:52:46.023: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:46.023: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:46.023: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:46.026: INFO: Number of nodes with available pods: 0 May 7 22:52:46.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:47.026: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:47.026: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:47.026: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:47.029: INFO: Number of nodes with available pods: 0 May 7 22:52:47.029: INFO: Node node1 is running more than one daemon pod May 7 22:52:48.024: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:48.024: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:48.024: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:48.026: INFO: Number of nodes with available pods: 0 May 7 22:52:48.026: INFO: Node node1 is running more than one daemon pod May 7 22:52:48.030: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:48.030: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:48.030: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node May 7 22:52:48.033: INFO: Number of nodes with available pods: 0 May 7 22:52:48.033: INFO: Node node1 is running more than one daemon pod May 7 22:52:48.033: FAIL: error waiting for daemon pod to start Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/apps.glob..func3.6() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:291 +0x4f0 k8s.io/kubernetes/test/e2e.RunE2ETests(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x345 k8s.io/kubernetes/test/e2e.TestE2E(0xc00211a180) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:145 +0x2b testing.tRunner(0xc00211a180, 0x4de37a0) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:100 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-8954, will wait for the garbage collector to delete the pods May 7 22:52:48.096: INFO: Deleting DaemonSet.extensions daemon-set took: 5.927551ms May 7 22:52:48.797: INFO: Terminating DaemonSet.extensions daemon-set pods took: 700.464047ms May 7 22:52:50.600: INFO: Number of nodes with available pods: 0 May 7 22:52:50.600: INFO: Number of running nodes: 0, number of available pods: 0 May 7 22:52:50.602: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"selfLink":"/apis/apps/v1/namespaces/daemonsets-8954/daemonsets","resourceVersion":"60100"},"items":null} May 7 22:52:50.604: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"selfLink":"/api/v1/namespaces/daemonsets-8954/pods","resourceVersion":"60100"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 STEP: Collecting events from namespace "daemonsets-8954". STEP: Found 18 events. May 7 22:52:50.616: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-lch27: { } Scheduled: Successfully assigned daemonsets-8954/daemon-set-lch27 to node1 May 7 22:52:50.616: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for daemon-set-qkcw2: { } Scheduled: Successfully assigned daemonsets-8954/daemon-set-qkcw2 to node2 May 7 22:52:50.616: INFO: At 2021-05-07 22:47:48 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-qkcw2 May 7 22:52:50.616: INFO: At 2021-05-07 22:47:48 +0000 UTC - event for daemon-set: {daemonset-controller } SuccessfulCreate: Created pod: daemon-set-lch27 May 7 22:52:50.616: INFO: At 2021-05-07 22:47:49 +0000 UTC - event for daemon-set-lch27: {multus } AddedInterface: Add eth0 [10.244.3.234/24] May 7 22:52:50.616: INFO: At 2021-05-07 22:47:49 +0000 UTC - event for daemon-set-lch27: {kubelet node1} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:52:50.616: INFO: At 2021-05-07 22:47:49 +0000 UTC - event for daemon-set-qkcw2: {kubelet node2} Pulling: Pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:52:50.616: INFO: At 2021-05-07 22:47:49 +0000 UTC - event for daemon-set-qkcw2: {multus } AddedInterface: Add eth0 [10.244.4.20/24] May 7 22:52:50.616: INFO: At 2021-05-07 22:47:50 +0000 UTC - event for daemon-set-lch27: {kubelet node1} SandboxChanged: Pod sandbox changed, it will be killed and re-created. May 7 22:52:50.616: INFO: At 2021-05-07 22:47:50 +0000 UTC - event for daemon-set-lch27: {kubelet node1} Failed: Error: ErrImagePull May 7 22:52:50.616: INFO: At 2021-05-07 22:47:50 +0000 UTC - event for daemon-set-lch27: {kubelet node1} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:52:50.616: INFO: At 2021-05-07 22:47:50 +0000 UTC - event for daemon-set-qkcw2: {kubelet node2} Failed: Failed to pull image "docker.io/library/httpd:2.4.38-alpine": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit May 7 22:52:50.616: INFO: At 2021-05-07 22:47:50 +0000 UTC - event for daemon-set-qkcw2: {kubelet node2} Failed: Error: ErrImagePull May 7 22:52:50.616: INFO: At 2021-05-07 22:47:50 +0000 UTC - event for daemon-set-qkcw2: {kubelet node2} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:52:50.616: INFO: At 2021-05-07 22:47:50 +0000 UTC - event for daemon-set-qkcw2: {kubelet node2} Failed: Error: ImagePullBackOff May 7 22:52:50.616: INFO: At 2021-05-07 22:47:52 +0000 UTC - event for daemon-set-lch27: {multus } AddedInterface: Add eth0 [10.244.3.235/24] May 7 22:52:50.616: INFO: At 2021-05-07 22:47:52 +0000 UTC - event for daemon-set-lch27: {kubelet node1} BackOff: Back-off pulling image "docker.io/library/httpd:2.4.38-alpine" May 7 22:52:50.616: INFO: At 2021-05-07 22:47:52 +0000 UTC - event for daemon-set-lch27: {kubelet node1} Failed: Error: ImagePullBackOff May 7 22:52:50.618: INFO: POD NODE PHASE GRACE CONDITIONS May 7 22:52:50.618: INFO: May 7 22:52:50.622: INFO: Logging node info for node master1 May 7 22:52:50.624: INFO: Node Info: &Node{ObjectMeta:{master1 /api/v1/nodes/master1 7277f528-99fb-4be3-a928-27761a4599e8 60072 0 2021-05-07 19:59:27 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master1 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"a2:74:f5:d6:48:e4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.202 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/master.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 19:59:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 19:59:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.0.0/24\"":{}},"f:taints":{}}}} {nfd-master Update v1 2021-05-07 20:08:42 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/master.version":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.0.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.0.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:15 +0000 UTC,LastTransitionTime:2021-05-07 20:05:15 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:45 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:45 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:45 +0000 UTC,LastTransitionTime:2021-05-07 19:59:26 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:52:45 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.202,},NodeAddress{Type:Hostname,Address:master1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:44253340a37b4ed7bf5b3a3547b5f57d,SystemUUID:00ACFB60-0631-E711-906E-0017A4403562,BootID:2a44f9c3-2714-4b5c-975d-25d069f66483,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:9d07c391aeb1a9d02eb4343c113ed01825227c70c32b3cae861711f90191b0fd quay.io/coreos/kube-rbac-proxy:v0.4.1],SizeBytes:41317870,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[quay.io/coreos/prometheus-operator@sha256:a54e806fb27d2fb0251da4f3b2a3bb5320759af63a54a755788304775f2384a7 quay.io/coreos/prometheus-operator:v0.40.0],SizeBytes:38238457,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[registry@sha256:1cd9409a311350c3072fe510b52046f104416376c126a479cef9a4dfe692cf57 registry:2.7.0],SizeBytes:24191168,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 tas-controller:latest localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[nginx@sha256:a97eb9ecc708c8aa715ccfb5e9338f5456e4b65575daf304f108301f3b497314 nginx:1.19.2-alpine],SizeBytes:22052669,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 tas-extender:latest localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[@ :],SizeBytes:5577654,},ContainerImage{Names:[alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a alpine:3.12.1],SizeBytes:5573013,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:52:50.625: INFO: Logging kubelet events for node master1 May 7 22:52:50.627: INFO: Logging pods the kubelet thinks is on node master1 May 7 22:52:50.643: INFO: kube-apiserver-master1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.643: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:52:50.643: INFO: kube-controller-manager-master1 started at 2021-05-07 20:04:26 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.643: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:52:50.643: INFO: kube-scheduler-master1 started at 2021-05-07 20:15:37 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.643: INFO: Container kube-scheduler ready: true, restart count 0 May 7 22:52:50.643: INFO: kube-flannel-nj6vr started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:52:50.643: INFO: Init container install-cni ready: true, restart count 0 May 7 22:52:50.643: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:52:50.643: INFO: coredns-7677f9bb54-wvd65 started at 2021-05-07 20:02:30 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.643: INFO: Container coredns ready: true, restart count 2 May 7 22:52:50.643: INFO: node-feature-discovery-controller-5bf5c49849-z2bj7 started at 2021-05-07 20:08:34 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.643: INFO: Container nfd-controller ready: true, restart count 0 May 7 22:52:50.643: INFO: node-exporter-9sm5v started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.643: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:52:50.643: INFO: Container node-exporter ready: true, restart count 0 May 7 22:52:50.643: INFO: kube-proxy-qpvcb started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.643: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:52:50.643: INFO: kube-multus-ds-amd64-8tjh4 started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.643: INFO: Container kube-multus ready: true, restart count 1 May 7 22:52:50.643: INFO: docker-registry-docker-registry-56cbc7bc58-267wq started at 2021-05-07 20:05:51 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.643: INFO: Container docker-registry ready: true, restart count 0 May 7 22:52:50.643: INFO: Container nginx ready: true, restart count 0 May 7 22:52:50.643: INFO: prometheus-operator-5bb8cb9d8f-xqpnw started at 2021-05-07 20:12:35 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.643: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:52:50.643: INFO: Container prometheus-operator ready: true, restart count 0 W0507 22:52:50.656905 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:52:50.683: INFO: Latency metrics for node master1 May 7 22:52:50.683: INFO: Logging node info for node master2 May 7 22:52:50.685: INFO: Node Info: &Node{ObjectMeta:{master2 /api/v1/nodes/master2 8193aa97-7914-4d63-b6cf-a7ceb8fe519c 60062 0 2021-05-07 20:00:06 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master2 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"86:88:6a:bc:18:32"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.203 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {kube-controller-manager Update v1 2021-05-07 20:01:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.1.0/24\"":{}},"f:taints":{}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}}]},Spec:NodeSpec{PodCIDR:10.244.1.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234767872 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324603904 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:58 +0000 UTC,LastTransitionTime:2021-05-07 20:04:58 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:41 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:41 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:41 +0000 UTC,LastTransitionTime:2021-05-07 20:00:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:52:41 +0000 UTC,LastTransitionTime:2021-05-07 20:02:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.203,},NodeAddress{Type:Hostname,Address:master2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:cf652b4fb7284de2aaafc5f52f51e312,SystemUUID:00A0DE53-E51D-E711-906E-0017A4403562,BootID:df4da196-5a1c-4b40-aef7-034e79f7a8e2,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:52:50.685: INFO: Logging kubelet events for node master2 May 7 22:52:50.688: INFO: Logging pods the kubelet thinks is on node master2 May 7 22:52:50.702: INFO: node-exporter-6nqvj started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.702: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:52:50.702: INFO: Container node-exporter ready: true, restart count 0 May 7 22:52:50.702: INFO: kube-apiserver-master2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.702: INFO: Container kube-apiserver ready: true, restart count 0 May 7 22:52:50.702: INFO: kube-controller-manager-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.702: INFO: Container kube-controller-manager ready: true, restart count 2 May 7 22:52:50.702: INFO: kube-scheduler-master2 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.702: INFO: Container kube-scheduler ready: true, restart count 2 May 7 22:52:50.702: INFO: kube-proxy-fg5dt started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.702: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:52:50.702: INFO: kube-flannel-wwlww started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:52:50.702: INFO: Init container install-cni ready: true, restart count 0 May 7 22:52:50.702: INFO: Container kube-flannel ready: true, restart count 1 May 7 22:52:50.702: INFO: kube-multus-ds-amd64-44vrh started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.702: INFO: Container kube-multus ready: true, restart count 1 May 7 22:52:50.702: INFO: dns-autoscaler-5b7b5c9b6f-flqh2 started at 2021-05-07 20:02:33 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.702: INFO: Container autoscaler ready: true, restart count 2 W0507 22:52:50.713513 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:52:50.742: INFO: Latency metrics for node master2 May 7 22:52:50.742: INFO: Logging node info for node master3 May 7 22:52:50.745: INFO: Node Info: &Node{ObjectMeta:{master3 /api/v1/nodes/master3 27e1bfdf-bb8c-4924-9488-acacef172e76 60063 0 2021-05-07 20:00:17 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:master3 kubernetes.io/os:linux node-role.kubernetes.io/master:] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"de:31:a8:23:73:1a"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.204 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2021-05-07 20:00:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}} {kubeadm Update v1 2021-05-07 20:00:18 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/master":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-05-07 20:02:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.2.0/24\"":{}},"f:taints":{}}}}]},Spec:NodeSpec{PodCIDR:10.244.2.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:,},},ConfigSource:nil,PodCIDRs:[10.244.2.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{201234763776 0} {} 196518324Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{79550 -3} {} 79550m DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{0 0} {} 0 DecimalSI},memory: {{200324599808 0} {} 195629492Ki BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:04:10 +0000 UTC,LastTransitionTime:2021-05-07 20:04:10 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:41 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:41 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:41 +0000 UTC,LastTransitionTime:2021-05-07 20:00:17 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:52:41 +0000 UTC,LastTransitionTime:2021-05-07 20:03:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.204,},NodeAddress{Type:Hostname,Address:master3,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:01ba71adbf0d4ef79a9af064c18faf21,SystemUUID:008B1444-141E-E711-906E-0017A4403562,BootID:1692e58d-c13c-425c-b11a-62d901f965ec,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[quay.io/coreos/etcd@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017 quay.io/coreos/etcd:v3.4.13],SizeBytes:83790470,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[k8s.gcr.io/coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c k8s.gcr.io/coredns:1.7.0],SizeBytes:45227747,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64@sha256:dce43068853ad396b0fb5ace9a56cc14114e31979e241342d12d04526be1dfcc k8s.gcr.io/cpa/cluster-proportional-autoscaler-amd64:1.8.3],SizeBytes:40647382,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:52:50.746: INFO: Logging kubelet events for node master3 May 7 22:52:50.749: INFO: Logging pods the kubelet thinks is on node master3 May 7 22:52:50.766: INFO: kube-controller-manager-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.766: INFO: Container kube-controller-manager ready: true, restart count 3 May 7 22:52:50.766: INFO: kube-scheduler-master3 started at 2021-05-07 20:00:42 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.766: INFO: Container kube-scheduler ready: true, restart count 2 May 7 22:52:50.766: INFO: kube-proxy-lvj72 started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.766: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:52:50.766: INFO: kube-flannel-j2xn4 started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:52:50.766: INFO: Init container install-cni ready: true, restart count 1 May 7 22:52:50.766: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:52:50.766: INFO: kube-multus-ds-amd64-hhqgw started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.766: INFO: Container kube-multus ready: true, restart count 1 May 7 22:52:50.766: INFO: coredns-7677f9bb54-pj7xl started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.766: INFO: Container coredns ready: true, restart count 2 May 7 22:52:50.766: INFO: node-exporter-tsk7w started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.766: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:52:50.766: INFO: Container node-exporter ready: true, restart count 0 May 7 22:52:50.766: INFO: kube-apiserver-master3 started at 2021-05-07 20:03:45 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.766: INFO: Container kube-apiserver ready: true, restart count 0 W0507 22:52:50.779842 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:52:50.805: INFO: Latency metrics for node master3 May 7 22:52:50.805: INFO: Logging node info for node node1 May 7 22:52:50.808: INFO: Node Info: &Node{ObjectMeta:{node1 /api/v1/nodes/node1 24d047f7-eb29-4f1d-96d0-63b225220bd5 60090 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node1 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"da:1d:6f:d2:a8:b4"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.207 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.3.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:09 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {e2e.test Update v1 2021-05-07 22:44:37 +0000 UTC FieldsV1 {"f:status":{"f:capacity":{"f:example.com/fakecpu":{}}}}} {kubelet Update v1 2021-05-07 22:47:48 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:example.com/fakecpu":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.3.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},example.com/fakecpu: {{1 3} {} 1k DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},example.com/fakecpu: {{1 3} {} 1k DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:03:55 +0000 UTC,LastTransitionTime:2021-05-07 20:03:55 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:49 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:49 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:49 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:52:49 +0000 UTC,LastTransitionTime:2021-05-07 20:03:44 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.207,},NodeAddress{Type:Hostname,Address:node1,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:d79c3a817fbd4f03a173930e545bb174,SystemUUID:00CDA902-D022-E711-906E-0017A4403562,BootID:53771151-d654-4c88-80fe-48032d3317a5,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[@ :],SizeBytes:1002488002,},ContainerImage{Names:[opnfv/barometer-collectd@sha256:ed5c574f653e2a39e784ff322033a2319aafde7366c803a88f20f7a2a8bc1efb opnfv/barometer-collectd:stable],SizeBytes:825413035,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec cmk:v1.5.1 localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[golang@sha256:1636899c10870ab66c48d960a9df620f4f9e86a0c72fbacf36032d27404e7e6c golang:alpine3.12],SizeBytes:301156062,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[grafana/grafana@sha256:89304bc2335f4976618548d7b93d165ed67369d3a051d2f627fc4e0aa3d0aff1 grafana/grafana:7.1.0],SizeBytes:179601493,},ContainerImage{Names:[quay.io/prometheus/prometheus@sha256:d4ba4dd1a9ebb90916d0bfed3c204adcb118ed24546bf8dd2e6b30fc0fd2009e quay.io/prometheus/prometheus:v2.20.0],SizeBytes:144886595,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[directxman12/k8s-prometheus-adapter-amd64@sha256:b63dc612e3cb73f79d2401a4516f794f9f0a83002600ca72e675e41baecff437 directxman12/k8s-prometheus-adapter-amd64:v0.6.0],SizeBytes:53267842,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d nfvpe/sriov-device-plugin:latest localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[kubernetesui/metrics-scraper@sha256:1f977343873ed0e2efd4916a6b2f3075f310ff6fe42ee098f54fc58aa7a28ab7 kubernetesui/metrics-scraper:v1.0.6],SizeBytes:34548789,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[quay.io/coreos/prometheus-config-reloader@sha256:c679a143b24b7731ad1577a9865aa3805426cbf1b25e30807b951dff68466ffd quay.io/coreos/prometheus-config-reloader:v0.40.0],SizeBytes:10131705,},ContainerImage{Names:[jimmidyson/configmap-reload@sha256:d107c7a235c266273b1c3502a391fec374430e5625539403d0de797fa9c556a2 jimmidyson/configmap-reload:v0.3.0],SizeBytes:9700438,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[appropriate/curl@sha256:027a0ad3c69d085fea765afca9984787b780c172cead6502fec989198b98d8bb appropriate/curl:edge],SizeBytes:5654234,},ContainerImage{Names:[alpine@sha256:36553b10a4947067b9fbb7d532951066293a68eae893beba1d9235f7d11a20ad alpine:3.12],SizeBytes:5581415,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[gcr.io/authenticated-image-pulling/alpine@sha256:7ff177862cb50c602bfe81f805969412e619c054a2bbead977d0c276988aa4a0 gcr.io/authenticated-image-pulling/alpine:3.7],SizeBytes:4206620,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:52:50.809: INFO: Logging kubelet events for node node1 May 7 22:52:50.812: INFO: Logging pods the kubelet thinks is on node node1 May 7 22:52:50.830: INFO: nginx-proxy-node1 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.830: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:52:50.830: INFO: kubernetes-metrics-scraper-678c97765c-g7srv started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.830: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:52:50.830: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.830: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:52:50.830: INFO: node-exporter-mpq58 started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.830: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:52:50.830: INFO: Container node-exporter ready: true, restart count 0 May 7 22:52:50.830: INFO: collectd-tmjfs started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:52:50.830: INFO: Container collectd ready: true, restart count 0 May 7 22:52:50.830: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:52:50.830: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:52:50.830: INFO: node-feature-discovery-worker-xvbpd started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.830: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:52:50.830: INFO: kube-proxy-bms7z started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.830: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:52:50.830: INFO: cmk-init-discover-node1-krbjn started at 2021-05-07 20:11:05 +0000 UTC (0+3 container statuses recorded) May 7 22:52:50.830: INFO: Container discover ready: false, restart count 0 May 7 22:52:50.830: INFO: Container init ready: false, restart count 0 May 7 22:52:50.830: INFO: Container install ready: false, restart count 0 May 7 22:52:50.830: INFO: cmk-gjhf2 started at 2021-05-07 20:11:48 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.830: INFO: Container nodereport ready: true, restart count 0 May 7 22:52:50.830: INFO: Container reconcile ready: true, restart count 0 May 7 22:52:50.830: INFO: kube-multus-ds-amd64-fxgdb started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.830: INFO: Container kube-multus ready: true, restart count 1 May 7 22:52:50.830: INFO: prometheus-k8s-0 started at 2021-05-07 20:12:50 +0000 UTC (0+5 container statuses recorded) May 7 22:52:50.830: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:52:50.830: INFO: Container grafana ready: true, restart count 0 May 7 22:52:50.830: INFO: Container prometheus ready: true, restart count 1 May 7 22:52:50.830: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:52:50.830: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:52:50.830: INFO: kube-flannel-qm7lv started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:52:50.830: INFO: Init container install-cni ready: true, restart count 2 May 7 22:52:50.830: INFO: Container kube-flannel ready: true, restart count 2 W0507 22:52:50.843820 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:52:50.881: INFO: Latency metrics for node node1 May 7 22:52:50.881: INFO: Logging node info for node node2 May 7 22:52:50.885: INFO: Node Info: &Node{ObjectMeta:{node2 /api/v1/nodes/node2 eae422ac-f6f0-4e9a-961d-e133dffc36be 60078 0 2021-05-07 20:01:25 +0000 UTC map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux cmk.intel.com/cmk-node:true feature.node.kubernetes.io/cpu-cpuid.ADX:true feature.node.kubernetes.io/cpu-cpuid.AESNI:true feature.node.kubernetes.io/cpu-cpuid.AVX:true feature.node.kubernetes.io/cpu-cpuid.AVX2:true feature.node.kubernetes.io/cpu-cpuid.AVX512BW:true feature.node.kubernetes.io/cpu-cpuid.AVX512CD:true feature.node.kubernetes.io/cpu-cpuid.AVX512DQ:true feature.node.kubernetes.io/cpu-cpuid.AVX512F:true feature.node.kubernetes.io/cpu-cpuid.AVX512VL:true feature.node.kubernetes.io/cpu-cpuid.FMA3:true feature.node.kubernetes.io/cpu-cpuid.HLE:true feature.node.kubernetes.io/cpu-cpuid.IBPB:true feature.node.kubernetes.io/cpu-cpuid.MPX:true feature.node.kubernetes.io/cpu-cpuid.RTM:true feature.node.kubernetes.io/cpu-cpuid.STIBP:true feature.node.kubernetes.io/cpu-cpuid.VMX:true feature.node.kubernetes.io/cpu-hardware_multithreading:true feature.node.kubernetes.io/cpu-pstate.turbo:true feature.node.kubernetes.io/cpu-rdt.RDTCMT:true feature.node.kubernetes.io/cpu-rdt.RDTL3CA:true feature.node.kubernetes.io/cpu-rdt.RDTMBA:true feature.node.kubernetes.io/cpu-rdt.RDTMBM:true feature.node.kubernetes.io/cpu-rdt.RDTMON:true feature.node.kubernetes.io/kernel-config.NO_HZ:true feature.node.kubernetes.io/kernel-config.NO_HZ_FULL:true feature.node.kubernetes.io/kernel-selinux.enabled:true feature.node.kubernetes.io/kernel-version.full:3.10.0-1160.25.1.el7.x86_64 feature.node.kubernetes.io/kernel-version.major:3 feature.node.kubernetes.io/kernel-version.minor:10 feature.node.kubernetes.io/kernel-version.revision:0 feature.node.kubernetes.io/memory-numa:true feature.node.kubernetes.io/network-sriov.capable:true feature.node.kubernetes.io/network-sriov.configured:true feature.node.kubernetes.io/pci-0300_1a03.present:true feature.node.kubernetes.io/storage-nonrotationaldisk:true feature.node.kubernetes.io/system-os_release.ID:centos feature.node.kubernetes.io/system-os_release.VERSION_ID:7 feature.node.kubernetes.io/system-os_release.VERSION_ID.major:7 kubernetes.io/arch:amd64 kubernetes.io/hostname:node2 kubernetes.io/os:linux] map[flannel.alpha.coreos.com/backend-data:{"VtepMAC":"22:df:da:84:9b:00"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:10.10.190.208 kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock nfd.node.kubernetes.io/extended-resources: nfd.node.kubernetes.io/feature-labels:cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-cpuid.AVX,cpu-cpuid.AVX2,cpu-cpuid.AVX512BW,cpu-cpuid.AVX512CD,cpu-cpuid.AVX512DQ,cpu-cpuid.AVX512F,cpu-cpuid.AVX512VL,cpu-cpuid.FMA3,cpu-cpuid.HLE,cpu-cpuid.IBPB,cpu-cpuid.MPX,cpu-cpuid.RTM,cpu-cpuid.STIBP,cpu-cpuid.VMX,cpu-hardware_multithreading,cpu-pstate.turbo,cpu-rdt.RDTCMT,cpu-rdt.RDTL3CA,cpu-rdt.RDTMBA,cpu-rdt.RDTMBM,cpu-rdt.RDTMON,kernel-config.NO_HZ,kernel-config.NO_HZ_FULL,kernel-selinux.enabled,kernel-version.full,kernel-version.major,kernel-version.minor,kernel-version.revision,memory-numa,network-sriov.capable,network-sriov.configured,pci-0300_1a03.present,storage-nonrotationaldisk,system-os_release.ID,system-os_release.VERSION_ID,system-os_release.VERSION_ID.major nfd.node.kubernetes.io/worker.version:v0.7.0 node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kube-controller-manager Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.244.4.0/24\"":{}}}}} {kubeadm Update v1 2021-05-07 20:01:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}}} {flanneld Update v1 2021-05-07 20:02:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:flannel.alpha.coreos.com/backend-data":{},"f:flannel.alpha.coreos.com/backend-type":{},"f:flannel.alpha.coreos.com/kube-subnet-manager":{},"f:flannel.alpha.coreos.com/public-ip":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {nfd-master Update v1 2021-05-07 20:08:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:nfd.node.kubernetes.io/extended-resources":{},"f:nfd.node.kubernetes.io/feature-labels":{},"f:nfd.node.kubernetes.io/worker.version":{}},"f:labels":{"f:feature.node.kubernetes.io/cpu-cpuid.ADX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AESNI":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX2":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512BW":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512CD":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512DQ":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512F":{},"f:feature.node.kubernetes.io/cpu-cpuid.AVX512VL":{},"f:feature.node.kubernetes.io/cpu-cpuid.FMA3":{},"f:feature.node.kubernetes.io/cpu-cpuid.HLE":{},"f:feature.node.kubernetes.io/cpu-cpuid.IBPB":{},"f:feature.node.kubernetes.io/cpu-cpuid.MPX":{},"f:feature.node.kubernetes.io/cpu-cpuid.RTM":{},"f:feature.node.kubernetes.io/cpu-cpuid.STIBP":{},"f:feature.node.kubernetes.io/cpu-cpuid.VMX":{},"f:feature.node.kubernetes.io/cpu-hardware_multithreading":{},"f:feature.node.kubernetes.io/cpu-pstate.turbo":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTCMT":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTL3CA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBA":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMBM":{},"f:feature.node.kubernetes.io/cpu-rdt.RDTMON":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ":{},"f:feature.node.kubernetes.io/kernel-config.NO_HZ_FULL":{},"f:feature.node.kubernetes.io/kernel-selinux.enabled":{},"f:feature.node.kubernetes.io/kernel-version.full":{},"f:feature.node.kubernetes.io/kernel-version.major":{},"f:feature.node.kubernetes.io/kernel-version.minor":{},"f:feature.node.kubernetes.io/kernel-version.revision":{},"f:feature.node.kubernetes.io/memory-numa":{},"f:feature.node.kubernetes.io/network-sriov.capable":{},"f:feature.node.kubernetes.io/network-sriov.configured":{},"f:feature.node.kubernetes.io/pci-0300_1a03.present":{},"f:feature.node.kubernetes.io/storage-nonrotationaldisk":{},"f:feature.node.kubernetes.io/system-os_release.ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID":{},"f:feature.node.kubernetes.io/system-os_release.VERSION_ID.major":{}}}}} {Swagger-Codegen Update v1 2021-05-07 20:11:31 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:cmk.intel.com/cmk-node":{}}},"f:status":{"f:capacity":{"f:cmk.intel.com/exclusive-cores":{}}}}} {kubelet Update v1 2021-05-07 22:47:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/os":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{}}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:cmk.intel.com/exclusive-cores":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:intel.com/intel_sriov_netdevice":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}}}]},Spec:NodeSpec{PodCIDR:10.244.4.0/24,DoNotUseExternalID:,ProviderID:,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.244.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{80 0} {} 80 DecimalSI},ephemeral-storage: {{450471260160 0} {} 439913340Ki BinarySI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{201269633024 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Allocatable:ResourceList{cmk.intel.com/exclusive-cores: {{3 0} {} 3 DecimalSI},cpu: {{77 0} {} 77 DecimalSI},ephemeral-storage: {{405424133473 0} {} 405424133473 DecimalSI},hugepages-1Gi: {{0 0} {} 0 DecimalSI},hugepages-2Mi: {{21474836480 0} {} 20Gi BinarySI},intel.com/intel_sriov_netdevice: {{4 0} {} 4 DecimalSI},memory: {{178884632576 0} {} BinarySI},pods: {{110 0} {} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-05-07 20:05:02 +0000 UTC,LastTransitionTime:2021-05-07 20:05:02 +0000 UTC,Reason:FlannelIsUp,Message:Flannel is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:46 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:46 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-05-07 22:52:46 +0000 UTC,LastTransitionTime:2021-05-07 20:01:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-05-07 22:52:46 +0000 UTC,LastTransitionTime:2021-05-07 20:02:07 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.10.190.208,},NodeAddress{Type:Hostname,Address:node2,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:6f56c5a750d0441dba0ffa6273fb1a17,SystemUUID:80B3CD56-852F-E711-906E-0017A4403562,BootID:98b263e9-3136-45ed-9b07-5f5b6b9d69b8,KernelVersion:3.10.0-1160.25.1.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://19.3.14,KubeletVersion:v1.19.8,KubeProxyVersion:v1.19.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[localhost:30500/barometer-collectd@sha256:facbba279b626f9254dfef1616802a1eadebffadd9d37bde82b5562163121c72 localhost:30500/barometer-collectd:stable],SizeBytes:1464089363,},ContainerImage{Names:[localhost:30500/cmk@sha256:9955df6c40f7a908013f9d77afdcd5df3df7f47ffb0eb09bbcb27d61112121ec localhost:30500/cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[cmk:v1.5.1],SizeBytes:726657349,},ContainerImage{Names:[centos/python-36-centos7@sha256:ac50754646f0d37616515fb30467d8743fb12954260ec36c9ecb5a94499447e0 centos/python-36-centos7:latest],SizeBytes:650061677,},ContainerImage{Names:[nfvpe/multus@sha256:ac1266b87ba44c09dc2a336f0d5dad968fccd389ce1944a85e87b32cd21f7224 nfvpe/multus:v3.4.2],SizeBytes:276587882,},ContainerImage{Names:[k8s.gcr.io/etcd@sha256:4ad90a11b55313b182afc186b9876c8e891531b8db4c9bf1541953021618d0e2 k8s.gcr.io/etcd:3.4.13-0],SizeBytes:253392289,},ContainerImage{Names:[kubernetesui/dashboard-amd64@sha256:3af248961c56916aeca8eb4000c15d6cf6a69641ea92f0540865bb37b495932f kubernetesui/dashboard-amd64:v2.1.0],SizeBytes:225733746,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/jessie-dnsutils@sha256:ad583e33cb284f7ef046673809b146ec4053cda19b54a85d2b180a86169715eb gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0],SizeBytes:195659796,},ContainerImage{Names:[nginx@sha256:75a55d33ecc73c2a242450a9f1cc858499d468f077ea942867e662c247b5e412 nginx:1.19],SizeBytes:133117205,},ContainerImage{Names:[httpd@sha256:eb8ccf084cf3e80eece1add239effefd171eb39adbc154d33c14260d905d4060 httpd:2.4.38-alpine],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:82e0ce4e1d08f3749d05c584fd60986197bfcdf9ce71d4666c71674221d53135 k8s.gcr.io/kube-apiserver:v1.19.8],SizeBytes:118813022,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:8ed30419d9cf8965854f9ed501159e15deb30c42c3d2a60a278ae169320d140e k8s.gcr.io/kube-proxy:v1.19.8],SizeBytes:117674285,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:17e61a0b9e498b6c73ed97670906be3d5a3ae394739c1bd5b619e1a004885cf0 k8s.gcr.io/e2e-test-images/agnhost:2.20],SizeBytes:113869866,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:2769005fb667dbb936009894d01fe35f5ce1bce45eee80a9ce3c139b9be4080e k8s.gcr.io/kube-controller-manager:v1.19.8],SizeBytes:110805342,},ContainerImage{Names:[gcr.io/k8s-staging-nfd/node-feature-discovery@sha256:5d116c2c340be665a2c8adc9aca7f91396bd5cbde4add4fdc8dab95d8db43425 gcr.io/k8s-staging-nfd/node-feature-discovery:v0.7.0],SizeBytes:108309584,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/sample-apiserver@sha256:ff02aacd9766d597883fabafc7ad604c719a57611db1bcc1564c69a45b000a55 gcr.io/kubernetes-e2e-test-images/sample-apiserver:1.17],SizeBytes:60684726,},ContainerImage{Names:[quay.io/coreos/flannel@sha256:34860ea294a018d392e61936f19a7862d5e92039d196cac9176da14b2bbd0fe3 quay.io/coreos/flannel@sha256:ac5322604bcab484955e6dbc507f45a906bde79046667322e3918a8578ab08c8 quay.io/coreos/flannel:v0.13.0 quay.io/coreos/flannel:v0.13.0-amd64],SizeBytes:57156911,},ContainerImage{Names:[quay.io/coreos/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b quay.io/coreos/kube-rbac-proxy:v0.5.0],SizeBytes:46626428,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:bb66135ce9a25ac405e43bbae6a2ac766e0efcac0a6a73ef9d1fbb4cf4732c9b k8s.gcr.io/kube-scheduler:v1.19.8],SizeBytes:46510430,},ContainerImage{Names:[localhost:30500/sriov-device-plugin@sha256:bae53f2ec899d23f9342d730c376a1ee3805e96fd1e5e4857e65085e6529557d localhost:30500/sriov-device-plugin:v3.3.1],SizeBytes:44392820,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonroot@sha256:4bd7ae247de5c988700233c5a4b55e804ffe90f8c66ae64853f1dae37b847213 gcr.io/kubernetes-e2e-test-images/nonroot:1.0],SizeBytes:42321438,},ContainerImage{Names:[quay.io/prometheus/node-exporter@sha256:a2f29256e53cc3e0b64d7a472512600b2e9410347d53cdc85b49f659c17e02ee quay.io/prometheus/node-exporter:v0.18.1],SizeBytes:22933477,},ContainerImage{Names:[localhost:30500/tas-controller@sha256:09461cf1b75776eb7d277a89d3a624c9eea355bf2ab1d8abbe45c40df99de268 localhost:30500/tas-controller:0.1],SizeBytes:22922439,},ContainerImage{Names:[localhost:30500/tas-extender@sha256:5b4ebd3c9985a2f36839e18a8b7c84e4d1deb89fa486247108510c71673efe12 localhost:30500/tas-extender:0.1],SizeBytes:21320903,},ContainerImage{Names:[prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654],SizeBytes:17463681,},ContainerImage{Names:[nginx@sha256:485b610fefec7ff6c463ced9623314a04ed67e3945b9c08d7e53a47f6d108dc7 nginx:1.14-alpine],SizeBytes:16032814,},ContainerImage{Names:[gcr.io/google-samples/hello-go-gke@sha256:4ea9cd3d35f81fc91bdebca3fae50c180a1048be0613ad0f811595365040396e gcr.io/google-samples/hello-go-gke:1.0],SizeBytes:11443478,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nonewprivs@sha256:10066e9039219449fe3c81f38fe01928f87914150768ab81b62a468e51fa7411 gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0],SizeBytes:6757579,},ContainerImage{Names:[gcr.io/kubernetes-e2e-test-images/nautilus@sha256:33a732d4c42a266912a5091598a0f07653c9134db4b8d571690d8afd509e0bfc gcr.io/kubernetes-e2e-test-images/nautilus:1.0],SizeBytes:4753501,},ContainerImage{Names:[busybox@sha256:8ccbac733d19c0dd4d70b4f0c1e12245b5fa3ad24758a11035ee505c629c0796 busybox:1.29],SizeBytes:1154361,},ContainerImage{Names:[busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 busybox:1.28],SizeBytes:1146369,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:682696,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:a319ac2280eb7e3a59e252e54b76327cb4a33cf8389053b0d78277f22bbca2fa k8s.gcr.io/pause:3.3],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} May 7 22:52:50.886: INFO: Logging kubelet events for node node2 May 7 22:52:50.888: INFO: Logging pods the kubelet thinks is on node node2 May 7 22:52:50.908: INFO: collectd-p5gbt started at 2021-05-07 20:18:33 +0000 UTC (0+3 container statuses recorded) May 7 22:52:50.908: INFO: Container collectd ready: true, restart count 0 May 7 22:52:50.908: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:52:50.908: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:52:50.908: INFO: cmk-webhook-6c9d5f8578-94s58 started at 2021-05-07 20:11:49 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.908: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:52:50.908: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z started at 2021-05-07 20:09:23 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.908: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:52:50.908: INFO: nginx-proxy-node2 started at 2021-05-07 20:07:46 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.908: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:52:50.908: INFO: kube-proxy-rgw7h started at 2021-05-07 20:01:27 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.908: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:52:50.908: INFO: node-exporter-4bcls started at 2021-05-07 20:12:42 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.908: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:52:50.908: INFO: Container node-exporter ready: true, restart count 0 May 7 22:52:50.908: INFO: node-feature-discovery-worker-wp5n6 started at 2021-05-07 20:08:19 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.908: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:52:50.908: INFO: kube-multus-ds-amd64-g98hm started at 2021-05-07 20:02:10 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.908: INFO: Container kube-multus ready: true, restart count 1 May 7 22:52:50.908: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f started at 2021-05-07 20:15:36 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.908: INFO: Container tas-controller ready: true, restart count 0 May 7 22:52:50.908: INFO: Container tas-extender ready: true, restart count 0 May 7 22:52:50.908: INFO: kube-flannel-htqkx started at 2021-05-07 20:02:02 +0000 UTC (1+1 container statuses recorded) May 7 22:52:50.908: INFO: Init container install-cni ready: true, restart count 2 May 7 22:52:50.908: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:52:50.908: INFO: cmk-init-discover-node2-kd9gg started at 2021-05-07 20:11:26 +0000 UTC (0+3 container statuses recorded) May 7 22:52:50.908: INFO: Container discover ready: false, restart count 0 May 7 22:52:50.908: INFO: Container init ready: false, restart count 0 May 7 22:52:50.908: INFO: Container install ready: false, restart count 0 May 7 22:52:50.908: INFO: cmk-gvh7j started at 2021-05-07 20:11:49 +0000 UTC (0+2 container statuses recorded) May 7 22:52:50.908: INFO: Container nodereport ready: true, restart count 0 May 7 22:52:50.908: INFO: Container reconcile ready: true, restart count 0 May 7 22:52:50.908: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 started at 2021-05-07 20:02:35 +0000 UTC (0+1 container statuses recorded) May 7 22:52:50.908: INFO: Container kubernetes-dashboard ready: true, restart count 1 W0507 22:52:50.919831 21 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled. May 7 22:52:50.960: INFO: Latency metrics for node node2 May 7 22:52:50.960: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-8954" for this suite. • Failure [302.999 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should retry creating failed daemon pods [Conformance] [It] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 May 7 22:52:48.033: error waiting for daemon pod to start Unexpected error: <*errors.errorString | 0xc0002fe1f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:291 ------------------------------ {"msg":"FAILED [sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]","total":17,"completed":10,"skipped":5060,"failed":5,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]","[sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:52:50.969: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename namespaces STEP: Waiting for a default service account to be provisioned in namespace [It] should ensure that all pods are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: Creating a test namespace STEP: Waiting for a default service account to be provisioned in namespace STEP: Creating a pod in the namespace STEP: Waiting for the pod to have running status STEP: Deleting the namespace STEP: Waiting for the namespace to be removed. STEP: Recreating the namespace STEP: Verifying there are no pods in the namespace [AfterEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:53:06.051: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "namespaces-8710" for this suite. STEP: Destroying namespace "nsdeletetest-3487" for this suite. May 7 22:53:06.060: INFO: Namespace nsdeletetest-3487 was already deleted STEP: Destroying namespace "nsdeletetest-6515" for this suite. • [SLOW TEST:15.098 seconds] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23 should ensure that all pods are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance]","total":17,"completed":11,"skipped":5095,"failed":5,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]","[sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 STEP: Creating a kubernetes client May 7 22:53:06.070: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 May 7 22:53:06.098: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready May 7 22:53:06.106: INFO: Waiting for terminating namespaces to be deleted... May 7 22:53:06.108: INFO: Logging pods the apiserver thinks is on node node1 before test May 7 22:53:06.115: INFO: cmk-gjhf2 from kube-system started at 2021-05-07 20:11:48 +0000 UTC (2 container statuses recorded) May 7 22:53:06.115: INFO: Container nodereport ready: true, restart count 0 May 7 22:53:06.115: INFO: Container reconcile ready: true, restart count 0 May 7 22:53:06.115: INFO: cmk-init-discover-node1-krbjn from kube-system started at 2021-05-07 20:11:05 +0000 UTC (3 container statuses recorded) May 7 22:53:06.115: INFO: Container discover ready: false, restart count 0 May 7 22:53:06.115: INFO: Container init ready: false, restart count 0 May 7 22:53:06.115: INFO: Container install ready: false, restart count 0 May 7 22:53:06.115: INFO: kube-flannel-qm7lv from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:53:06.115: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:53:06.115: INFO: kube-multus-ds-amd64-fxgdb from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:53:06.115: INFO: Container kube-multus ready: true, restart count 1 May 7 22:53:06.115: INFO: kube-proxy-bms7z from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:53:06.115: INFO: Container kube-proxy ready: true, restart count 2 May 7 22:53:06.115: INFO: kubernetes-metrics-scraper-678c97765c-g7srv from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:53:06.115: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 May 7 22:53:06.115: INFO: nginx-proxy-node1 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:53:06.115: INFO: Container nginx-proxy ready: true, restart count 1 May 7 22:53:06.115: INFO: node-feature-discovery-worker-xvbpd from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:53:06.115: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:53:06.115: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:53:06.115: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:53:06.115: INFO: collectd-tmjfs from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:53:06.115: INFO: Container collectd ready: true, restart count 0 May 7 22:53:06.115: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:53:06.115: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:53:06.115: INFO: node-exporter-mpq58 from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:53:06.115: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:53:06.115: INFO: Container node-exporter ready: true, restart count 0 May 7 22:53:06.115: INFO: prometheus-k8s-0 from monitoring started at 2021-05-07 20:12:50 +0000 UTC (5 container statuses recorded) May 7 22:53:06.115: INFO: Container custom-metrics-apiserver ready: true, restart count 0 May 7 22:53:06.115: INFO: Container grafana ready: true, restart count 0 May 7 22:53:06.115: INFO: Container prometheus ready: true, restart count 1 May 7 22:53:06.115: INFO: Container prometheus-config-reloader ready: true, restart count 0 May 7 22:53:06.115: INFO: Container rules-configmap-reloader ready: true, restart count 0 May 7 22:53:06.115: INFO: Logging pods the apiserver thinks is on node node2 before test May 7 22:53:06.124: INFO: cmk-gvh7j from kube-system started at 2021-05-07 20:11:49 +0000 UTC (2 container statuses recorded) May 7 22:53:06.124: INFO: Container nodereport ready: true, restart count 0 May 7 22:53:06.124: INFO: Container reconcile ready: true, restart count 0 May 7 22:53:06.124: INFO: cmk-init-discover-node2-kd9gg from kube-system started at 2021-05-07 20:11:26 +0000 UTC (3 container statuses recorded) May 7 22:53:06.124: INFO: Container discover ready: false, restart count 0 May 7 22:53:06.124: INFO: Container init ready: false, restart count 0 May 7 22:53:06.124: INFO: Container install ready: false, restart count 0 May 7 22:53:06.124: INFO: cmk-webhook-6c9d5f8578-94s58 from kube-system started at 2021-05-07 20:11:49 +0000 UTC (1 container statuses recorded) May 7 22:53:06.124: INFO: Container cmk-webhook ready: true, restart count 0 May 7 22:53:06.124: INFO: kube-flannel-htqkx from kube-system started at 2021-05-07 20:02:02 +0000 UTC (1 container statuses recorded) May 7 22:53:06.124: INFO: Container kube-flannel ready: true, restart count 2 May 7 22:53:06.124: INFO: kube-multus-ds-amd64-g98hm from kube-system started at 2021-05-07 20:02:10 +0000 UTC (1 container statuses recorded) May 7 22:53:06.124: INFO: Container kube-multus ready: true, restart count 1 May 7 22:53:06.124: INFO: kube-proxy-rgw7h from kube-system started at 2021-05-07 20:01:27 +0000 UTC (1 container statuses recorded) May 7 22:53:06.124: INFO: Container kube-proxy ready: true, restart count 1 May 7 22:53:06.124: INFO: kubernetes-dashboard-86c6f9df5b-k9cj2 from kube-system started at 2021-05-07 20:02:35 +0000 UTC (1 container statuses recorded) May 7 22:53:06.124: INFO: Container kubernetes-dashboard ready: true, restart count 1 May 7 22:53:06.124: INFO: nginx-proxy-node2 from kube-system started at 2021-05-07 20:07:46 +0000 UTC (1 container statuses recorded) May 7 22:53:06.124: INFO: Container nginx-proxy ready: true, restart count 2 May 7 22:53:06.124: INFO: node-feature-discovery-worker-wp5n6 from kube-system started at 2021-05-07 20:08:19 +0000 UTC (1 container statuses recorded) May 7 22:53:06.124: INFO: Container nfd-worker ready: true, restart count 0 May 7 22:53:06.124: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z from kube-system started at 2021-05-07 20:09:23 +0000 UTC (1 container statuses recorded) May 7 22:53:06.124: INFO: Container kube-sriovdp ready: true, restart count 0 May 7 22:53:06.124: INFO: collectd-p5gbt from monitoring started at 2021-05-07 20:18:33 +0000 UTC (3 container statuses recorded) May 7 22:53:06.124: INFO: Container collectd ready: true, restart count 0 May 7 22:53:06.124: INFO: Container collectd-exporter ready: true, restart count 0 May 7 22:53:06.124: INFO: Container rbac-proxy ready: true, restart count 0 May 7 22:53:06.124: INFO: node-exporter-4bcls from monitoring started at 2021-05-07 20:12:42 +0000 UTC (2 container statuses recorded) May 7 22:53:06.124: INFO: Container kube-rbac-proxy ready: true, restart count 0 May 7 22:53:06.124: INFO: Container node-exporter ready: true, restart count 0 May 7 22:53:06.124: INFO: tas-telemetry-aware-scheduling-575ccbc9d4-8z46f from monitoring started at 2021-05-07 20:15:36 +0000 UTC (2 container statuses recorded) May 7 22:53:06.124: INFO: Container tas-controller ready: true, restart count 0 May 7 22:53:06.124: INFO: Container tas-extender ready: true, restart count 0 [It] validates resource limits of pods that are allowed to run [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 STEP: verifying the node has the label node node1 STEP: verifying the node has the label node node2 May 7 22:53:06.174: INFO: Pod cmk-gjhf2 requesting resource cpu=0m on Node node1 May 7 22:53:06.174: INFO: Pod cmk-gvh7j requesting resource cpu=0m on Node node2 May 7 22:53:06.174: INFO: Pod cmk-webhook-6c9d5f8578-94s58 requesting resource cpu=0m on Node node2 May 7 22:53:06.174: INFO: Pod kube-flannel-htqkx requesting resource cpu=150m on Node node2 May 7 22:53:06.174: INFO: Pod kube-flannel-qm7lv requesting resource cpu=150m on Node node1 May 7 22:53:06.174: INFO: Pod kube-multus-ds-amd64-fxgdb requesting resource cpu=100m on Node node1 May 7 22:53:06.174: INFO: Pod kube-multus-ds-amd64-g98hm requesting resource cpu=100m on Node node2 May 7 22:53:06.174: INFO: Pod kube-proxy-bms7z requesting resource cpu=0m on Node node1 May 7 22:53:06.174: INFO: Pod kube-proxy-rgw7h requesting resource cpu=0m on Node node2 May 7 22:53:06.174: INFO: Pod kubernetes-dashboard-86c6f9df5b-k9cj2 requesting resource cpu=50m on Node node2 May 7 22:53:06.174: INFO: Pod kubernetes-metrics-scraper-678c97765c-g7srv requesting resource cpu=0m on Node node1 May 7 22:53:06.175: INFO: Pod nginx-proxy-node1 requesting resource cpu=25m on Node node1 May 7 22:53:06.175: INFO: Pod nginx-proxy-node2 requesting resource cpu=25m on Node node2 May 7 22:53:06.175: INFO: Pod node-feature-discovery-worker-wp5n6 requesting resource cpu=0m on Node node2 May 7 22:53:06.175: INFO: Pod node-feature-discovery-worker-xvbpd requesting resource cpu=0m on Node node1 May 7 22:53:06.175: INFO: Pod sriov-net-dp-kube-sriov-device-plugin-amd64-mq752 requesting resource cpu=0m on Node node1 May 7 22:53:06.175: INFO: Pod sriov-net-dp-kube-sriov-device-plugin-amd64-tkw8z requesting resource cpu=0m on Node node2 May 7 22:53:06.175: INFO: Pod collectd-p5gbt requesting resource cpu=0m on Node node2 May 7 22:53:06.175: INFO: Pod collectd-tmjfs requesting resource cpu=0m on Node node1 May 7 22:53:06.175: INFO: Pod node-exporter-4bcls requesting resource cpu=112m on Node node2 May 7 22:53:06.175: INFO: Pod node-exporter-mpq58 requesting resource cpu=112m on Node node1 May 7 22:53:06.175: INFO: Pod prometheus-k8s-0 requesting resource cpu=300m on Node node1 May 7 22:53:06.175: INFO: Pod tas-telemetry-aware-scheduling-575ccbc9d4-8z46f requesting resource cpu=0m on Node node2 STEP: Starting Pods to consume most of the cluster CPU. May 7 22:53:06.175: INFO: Creating a pod which consumes cpu=53419m on Node node1 May 7 22:53:06.187: INFO: Creating a pod which consumes cpu=53594m on Node node2 STEP: Creating another pod that requires unavailable amount of CPU. STEP: Considering event: Type = [Normal], Name = [filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42.167ceaab04bb1711], Reason = [Scheduled], Message = [Successfully assigned sched-pred-3096/filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42 to node1] STEP: Considering event: Type = [Normal], Name = [filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42.167ceaab61b52d98], Reason = [AddedInterface], Message = [Add eth0 [10.244.3.237/24]] STEP: Considering event: Type = [Normal], Name = [filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42.167ceaab6266a614], Reason = [Pulling], Message = [Pulling image "k8s.gcr.io/pause:3.2"] STEP: Considering event: Type = [Normal], Name = [filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42.167ceaab8192aebe], Reason = [Pulled], Message = [Successfully pulled image "k8s.gcr.io/pause:3.2" in 522.969734ms] STEP: Considering event: Type = [Normal], Name = [filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42.167ceaab8887c27d], Reason = [Created], Message = [Created container filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42] STEP: Considering event: Type = [Normal], Name = [filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42.167ceaab8f8e3845], Reason = [Started], Message = [Started container filler-pod-55a3edbd-a487-429b-a742-f3e2c3b3ca42] STEP: Considering event: Type = [Normal], Name = [filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded.167ceaab054bb09f], Reason = [Scheduled], Message = [Successfully assigned sched-pred-3096/filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded to node2] STEP: Considering event: Type = [Normal], Name = [filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded.167ceaab5837be36], Reason = [AddedInterface], Message = [Add eth0 [10.244.4.21/24]] STEP: Considering event: Type = [Normal], Name = [filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded.167ceaab5905378e], Reason = [Pulling], Message = [Pulling image "k8s.gcr.io/pause:3.2"] STEP: Considering event: Type = [Normal], Name = [filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded.167ceaab78ccf5d2], Reason = [Pulled], Message = [Successfully pulled image "k8s.gcr.io/pause:3.2" in 533.176671ms] STEP: Considering event: Type = [Normal], Name = [filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded.167ceaab80c5a9cb], Reason = [Created], Message = [Created container filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded] STEP: Considering event: Type = [Normal], Name = [filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded.167ceaab86cf9c74], Reason = [Started], Message = [Started container filler-pod-bee1619a-5627-4a4d-9a8c-24a1764ebded] STEP: Considering event: Type = [Warning], Name = [additional-pod.167ceaabf51ef485], Reason = [FailedScheduling], Message = [0/5 nodes are available: 2 Insufficient cpu, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.] STEP: Considering event: Type = [Warning], Name = [additional-pod.167ceaabf579c805], Reason = [FailedScheduling], Message = [0/5 nodes are available: 2 Insufficient cpu, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.] STEP: removing the label node off the node node1 STEP: verifying the node doesn't have the label node STEP: removing the label node off the node node2 STEP: verifying the node doesn't have the label node [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 May 7 22:53:11.251: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-3096" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 • [SLOW TEST:5.187 seconds] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates resource limits of pods that are allowed to run [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance]","total":17,"completed":12,"skipped":5303,"failed":5,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]","[sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]"]} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSMay 7 22:53:11.260: INFO: Running AfterSuite actions on all nodes May 7 22:53:11.260: INFO: Running AfterSuite actions on node 1 May 7 22:53:11.260: INFO: Skipping dumping logs from cluster JUnit report was created: /home/opnfv/functest/results/k8s_conformance_serial/junit_01.xml {"msg":"Test Suite completed","total":17,"completed":12,"skipped":5467,"failed":5,"failures":["[sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","[sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","[sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]","[sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]"]} Summarizing 5 Failures: [Fail] [sig-apps] Daemon set [Serial] [It] should run and stop complex daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:203 [Fail] [sig-apps] Daemon set [Serial] [It] should run and stop simple daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:163 [Fail] [sig-apps] Daemon set [Serial] [It] should update pod when spec was updated and update strategy is RollingUpdate [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:373 [Fail] [sig-apps] Daemon set [Serial] [It] should rollback without unnecessary restarts [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:433 [Fail] [sig-apps] Daemon set [Serial] [It] should retry creating failed daemon pods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:291 Ran 17 of 5484 Specs in 2237.620 seconds FAIL! -- 12 Passed | 5 Failed | 0 Pending | 5467 Skipped --- FAIL: TestE2E (2237.72s) FAIL Ginkgo ran 1 suite in 37m18.840050532s Test Suite Failed