PR #114764 pull-kubernetes-e2e-capz-conformance #1617440617816657920
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | claudiubelu: unittests: Fixes unit tests for Windows (part 7) |
| Result | FAILURE |
| Tests | 1 failed / 0 succeeded |
| Started | |
| Elapsed | 52m44s |
| Revision | d8b01e332c17d4c1fe4cbc9ef3928eaa5c93557d |
| Refs |
114764 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sConformance\sTests\sconformance\-tests$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99
Unexpected error:
<*errors.withStack | 0xc0029c47e0>: {
error: <*errors.withMessage | 0xc000450280>{
cause: <*errors.errorString | 0xc001a5e5c0>{
s: "error container run failed with exit code 1",
},
msg: "Unable to run conformance tests",
},
stack: [0x2ef56b8, 0x32ed787, 0x1878d97, 0x32ed553, 0x143a565, 0x1439a5c, 0x187a5fc, 0x187b611, 0x187b005, 0x187a69b, 0x1880929, 0x1880312, 0x188cc11, 0x188c936, 0x188bf85, 0x188e645, 0x189bea9, 0x189bcbe, 0x32f26f8, 0x148fccb, 0x13c7801],
}
Unable to run conformance tests: error container run failed with exit code 1
occurred
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:232
[BeforeEach] Conformance Tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:55
INFO: Cluster name is capz-conf-y1oqv9
�[1mSTEP�[0m: Creating namespace "capz-conf-y1oqv9" for hosting the cluster
Jan 23 09:05:34.279: INFO: starting to create namespace for hosting the "capz-conf-y1oqv9" test spec
INFO: Creating namespace capz-conf-y1oqv9
INFO: Creating event watcher for namespace "capz-conf-y1oqv9"
[Measure] conformance-tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99
INFO: Creating the workload cluster with name "capz-conf-y1oqv9" using the "conformance-presubmit-artifacts" template (Kubernetes v1.27.0-alpha.0.1196+724497cda467b7, 1 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster capz-conf-y1oqv9 --infrastructure (default) --kubernetes-version v1.27.0-alpha.0.1196+724497cda467b7 --control-plane-machine-count 1 --worker-machine-count 2 --flavor conformance-presubmit-artifacts
INFO: Applying the cluster template yaml to the cluster
INFO: Waiting for the cluster infrastructure to be provisioned
�[1mSTEP�[0m: Waiting for cluster to enter the provisioned phase
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by capz-conf-y1oqv9/capz-conf-y1oqv9-control-plane to be provisioned
�[1mSTEP�[0m: Waiting for one control plane node to exist
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane capz-conf-y1oqv9/capz-conf-y1oqv9-control-plane to be ready (implies underlying nodes to be ready as well)
�[1mSTEP�[0m: Waiting for the control plane to be ready
�[1mSTEP�[0m: Checking all the the control plane machines are in the expected failure domains
INFO: Waiting for the machine deployments to be provisioned
�[1mSTEP�[0m: Waiting for the workload nodes to exist
�[1mSTEP�[0m: Checking all the machines controlled by capz-conf-y1oqv9-md-0 are in the "<None>" failure domain
�[1mSTEP�[0m: Waiting for the workload nodes to exist
�[1mSTEP�[0m: Checking all the machines controlled by capz-conf-y1oqv9-md-win are in the "<None>" failure domain
INFO: Waiting for the machine pools to be provisioned
�[1mSTEP�[0m: Running e2e test: dir=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e, command=["-nodes=25" "-slowSpecThreshold=120" "/usr/local/bin/e2e.test" "--" "--provider=skeleton" "--report-dir=/output" "--e2e-output-dir=/output/e2e-output" "--dump-logs-on-failure=false" "--report-prefix=kubetest." "--num-nodes=2" "--kubeconfig=/tmp/kubeconfig" "-disable-log-dump=true" "-ginkgo.focus=\\[Conformance\\]" "-ginkgo.progress=true" "-ginkgo.skip=\\[Serial\\]" "-ginkgo.slow-spec-threshold=120s" "-ginkgo.timeout=3h" "-ginkgo.trace=true" "-ginkgo.v=true"]
Running Suite: Kubernetes e2e suite - /usr/local/bin
====================================================
Random Seed: �[1m1674465189�[0m - will randomize all specs
Will run �[1m344�[0m of �[1m7075�[0m specs
Running in parallel across �[1m25�[0m processes
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.347 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;243mTimeline >>�[0m
Jan 23 09:13:12.641: INFO: >>> kubeConfig: /tmp/kubeconfig
Jan 23 09:13:12.647: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Jan 23 09:13:12.975: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Jan 23 09:13:13.320: INFO: The status of Pod calico-node-vnrl7 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:13.320: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:13.320: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Jan 23 09:13:13.320: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:13.320: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:13.320: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }]
Jan 23 09:13:13.321: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:13.321: INFO:
Jan 23 09:13:15.559: INFO: The status of Pod calico-node-vnrl7 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:15.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:15.559: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Jan 23 09:13:15.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:15.559: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:15.559: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }]
Jan 23 09:13:15.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:15.559: INFO:
Jan 23 09:13:17.560: INFO: The status of Pod calico-node-vnrl7 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:17.560: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:17.560: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Jan 23 09:13:17.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:17.560: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:17.560: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }]
Jan 23 09:13:17.560: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:17.560: INFO:
Jan 23 09:13:19.552: INFO: The status of Pod calico-node-vnrl7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:19.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:19.552: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Jan 23 09:13:19.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:19.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:19.552: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }]
Jan 23 09:13:19.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:19.552: INFO:
Jan 23 09:13:21.550: INFO: The status of Pod calico-node-vnrl7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:21.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:21.550: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Jan 23 09:13:21.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:21.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:21.550: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }]
Jan 23 09:13:21.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:21.550: INFO:
Jan 23 09:13:23.551: INFO: The status of Pod calico-node-vnrl7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:23.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:23.551: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Jan 23 09:13:23.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:23.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:23.551: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }]
Jan 23 09:13:23.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:23.551: INFO:
Jan 23 09:13:25.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:25.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Jan 23 09:13:25.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:25.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:25.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:25.551: INFO:
Jan 23 09:13:27.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:27.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Jan 23 09:13:27.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:27.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:27.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:27.551: INFO:
Jan 23 09:13:29.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:29.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Jan 23 09:13:29.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:29.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:29.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:29.550: INFO:
Jan 23 09:13:31.560: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:31.560: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Jan 23 09:13:31.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:31.560: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:31.560: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:31.560: INFO:
Jan 23 09:13:33.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:33.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Jan 23 09:13:33.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:33.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:33.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:33.551: INFO:
Jan 23 09:13:35.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:35.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Jan 23 09:13:35.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:35.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:35.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:35.550: INFO:
Jan 23 09:13:37.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:37.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Jan 23 09:13:37.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:37.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:37.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:37.553: INFO:
Jan 23 09:13:39.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:39.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Jan 23 09:13:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:39.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:39.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:39.550: INFO:
Jan 23 09:13:41.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:41.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Jan 23 09:13:41.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:41.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:41.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:41.550: INFO:
Jan 23 09:13:43.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:43.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Jan 23 09:13:43.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:43.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:43.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:43.550: INFO:
Jan 23 09:13:45.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:45.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Jan 23 09:13:45.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:45.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:45.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:45.554: INFO:
Jan 23 09:13:47.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:47.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Jan 23 09:13:47.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:47.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:47.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:47.551: INFO:
Jan 23 09:13:49.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:49.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Jan 23 09:13:49.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:49.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:49.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:49.551: INFO:
Jan 23 09:13:51.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:51.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Jan 23 09:13:51.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:51.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:51.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:51.551: INFO:
Jan 23 09:13:53.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:53.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Jan 23 09:13:53.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:53.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:53.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:53.551: INFO:
Jan 23 09:13:55.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:55.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Jan 23 09:13:55.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:55.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:55.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:55.552: INFO:
Jan 23 09:13:57.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:57.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Jan 23 09:13:57.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:57.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:57.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:57.549: INFO:
Jan 23 09:13:59.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:13:59.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Jan 23 09:13:59.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:13:59.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:13:59.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:13:59.551: INFO:
Jan 23 09:14:01.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:01.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Jan 23 09:14:01.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:01.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:01.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:01.550: INFO:
Jan 23 09:14:03.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:03.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Jan 23 09:14:03.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:03.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:03.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:03.550: INFO:
Jan 23 09:14:05.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:05.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Jan 23 09:14:05.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:05.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:05.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:05.550: INFO:
Jan 23 09:14:07.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:07.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Jan 23 09:14:07.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:07.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:07.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:07.550: INFO:
Jan 23 09:14:09.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:09.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Jan 23 09:14:09.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:09.558: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:09.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:09.558: INFO:
Jan 23 09:14:11.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:11.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Jan 23 09:14:11.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:11.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:11.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:11.556: INFO:
Jan 23 09:14:13.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:13.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Jan 23 09:14:13.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:13.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:13.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:13.552: INFO:
Jan 23 09:14:15.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:15.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Jan 23 09:14:15.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:15.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:15.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:15.549: INFO:
Jan 23 09:14:17.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:17.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Jan 23 09:14:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:17.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:17.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:17.550: INFO:
Jan 23 09:14:19.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:19.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Jan 23 09:14:19.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:19.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:19.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:19.555: INFO:
Jan 23 09:14:21.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:21.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Jan 23 09:14:21.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:21.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:21.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:21.549: INFO:
Jan 23 09:14:23.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:23.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Jan 23 09:14:23.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:23.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:23.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:23.551: INFO:
Jan 23 09:14:25.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:25.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Jan 23 09:14:25.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:25.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:25.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:25.553: INFO:
Jan 23 09:14:27.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:27.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Jan 23 09:14:27.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:27.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:27.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:27.550: INFO:
Jan 23 09:14:29.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:29.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Jan 23 09:14:29.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:29.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:29.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:29.551: INFO:
Jan 23 09:14:31.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:31.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Jan 23 09:14:31.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:31.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:31.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:31.550: INFO:
Jan 23 09:14:33.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:33.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Jan 23 09:14:33.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:33.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:33.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:33.551: INFO:
Jan 23 09:14:35.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:35.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Jan 23 09:14:35.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:35.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:35.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:35.552: INFO:
Jan 23 09:14:37.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:37.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Jan 23 09:14:37.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:37.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:37.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:37.549: INFO:
Jan 23 09:14:39.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:39.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Jan 23 09:14:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:39.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:39.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:39.550: INFO:
Jan 23 09:14:41.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:41.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Jan 23 09:14:41.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:41.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:41.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:41.551: INFO:
Jan 23 09:14:43.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:43.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Jan 23 09:14:43.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:43.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:43.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:43.549: INFO:
Jan 23 09:14:45.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:45.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Jan 23 09:14:45.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:45.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:45.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:45.556: INFO:
Jan 23 09:14:47.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:47.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Jan 23 09:14:47.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:47.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:47.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:47.550: INFO:
Jan 23 09:14:49.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:49.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Jan 23 09:14:49.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:49.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:49.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:49.552: INFO:
Jan 23 09:14:51.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:51.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Jan 23 09:14:51.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:51.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:51.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:51.551: INFO:
Jan 23 09:14:53.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:53.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Jan 23 09:14:53.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:53.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:53.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:53.555: INFO:
Jan 23 09:14:55.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:55.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Jan 23 09:14:55.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:55.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:55.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:55.551: INFO:
Jan 23 09:14:57.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:57.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Jan 23 09:14:57.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:57.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:57.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:57.549: INFO:
Jan 23 09:14:59.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:14:59.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Jan 23 09:14:59.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:14:59.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:14:59.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:14:59.549: INFO:
Jan 23 09:15:01.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:01.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Jan 23 09:15:01.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:01.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:01.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:01.552: INFO:
Jan 23 09:15:03.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:03.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Jan 23 09:15:03.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:03.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:03.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:03.550: INFO:
Jan 23 09:15:05.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:05.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Jan 23 09:15:05.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:05.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:05.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:05.557: INFO:
Jan 23 09:15:07.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:07.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Jan 23 09:15:07.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:07.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:07.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:07.549: INFO:
Jan 23 09:15:09.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:09.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Jan 23 09:15:09.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:09.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:09.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:09.550: INFO:
Jan 23 09:15:11.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:11.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Jan 23 09:15:11.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:11.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:11.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:11.553: INFO:
Jan 23 09:15:13.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:13.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Jan 23 09:15:13.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:13.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:13.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:13.550: INFO:
Jan 23 09:15:15.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:15.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Jan 23 09:15:15.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:15.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:15.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:15.551: INFO:
Jan 23 09:15:17.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:17.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Jan 23 09:15:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:17.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:17.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:17.550: INFO:
Jan 23 09:15:19.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:19.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Jan 23 09:15:19.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:19.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:19.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:19.549: INFO:
Jan 23 09:15:21.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:21.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Jan 23 09:15:21.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:21.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:21.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:21.552: INFO:
Jan 23 09:15:23.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:23.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Jan 23 09:15:23.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:23.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:23.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:23.551: INFO:
Jan 23 09:15:25.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:25.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Jan 23 09:15:25.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:25.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:25.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:25.549: INFO:
Jan 23 09:15:27.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:27.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Jan 23 09:15:27.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:27.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:27.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:27.549: INFO:
Jan 23 09:15:29.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:29.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Jan 23 09:15:29.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:29.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:29.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:29.549: INFO:
Jan 23 09:15:31.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:31.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Jan 23 09:15:31.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:31.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:31.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:31.552: INFO:
Jan 23 09:15:33.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:33.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Jan 23 09:15:33.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:33.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:33.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:33.551: INFO:
Jan 23 09:15:35.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:35.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Jan 23 09:15:35.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:35.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:35.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:35.551: INFO:
Jan 23 09:15:37.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:37.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Jan 23 09:15:37.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:37.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:37.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:37.549: INFO:
Jan 23 09:15:39.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:39.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Jan 23 09:15:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:39.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:39.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:39.550: INFO:
Jan 23 09:15:41.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:41.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Jan 23 09:15:41.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:41.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:41.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:41.549: INFO:
Jan 23 09:15:43.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:43.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Jan 23 09:15:43.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:43.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:43.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:43.549: INFO:
Jan 23 09:15:45.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:45.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Jan 23 09:15:45.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:45.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:45.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:45.549: INFO:
Jan 23 09:15:47.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:47.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Jan 23 09:15:47.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:47.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:47.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:47.550: INFO:
Jan 23 09:15:49.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:49.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Jan 23 09:15:49.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:49.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:49.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:49.553: INFO:
Jan 23 09:15:51.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:51.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Jan 23 09:15:51.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:51.559: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:51.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:51.559: INFO:
Jan 23 09:15:53.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:53.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Jan 23 09:15:53.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:53.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:53.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:53.549: INFO:
Jan 23 09:15:55.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:55.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Jan 23 09:15:55.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:55.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:55.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:55.549: INFO:
Jan 23 09:15:57.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:57.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Jan 23 09:15:57.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:57.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:57.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:57.555: INFO:
Jan 23 09:15:59.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:15:59.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Jan 23 09:15:59.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:15:59.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:15:59.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:15:59.551: INFO:
Jan 23 09:16:01.786: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:01.786: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Jan 23 09:16:01.786: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:01.786: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:01.786: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:01.786: INFO:
Jan 23 09:16:03.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:03.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Jan 23 09:16:03.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:03.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:03.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:03.549: INFO:
Jan 23 09:16:05.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:05.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Jan 23 09:16:05.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:05.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:05.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:05.550: INFO:
Jan 23 09:16:07.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:07.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Jan 23 09:16:07.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:07.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:07.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:07.550: INFO:
Jan 23 09:16:09.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:09.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Jan 23 09:16:09.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:09.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:09.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:09.550: INFO:
Jan 23 09:16:11.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:11.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Jan 23 09:16:11.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:11.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:11.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:11.551: INFO:
Jan 23 09:16:13.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:13.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Jan 23 09:16:13.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:13.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:13.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:13.551: INFO:
Jan 23 09:16:15.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:15.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Jan 23 09:16:15.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:15.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:15.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:15.551: INFO:
Jan 23 09:16:17.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:17.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Jan 23 09:16:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:17.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:17.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:17.550: INFO:
Jan 23 09:16:19.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:19.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Jan 23 09:16:19.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:19.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:19.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:19.553: INFO:
Jan 23 09:16:21.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:21.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Jan 23 09:16:21.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:21.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:21.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:21.557: INFO:
Jan 23 09:16:23.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:23.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Jan 23 09:16:23.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:23.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:23.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:23.550: INFO:
Jan 23 09:16:25.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:25.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Jan 23 09:16:25.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:25.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:25.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:25.550: INFO:
Jan 23 09:16:27.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:27.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Jan 23 09:16:27.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:27.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:27.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:27.550: INFO:
Jan 23 09:16:29.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:29.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Jan 23 09:16:29.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:29.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:29.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:29.551: INFO:
Jan 23 09:16:31.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:31.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Jan 23 09:16:31.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:31.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:31.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:31.552: INFO:
Jan 23 09:16:33.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:33.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Jan 23 09:16:33.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:33.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:33.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:33.555: INFO:
Jan 23 09:16:35.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:35.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Jan 23 09:16:35.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:35.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:35.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:35.553: INFO:
Jan 23 09:16:37.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:37.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Jan 23 09:16:37.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:37.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:37.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:37.554: INFO:
Jan 23 09:16:39.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:39.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Jan 23 09:16:39.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:39.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:39.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:39.549: INFO:
Jan 23 09:16:41.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:41.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Jan 23 09:16:41.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:41.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:41.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:41.549: INFO:
Jan 23 09:16:43.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:43.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Jan 23 09:16:43.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:43.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:43.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:43.550: INFO:
Jan 23 09:16:45.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:45.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Jan 23 09:16:45.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:45.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:45.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:45.551: INFO:
Jan 23 09:16:47.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:47.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Jan 23 09:16:47.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:47.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:47.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:47.550: INFO:
Jan 23 09:16:49.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:49.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Jan 23 09:16:49.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:49.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:49.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:49.550: INFO:
Jan 23 09:16:51.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:51.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Jan 23 09:16:51.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:51.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:51.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:51.552: INFO:
Jan 23 09:16:53.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:53.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Jan 23 09:16:53.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:53.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:53.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:53.550: INFO:
Jan 23 09:16:55.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:55.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Jan 23 09:16:55.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:55.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:55.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:55.549: INFO:
Jan 23 09:16:57.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:57.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Jan 23 09:16:57.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:57.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:57.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:57.550: INFO:
Jan 23 09:16:59.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:16:59.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Jan 23 09:16:59.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:16:59.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:16:59.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:16:59.555: INFO:
Jan 23 09:17:01.576: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:01.576: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Jan 23 09:17:01.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:01.576: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:01.576: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:01.576: INFO:
Jan 23 09:17:03.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:03.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Jan 23 09:17:03.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:03.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:03.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:03.551: INFO:
Jan 23 09:17:05.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:05.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Jan 23 09:17:05.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:05.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:05.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:05.549: INFO:
Jan 23 09:17:07.569: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:07.569: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Jan 23 09:17:07.569: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:07.569: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:07.569: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:07.569: INFO:
Jan 23 09:17:09.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:09.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Jan 23 09:17:09.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:09.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:09.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:09.549: INFO:
Jan 23 09:17:11.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:11.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Jan 23 09:17:11.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:11.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:11.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:11.550: INFO:
Jan 23 09:17:13.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:13.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Jan 23 09:17:13.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:13.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:13.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:13.551: INFO:
Jan 23 09:17:15.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:15.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Jan 23 09:17:15.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:15.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:15.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:15.549: INFO:
Jan 23 09:17:17.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:17.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Jan 23 09:17:17.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:17.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:17.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:17.552: INFO:
Jan 23 09:17:19.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:19.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Jan 23 09:17:19.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:19.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:19.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:19.551: INFO:
Jan 23 09:17:21.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:21.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Jan 23 09:17:21.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:21.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:21.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:21.551: INFO:
Jan 23 09:17:23.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:23.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Jan 23 09:17:23.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:23.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:23.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:23.549: INFO:
Jan 23 09:17:25.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:25.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Jan 23 09:17:25.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:25.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:25.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:25.550: INFO:
Jan 23 09:17:27.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:27.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Jan 23 09:17:27.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:27.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:27.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:27.550: INFO:
Jan 23 09:17:29.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:29.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Jan 23 09:17:29.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:29.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:29.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:29.549: INFO:
Jan 23 09:17:31.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:31.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Jan 23 09:17:31.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:31.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:31.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:31.556: INFO:
Jan 23 09:17:33.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:33.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Jan 23 09:17:33.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:33.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:33.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:33.551: INFO:
Jan 23 09:17:35.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:35.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Jan 23 09:17:35.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:35.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:35.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:35.551: INFO:
Jan 23 09:17:37.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:37.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Jan 23 09:17:37.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:37.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:37.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:37.550: INFO:
Jan 23 09:17:39.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:39.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Jan 23 09:17:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:39.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:39.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:39.550: INFO:
Jan 23 09:17:41.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:41.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Jan 23 09:17:41.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:41.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:41.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:41.553: INFO:
Jan 23 09:17:43.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:43.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Jan 23 09:17:43.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:43.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:43.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:43.551: INFO:
Jan 23 09:17:45.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:45.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Jan 23 09:17:45.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:45.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:45.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:45.553: INFO:
Jan 23 09:17:47.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:47.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Jan 23 09:17:47.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:47.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:47.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:47.552: INFO:
Jan 23 09:17:49.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:49.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Jan 23 09:17:49.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:49.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:49.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:49.551: INFO:
Jan 23 09:17:51.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:51.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Jan 23 09:17:51.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:51.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:51.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:51.553: INFO:
Jan 23 09:17:53.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:53.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Jan 23 09:17:53.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:53.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:53.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:53.552: INFO:
Jan 23 09:17:55.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:55.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Jan 23 09:17:55.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:55.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:55.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:55.554: INFO:
Jan 23 09:17:57.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:57.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Jan 23 09:17:57.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:57.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:57.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:57.554: INFO:
Jan 23 09:17:59.548: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:17:59.548: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Jan 23 09:17:59.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:17:59.548: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:17:59.548: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:17:59.548: INFO:
Jan 23 09:18:01.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:01.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Jan 23 09:18:01.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:01.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:01.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:01.550: INFO:
Jan 23 09:18:03.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:03.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Jan 23 09:18:03.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:03.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:03.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:03.550: INFO:
Jan 23 09:18:05.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:05.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Jan 23 09:18:05.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:05.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:05.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:05.549: INFO:
Jan 23 09:18:07.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:07.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Jan 23 09:18:07.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:07.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:07.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:07.556: INFO:
Jan 23 09:18:09.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:09.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Jan 23 09:18:09.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:09.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:09.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:09.555: INFO:
Jan 23 09:18:11.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:11.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Jan 23 09:18:11.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:11.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:11.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:11.554: INFO:
Jan 23 09:18:13.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:13.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Jan 23 09:18:13.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:13.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:13.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:13.549: INFO:
Jan 23 09:18:15.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:15.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Jan 23 09:18:15.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:15.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:15.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:15.550: INFO:
Jan 23 09:18:17.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:17.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Jan 23 09:18:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:17.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:17.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:17.550: INFO:
Jan 23 09:18:19.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:19.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Jan 23 09:18:19.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:19.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:19.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:19.550: INFO:
Jan 23 09:18:21.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:21.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Jan 23 09:18:21.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:21.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:21.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:21.551: INFO:
Jan 23 09:18:23.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:23.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Jan 23 09:18:23.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:23.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:23.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:23.555: INFO:
Jan 23 09:18:25.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:25.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Jan 23 09:18:25.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:25.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:25.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:25.551: INFO:
Jan 23 09:18:27.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:27.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Jan 23 09:18:27.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:27.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:27.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:27.549: INFO:
Jan 23 09:18:29.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:29.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Jan 23 09:18:29.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:29.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:29.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:29.551: INFO:
Jan 23 09:18:31.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:31.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Jan 23 09:18:31.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:31.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:31.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:31.551: INFO:
Jan 23 09:18:33.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:33.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Jan 23 09:18:33.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:33.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:33.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:33.550: INFO:
Jan 23 09:18:35.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:35.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Jan 23 09:18:35.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:35.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:35.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:35.551: INFO:
Jan 23 09:18:37.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:37.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Jan 23 09:18:37.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:37.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:37.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:37.550: INFO:
Jan 23 09:18:39.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:39.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Jan 23 09:18:39.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:39.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:39.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:39.551: INFO:
Jan 23 09:18:41.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:41.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Jan 23 09:18:41.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:41.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:41.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:41.550: INFO:
Jan 23 09:18:43.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:43.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Jan 23 09:18:43.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:43.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:43.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:43.551: INFO:
Jan 23 09:18:45.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:45.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Jan 23 09:18:45.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:45.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:45.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:45.550: INFO:
Jan 23 09:18:47.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:47.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Jan 23 09:18:47.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:47.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:47.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:47.549: INFO:
Jan 23 09:18:49.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:49.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Jan 23 09:18:49.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:49.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:49.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:49.551: INFO:
Jan 23 09:18:51.564: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:51.564: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Jan 23 09:18:51.564: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:51.564: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:51.564: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:51.564: INFO:
Jan 23 09:18:53.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:53.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Jan 23 09:18:53.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:53.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:53.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:53.550: INFO:
Jan 23 09:18:55.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:55.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Jan 23 09:18:55.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:55.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:55.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:55.549: INFO:
Jan 23 09:18:57.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:57.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Jan 23 09:18:57.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:57.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:57.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:57.549: INFO:
Jan 23 09:18:59.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:18:59.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Jan 23 09:18:59.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:18:59.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:18:59.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:18:59.549: INFO:
Jan 23 09:19:01.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:01.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Jan 23 09:19:01.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:01.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:01.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:01.551: INFO:
Jan 23 09:19:03.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:03.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Jan 23 09:19:03.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:03.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:03.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:03.550: INFO:
Jan 23 09:19:05.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:05.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Jan 23 09:19:05.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:05.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:05.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:05.549: INFO:
Jan 23 09:19:07.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:07.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Jan 23 09:19:07.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:07.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:07.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:07.552: INFO:
Jan 23 09:19:09.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:09.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Jan 23 09:19:09.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:09.559: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:09.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:09.559: INFO:
Jan 23 09:19:11.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:11.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Jan 23 09:19:11.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:11.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:11.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:11.550: INFO:
Jan 23 09:19:13.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:13.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Jan 23 09:19:13.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:13.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:13.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:13.550: INFO:
Jan 23 09:19:15.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:15.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Jan 23 09:19:15.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:15.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:15.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:15.552: INFO:
Jan 23 09:19:17.548: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:17.548: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Jan 23 09:19:17.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:17.548: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:17.548: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:17.548: INFO:
Jan 23 09:19:19.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:19.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Jan 23 09:19:19.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:19.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:19.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:19.550: INFO:
Jan 23 09:19:21.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:21.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Jan 23 09:19:21.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:21.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:21.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:21.552: INFO:
Jan 23 09:19:23.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:23.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Jan 23 09:19:23.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:23.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:23.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:23.550: INFO:
Jan 23 09:19:25.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:25.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Jan 23 09:19:25.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:25.549: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:25.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:25.549: INFO:
Jan 23 09:19:27.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:27.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Jan 23 09:19:27.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:27.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:27.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:27.554: INFO:
Jan 23 09:19:29.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:29.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Jan 23 09:19:29.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:29.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:29.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:29.556: INFO:
Jan 23 09:19:31.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:31.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Jan 23 09:19:31.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:31.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:31.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:31.557: INFO:
Jan 23 09:19:33.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:33.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Jan 23 09:19:33.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:33.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:33.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:33.552: INFO:
Jan 23 09:19:35.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:35.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Jan 23 09:19:35.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:35.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:35.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:35.552: INFO:
Jan 23 09:19:37.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:37.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Jan 23 09:19:37.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:37.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:37.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:37.552: INFO:
Jan 23 09:19:39.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:39.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Jan 23 09:19:39.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:39.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:39.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:39.554: INFO:
Jan 23 09:19:41.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:41.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Jan 23 09:19:41.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:41.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:41.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:41.557: INFO:
Jan 23 09:19:43.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:43.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Jan 23 09:19:43.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:43.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:43.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:43.557: INFO:
Jan 23 09:19:45.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:45.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Jan 23 09:19:45.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:45.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:45.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:45.556: INFO:
Jan 23 09:19:47.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:47.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Jan 23 09:19:47.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:47.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:47.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:47.553: INFO:
Jan 23 09:19:49.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:49.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Jan 23 09:19:49.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:49.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:49.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:49.557: INFO:
Jan 23 09:19:51.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:51.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Jan 23 09:19:51.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:51.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:51.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:51.557: INFO:
Jan 23 09:19:53.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:53.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Jan 23 09:19:53.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:53.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:53.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:53.557: INFO:
Jan 23 09:19:55.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:55.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Jan 23 09:19:55.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:55.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:55.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:55.554: INFO:
Jan 23 09:19:57.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:57.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Jan 23 09:19:57.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:57.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:57.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:57.553: INFO:
Jan 23 09:19:59.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:19:59.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Jan 23 09:19:59.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:19:59.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:19:59.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:19:59.555: INFO:
Jan 23 09:20:01.565: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:01.565: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Jan 23 09:20:01.565: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:01.565: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:01.565: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:01.565: INFO:
Jan 23 09:20:03.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:03.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Jan 23 09:20:03.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:03.561: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:03.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:03.561: INFO:
Jan 23 09:20:05.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:05.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Jan 23 09:20:05.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:05.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:05.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:05.555: INFO:
Jan 23 09:20:07.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:07.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Jan 23 09:20:07.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:07.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:07.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:07.556: INFO:
Jan 23 09:20:09.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:09.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Jan 23 09:20:09.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:09.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:09.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:09.553: INFO:
Jan 23 09:20:11.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:11.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Jan 23 09:20:11.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:11.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:11.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:11.555: INFO:
Jan 23 09:20:13.562: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:13.562: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Jan 23 09:20:13.562: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:13.562: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:13.562: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:13.562: INFO:
Jan 23 09:20:15.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:15.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Jan 23 09:20:15.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:15.558: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:15.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:15.558: INFO:
Jan 23 09:20:17.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:17.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Jan 23 09:20:17.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:17.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:17.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:17.555: INFO:
Jan 23 09:20:19.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:19.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Jan 23 09:20:19.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:19.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:19.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:19.557: INFO:
Jan 23 09:20:21.564: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:21.564: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Jan 23 09:20:21.564: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:21.564: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:21.564: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:21.564: INFO:
Jan 23 09:20:23.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:23.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Jan 23 09:20:23.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:23.561: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:23.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:23.561: INFO:
Jan 23 09:20:25.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:25.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Jan 23 09:20:25.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:25.558: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:25.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:25.558: INFO:
Jan 23 09:20:27.560: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:27.560: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Jan 23 09:20:27.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:27.560: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:27.560: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:27.560: INFO:
Jan 23 09:20:29.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:29.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Jan 23 09:20:29.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:29.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:29.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:29.556: INFO:
Jan 23 09:20:31.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:31.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Jan 23 09:20:31.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:31.559: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:31.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:31.559: INFO:
Jan 23 09:20:33.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:33.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Jan 23 09:20:33.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:33.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:33.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:33.556: INFO:
Jan 23 09:20:35.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:35.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Jan 23 09:20:35.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:35.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:35.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:35.554: INFO:
Jan 23 09:20:37.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:37.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Jan 23 09:20:37.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:37.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:37.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:37.555: INFO:
Jan 23 09:20:39.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:39.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Jan 23 09:20:39.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:39.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:39.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:39.556: INFO:
Jan 23 09:20:41.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:41.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Jan 23 09:20:41.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:41.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:41.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:41.555: INFO:
Jan 23 09:20:43.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:43.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Jan 23 09:20:43.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:43.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:43.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:43.553: INFO:
Jan 23 09:20:45.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:45.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Jan 23 09:20:45.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:45.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:45.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:45.554: INFO:
Jan 23 09:20:47.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:47.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Jan 23 09:20:47.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:47.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:47.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:47.553: INFO:
Jan 23 09:20:49.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:49.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Jan 23 09:20:49.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:49.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:49.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:49.555: INFO:
Jan 23 09:20:51.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:51.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Jan 23 09:20:51.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:51.561: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:51.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:51.561: INFO:
Jan 23 09:20:53.569: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:53.569: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Jan 23 09:20:53.569: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:53.569: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:53.569: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:53.569: INFO:
Jan 23 09:20:55.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:55.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Jan 23 09:20:55.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:55.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:55.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:55.557: INFO:
Jan 23 09:20:57.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:57.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Jan 23 09:20:57.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:57.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:57.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:57.557: INFO:
Jan 23 09:20:59.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:20:59.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Jan 23 09:20:59.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:20:59.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:20:59.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:20:59.553: INFO:
Jan 23 09:21:01.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:01.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Jan 23 09:21:01.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:01.558: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:01.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:01.558: INFO:
Jan 23 09:21:03.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:03.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Jan 23 09:21:03.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:03.561: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:03.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:03.561: INFO:
Jan 23 09:21:05.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:05.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Jan 23 09:21:05.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:05.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:05.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:05.553: INFO:
Jan 23 09:21:07.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:07.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Jan 23 09:21:07.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:07.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:07.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:07.553: INFO:
Jan 23 09:21:09.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:09.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Jan 23 09:21:09.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:09.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:09.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:09.555: INFO:
Jan 23 09:21:11.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:11.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Jan 23 09:21:11.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:11.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:11.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:11.556: INFO:
Jan 23 09:21:13.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:13.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Jan 23 09:21:13.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:13.559: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:13.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:13.559: INFO:
Jan 23 09:21:15.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:15.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Jan 23 09:21:15.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:15.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:15.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:15.556: INFO:
Jan 23 09:21:17.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:17.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Jan 23 09:21:17.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:17.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:17.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:17.554: INFO:
Jan 23 09:21:19.563: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:19.563: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Jan 23 09:21:19.563: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:19.563: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:19.563: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:19.563: INFO:
Jan 23 09:21:21.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:21.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Jan 23 09:21:21.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:21.561: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:21.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:21.561: INFO:
Jan 23 09:21:23.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:23.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Jan 23 09:21:23.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:23.558: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:23.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:23.558: INFO:
Jan 23 09:21:25.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:25.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Jan 23 09:21:25.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:25.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:25.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:25.553: INFO:
Jan 23 09:21:27.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:27.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Jan 23 09:21:27.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:27.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:27.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:27.553: INFO:
Jan 23 09:21:29.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:29.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Jan 23 09:21:29.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:29.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:29.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:29.551: INFO:
Jan 23 09:21:31.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:31.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Jan 23 09:21:31.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:31.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:31.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:31.553: INFO:
Jan 23 09:21:33.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:33.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Jan 23 09:21:33.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:33.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:33.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:33.556: INFO:
Jan 23 09:21:35.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:35.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Jan 23 09:21:35.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:35.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:35.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:35.554: INFO:
Jan 23 09:21:37.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:37.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Jan 23 09:21:37.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:37.558: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:37.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:37.558: INFO:
Jan 23 09:21:39.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:39.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Jan 23 09:21:39.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:39.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:39.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:39.554: INFO:
Jan 23 09:21:41.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:41.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Jan 23 09:21:41.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:41.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:41.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:41.553: INFO:
Jan 23 09:21:43.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:43.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Jan 23 09:21:43.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:43.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:43.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:43.556: INFO:
Jan 23 09:21:45.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:45.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Jan 23 09:21:45.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:45.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:45.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:45.557: INFO:
Jan 23 09:21:47.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:47.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Jan 23 09:21:47.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:47.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:47.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:47.552: INFO:
Jan 23 09:21:49.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:49.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Jan 23 09:21:49.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:49.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:49.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:49.554: INFO:
Jan 23 09:21:51.560: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:51.560: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Jan 23 09:21:51.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:51.560: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:51.560: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:51.560: INFO:
Jan 23 09:21:53.562: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:53.562: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Jan 23 09:21:53.562: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:53.562: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:53.562: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:53.562: INFO:
Jan 23 09:21:55.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:55.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Jan 23 09:21:55.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:55.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:55.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:55.558: INFO:
Jan 23 09:21:57.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:57.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Jan 23 09:21:57.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:57.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:57.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:57.552: INFO:
Jan 23 09:21:59.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:21:59.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Jan 23 09:21:59.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:21:59.552: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:21:59.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:21:59.552: INFO:
Jan 23 09:22:01.563: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:01.563: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Jan 23 09:22:01.563: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:01.563: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:01.563: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:01.563: INFO:
Jan 23 09:22:03.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:03.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Jan 23 09:22:03.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:03.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:03.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:03.556: INFO:
Jan 23 09:22:05.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:05.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Jan 23 09:22:05.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:05.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:05.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:05.555: INFO:
Jan 23 09:22:07.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:07.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Jan 23 09:22:07.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:07.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:07.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:07.553: INFO:
Jan 23 09:22:09.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:09.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Jan 23 09:22:09.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:09.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:09.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:09.553: INFO:
Jan 23 09:22:11.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:11.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Jan 23 09:22:11.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:11.559: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:11.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:11.559: INFO:
Jan 23 09:22:13.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:13.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Jan 23 09:22:13.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:13.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:13.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:13.554: INFO:
Jan 23 09:22:15.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:15.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Jan 23 09:22:15.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:15.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:15.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:15.556: INFO:
Jan 23 09:22:17.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:17.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Jan 23 09:22:17.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:17.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:17.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:17.555: INFO:
Jan 23 09:22:19.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:19.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Jan 23 09:22:19.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:19.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:19.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:19.556: INFO:
Jan 23 09:22:21.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:21.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Jan 23 09:22:21.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:21.558: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:21.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:21.558: INFO:
Jan 23 09:22:23.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:23.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Jan 23 09:22:23.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:23.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:23.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:23.554: INFO:
Jan 23 09:22:25.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:25.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Jan 23 09:22:25.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:25.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:25.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:25.553: INFO:
Jan 23 09:22:27.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:27.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Jan 23 09:22:27.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:27.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:27.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:27.554: INFO:
Jan 23 09:22:29.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:29.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Jan 23 09:22:29.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:29.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:29.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:29.550: INFO:
Jan 23 09:22:31.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:31.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Jan 23 09:22:31.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:31.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:31.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:31.553: INFO:
Jan 23 09:22:33.562: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:33.562: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Jan 23 09:22:33.562: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:33.562: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:33.562: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:33.562: INFO:
Jan 23 09:22:35.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:35.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Jan 23 09:22:35.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:35.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:35.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:35.557: INFO:
Jan 23 09:22:37.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:37.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Jan 23 09:22:37.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:37.561: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:37.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:37.561: INFO:
Jan 23 09:22:39.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:39.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Jan 23 09:22:39.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:39.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:39.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:39.555: INFO:
Jan 23 09:22:41.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:41.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Jan 23 09:22:41.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:41.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:41.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:41.556: INFO:
Jan 23 09:22:43.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:43.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Jan 23 09:22:43.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:43.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:43.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:43.555: INFO:
Jan 23 09:22:45.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:45.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Jan 23 09:22:45.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:45.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:45.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:45.557: INFO:
Jan 23 09:22:47.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:47.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Jan 23 09:22:47.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:47.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:47.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:47.554: INFO:
Jan 23 09:22:49.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:49.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Jan 23 09:22:49.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:49.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:49.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:49.557: INFO:
Jan 23 09:22:51.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:51.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Jan 23 09:22:51.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:51.559: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:51.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:51.559: INFO:
Jan 23 09:22:53.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:53.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Jan 23 09:22:53.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:53.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:53.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:53.554: INFO:
Jan 23 09:22:55.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:55.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Jan 23 09:22:55.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:55.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:55.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:55.554: INFO:
Jan 23 09:22:57.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:57.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Jan 23 09:22:57.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:57.553: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:57.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:57.553: INFO:
Jan 23 09:22:59.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:22:59.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Jan 23 09:22:59.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:22:59.551: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:22:59.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:22:59.551: INFO:
Jan 23 09:23:01.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:23:01.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Jan 23 09:23:01.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:23:01.555: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:01.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:01.555: INFO:
Jan 23 09:23:03.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:23:03.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Jan 23 09:23:03.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:23:03.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:03.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:03.556: INFO:
Jan 23 09:23:05.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:23:05.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Jan 23 09:23:05.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:23:05.556: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:05.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:05.556: INFO:
Jan 23 09:23:07.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:23:07.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Jan 23 09:23:07.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:23:07.554: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:07.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:07.554: INFO:
Jan 23 09:23:09.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:23:09.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Jan 23 09:23:09.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:23:09.550: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:09.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:09.550: INFO:
Jan 23 09:23:11.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:23:11.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Jan 23 09:23:11.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:23:11.557: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:11.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:11.557: INFO:
Jan 23 09:23:13.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:23:13.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Jan 23 09:23:13.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:23:13.561: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:13.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:13.561: INFO:
Jan 23 09:23:13.814: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 23 09:23:13.814: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Jan 23 09:23:13.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 23 09:23:13.814: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:13.814: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:13.814: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m@ 01/23/23 09:23:13.814�[0m
�[1mSTEP:�[0m Found 124 events. �[38;5;243m@ 01/23/23 09:23:13.891�[0m
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: { } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-c6nrc to capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: { } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for calico-node-klq6b: { } Scheduled: Successfully assigned kube-system/calico-node-klq6b to capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for calico-node-v2pkj: { } Scheduled: Successfully assigned kube-system/calico-node-v2pkj to capz-conf-y1oqv9-md-0-jmtm2
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for calico-node-vnrl7: { } Scheduled: Successfully assigned kube-system/calico-node-vnrl7 to capz-conf-y1oqv9-md-0-z5lhc
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: { } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: { } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-9l9fx to capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: { } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: { } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-tvxsr to capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for kube-proxy-cn4p2: { } Scheduled: Successfully assigned kube-system/kube-proxy-cn4p2 to capz-conf-y1oqv9-md-0-z5lhc
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for kube-proxy-s7wrt: { } Scheduled: Successfully assigned kube-system/kube-proxy-s7wrt to capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for kube-proxy-xdqh8: { } Scheduled: Successfully assigned kube-system/kube-proxy-xdqh8 to capz-conf-y1oqv9-md-0-jmtm2
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for metrics-server-c9574f845-cwq45: { } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Jan 23 09:23:13.891: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for metrics-server-c9574f845-cwq45: { } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-cwq45 to capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:37 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-y1oqv9-control-plane-9wsvb_034a3d1b-fea0-4060-a37d-5356c02cf07d became leader
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:39 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-y1oqv9-control-plane-9wsvb_bdb0743f-ba4f-408a-9251-0675fefb0817 became leader
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-9l9fx
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-tvxsr
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-946zt
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-946zt
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for kube-proxy-946zt: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-946zt to capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:43 +0000 UTC - event for kube-proxy-946zt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Failed: Error: cannot find volume "kube-proxy" to mount into container "kube-proxy"
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:43 +0000 UTC - event for kube-proxy-946zt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:43 +0000 UTC - event for kube-proxy-946zt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Container image "gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.1196_724497cda467b7" already present on machine
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:44 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Killing: Stopping container kube-controller-manager
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:44 +0000 UTC - event for kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Killing: Stopping container kube-scheduler
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:56 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "capzci.azurecr.io/kube-controller-manager:v1.27.0-alpha.0.1204_877c0188a44185"
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:57 +0000 UTC - event for kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "capzci.azurecr.io/kube-scheduler:v1.27.0-alpha.0.1204_877c0188a44185"
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:01 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container kube-controller-manager
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:01 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container kube-controller-manager
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:01 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "capzci.azurecr.io/kube-controller-manager:v1.27.0-alpha.0.1204_877c0188a44185" in 4.39289367s (4.393221879s including waiting)
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:04 +0000 UTC - event for kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "capzci.azurecr.io/kube-scheduler:v1.27.0-alpha.0.1204_877c0188a44185" in 3.375797191s (6.778439528s including waiting)
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:04 +0000 UTC - event for kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container kube-scheduler
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:04 +0000 UTC - event for kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container kube-scheduler
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:05 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-y1oqv9-control-plane-9wsvb_8447256d-d9f5-45e8-afa7-c063038603f1 became leader
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:17 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-y1oqv9-control-plane-9wsvb_277b2047-8f25-4f88-b9a6-5a5dae3680ef became leader
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:20 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:20 +0000 UTC - event for calico-kube-controllers: {controllermanager } NoPods: No matching pods found
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:20 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-klq6b
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:20 +0000 UTC - event for etcd-capz-conf-y1oqv9-control-plane-9wsvb: {node-controller } NodeNotReady: Node is not ready
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:20 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {node-controller } NodeNotReady: Node is not ready
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:20 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-s7wrt
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:20 +0000 UTC - event for kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb: {node-controller } NodeNotReady: Node is not ready
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:20 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:21 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-c6nrc
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:21 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:21 +0000 UTC - event for kube-proxy-s7wrt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185"
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:21 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-cwq45
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:27 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.561493051s (6.561638867s including waiting)
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:27 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container upgrade-ipam
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:28 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container upgrade-ipam
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:31 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:31 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container install-cni
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:31 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container install-cni
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:33 +0000 UTC - event for kube-proxy-s7wrt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185" in 5.944252602s (12.3873728s including waiting)
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:34 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "ca8f39c57f0b4fc0e0c799c43d07c10d1220e36762c433879157a7ab4bceded1": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:34 +0000 UTC - event for kube-proxy-s7wrt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container kube-proxy
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:34 +0000 UTC - event for kube-proxy-s7wrt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container kube-proxy
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/calico-kube-controllers-657b584867-c6nrc
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "fc224f7e6e7c67523299b7cc714660912423b3553d8eee0b9014cba0d0bf6d37": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-56f4c55bf9-9l9fx
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "8a9c89995202d7f51715db6934764c96c59bf7bb832ecdd0da47101b37a213a8": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-56f4c55bf9-tvxsr
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for metrics-server-c9574f845-cwq45: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-c9574f845-cwq45
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a3e766dcfad2c005fb90e660919f1e49502df18adb3df401ce8e2fd3e9616d40": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:42 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.152507128s (7.152512828s including waiting)
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:43 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:43 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container calico-node
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:43 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container calico-node
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:44 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:45 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:47 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container coredns
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:47 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container coredns
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:47 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:49 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container coredns
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:49 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:49 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container coredns
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:50 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:50 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.748253971s (4.748410873s including waiting)
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:50 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container metrics-server
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:50 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container metrics-server
Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:56 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container calico-kube-controllers
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:10:56 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container calico-kube-controllers
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:10:56 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Unhealthy: Readiness probe failed: initialized to false
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:10:56 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.936713244s (6.325842494s including waiting)
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:11:52 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-v2pkj
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:11:52 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-xdqh8
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:11:58 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:11:58 +0000 UTC - event for kube-proxy-xdqh8: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185"
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:05 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Started: Started container upgrade-ipam
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:05 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Created: Created container upgrade-ipam
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:05 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.65242724s (6.652553439s including waiting)
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:08 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Created: Created container install-cni
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:08 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:08 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Started: Started container install-cni
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:11 +0000 UTC - event for kube-proxy-xdqh8: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Created: Created container kube-proxy
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:11 +0000 UTC - event for kube-proxy-xdqh8: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185" in 6.289183447s (12.937268171s including waiting)
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:12 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:12 +0000 UTC - event for kube-proxy-xdqh8: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Started: Started container kube-proxy
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:19 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Created: Created container calico-node
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:19 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.153259189s (7.153263689s including waiting)
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:19 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Started: Started container calico-node
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:20 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:39 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-vnrl7
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:39 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-cn4p2
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:56 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:56 +0000 UTC - event for kube-proxy-cn4p2: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185"
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:03 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.118557316s (7.118740523s including waiting)
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:03 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Created: Created container upgrade-ipam
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:03 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Started: Started container upgrade-ipam
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:05 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Created: Created container install-cni
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:05 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:05 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Started: Started container install-cni
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:09 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:09 +0000 UTC - event for kube-proxy-cn4p2: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Started: Started container kube-proxy
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:09 +0000 UTC - event for kube-proxy-cn4p2: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Created: Created container kube-proxy
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:09 +0000 UTC - event for kube-proxy-cn4p2: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185" in 6.078029749s (13.186037351s including waiting)
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:17 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.485894077s (7.485908577s including waiting)
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:17 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Created: Created container calico-node
Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:17 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Started: Started container calico-node
Jan 23 09:23:13.997: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 23 09:23:13.997: INFO: calico-kube-controllers-657b584867-c6nrc capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:57 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:57 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:34 +0000 UTC }]
Jan 23 09:23:13.997: INFO: calico-node-klq6b capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:35 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:51 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:51 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:20 +0000 UTC }]
Jan 23 09:23:13.997: INFO: calico-node-v2pkj capz-conf-y1oqv9-md-0-jmtm2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:12 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:21 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:21 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:11:52 +0000 UTC }]
Jan 23 09:23:13.997: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:23 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:23 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }]
Jan 23 09:23:13.997: INFO: coredns-56f4c55bf9-9l9fx capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:34 +0000 UTC }]
Jan 23 09:23:13.997: INFO: coredns-56f4c55bf9-tvxsr capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:49 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:49 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:34 +0000 UTC }]
Jan 23 09:23:13.997: INFO: etcd-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:09:42 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:09:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:09:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:09:42 +0000 UTC }]
Jan 23 09:23:13.997: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
Jan 23 09:23:13.997: INFO: kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:09:56 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:16 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:16 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:09:56 +0000 UTC }]
Jan 23 09:23:13.997: INFO: kube-proxy-cn4p2 capz-conf-y1oqv9-md-0-z5lhc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }]
Jan 23 09:23:13.997: INFO: kube-proxy-s7wrt capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:20 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:35 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:35 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:20 +0000 UTC }]
Jan 23 09:23:13.997: INFO: kube-proxy-xdqh8 capz-conf-y1oqv9-md-0-jmtm2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:11:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:12 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:12 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:11:52 +0000 UTC }]
Jan 23 09:23:13.997: INFO: kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:09:57 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:09:57 +0000 UTC }]
Jan 23 09:23:13.997: INFO: metrics-server-c9574f845-cwq45 capz-conf-y1oqv9-control-plane-9wsvb Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:11:15 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:11:15 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:10:34 +0000 UTC }]
Jan 23 09:23:13.997: INFO:
Jan 23 09:23:14.422: INFO:
Logging node info for node capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:14.487: INFO: Node Info: &Node{ObjectMeta:{capz-conf-y1oqv9-control-plane-9wsvb dad5094c-4ae3-4fac-b937-c3c147f5f205 1801 0 2023-01-23 09:09:40 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:westus3 failure-domain.beta.kubernetes.io/zone:westus3-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-y1oqv9-control-plane-9wsvb kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:westus3 topology.kubernetes.io/zone:westus3-1] map[cluster.x-k8s.io/cluster-name:capz-conf-y1oqv9 cluster.x-k8s.io/cluster-namespace:capz-conf-y1oqv9 cluster.x-k8s.io/machine:capz-conf-y1oqv9-control-plane-9whxt cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-y1oqv9-control-plane kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.0.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.66.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-23 09:09:40 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/control-plane":{},"f:node.kubernetes.io/exclude-from-external-load-balancers":{}}}} } {kubelet Update v1 2023-01-23 09:09:40 +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/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {manager Update v1 2023-01-23 09:10:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2023-01-23 09:10:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2023-01-23 09:10:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-23 09:21:26 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-y1oqv9/providers/Microsoft.Compute/virtualMachines/capz-conf-y1oqv9-control-plane-9wsvb,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/control-plane,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8344743936 0} {<nil>} 8149164Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-23 09:10:43 +0000 UTC,LastTransitionTime:2023-01-23 09:10:43 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-23 09:21:26 +0000 UTC,LastTransitionTime:2023-01-23 09:09:16 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-23 09:21:26 +0000 UTC,LastTransitionTime:2023-01-23 09:09:16 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-23 09:21:26 +0000 UTC,LastTransitionTime:2023-01-23 09:09:16 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-23 09:21:26 +0000 UTC,LastTransitionTime:2023-01-23 09:10:34 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-y1oqv9-control-plane-9wsvb,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a2115c563e2748f8bb169b4ca1cbe920,SystemUUID:bd540898-3c85-7c4e-921e-39f0f43c21d7,BootID:e92a7bb3-6b5f-4e64-b632-f219541c125f,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1204+877c0188a44185,KubeProxyVersion:v1.27.0-alpha.0.1204+877c0188a44185,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:78bc199299f966b0694dc4044501aee2d7ebd6862b2b0a00bca3ee8d3813c82f docker.io/calico/kube-controllers:v3.23.0],SizeBytes:56343954,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:2f00157b962616db88291e8a1fc2bc8a89404240d20812811cd7ce8f86793634 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.1196_724497cda467b7],SizeBytes:35465106,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:de11e335abdc4b0e6de86099ec83eab033b037463b91cacfafd54f31ea47c794 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.1196_724497cda467b7],SizeBytes:32315279,},ContainerImage{Names:[capzci.azurecr.io/kube-controller-manager@sha256:828a352f6be7cd05b8a6969c60ae715847deb5887a3a56ffb176d9b3552393fd capzci.azurecr.io/kube-controller-manager:v1.27.0-alpha.0.1204_877c0188a44185],SizeBytes:32314031,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:35c6c0b1f74e3e0ed99205a7dd7f5238fbe549a4634168500a9acb95f15f0988 gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.1196_724497cda467b7],SizeBytes:21486199,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:0928b987d89291e341df06d9b567fa293fb8baf6dbd4874e1416fbd07225cf02 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185],SizeBytes:21484016,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:556c96edf539ecb8a554d098c506f6050f5e878d528c6d3bc7919bb2b64d77ce gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.1196_724497cda467b7],SizeBytes:17471546,},ContainerImage{Names:[capzci.azurecr.io/kube-scheduler@sha256:4229dc00850873442ac06ee3a9098467376b6a5593d9fa2d40fa93fe9d1af9fb capzci.azurecr.io/kube-scheduler:v1.27.0-alpha.0.1204_877c0188a44185],SizeBytes:17469538,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Jan 23 09:23:14.488: INFO:
Logging kubelet events for node capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:14.554: INFO:
Logging pods the kubelet thinks is on node capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:14.638: INFO: coredns-56f4c55bf9-tvxsr started at 2023-01-23 09:10:34 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Container coredns ready: true, restart count 0
Jan 23 09:23:14.638: INFO: etcd-capz-conf-y1oqv9-control-plane-9wsvb started at 2023-01-23 09:09:42 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Container etcd ready: true, restart count 0
Jan 23 09:23:14.638: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb started at <nil> (0+0 container statuses recorded)
Jan 23 09:23:14.638: INFO: kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb started at 2023-01-23 09:09:56 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Container kube-controller-manager ready: true, restart count 0
Jan 23 09:23:14.638: INFO: kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb started at 2023-01-23 09:09:57 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Container kube-scheduler ready: true, restart count 0
Jan 23 09:23:14.638: INFO: calico-node-klq6b started at 2023-01-23 09:10:20 +0000 UTC (2+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 23 09:23:14.638: INFO: Init container install-cni ready: true, restart count 0
Jan 23 09:23:14.638: INFO: Container calico-node ready: true, restart count 0
Jan 23 09:23:14.638: INFO: kube-proxy-s7wrt started at 2023-01-23 09:10:20 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Container kube-proxy ready: true, restart count 0
Jan 23 09:23:14.638: INFO: coredns-56f4c55bf9-9l9fx started at 2023-01-23 09:10:34 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Container coredns ready: true, restart count 0
Jan 23 09:23:14.638: INFO: calico-kube-controllers-657b584867-c6nrc started at 2023-01-23 09:10:34 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Container calico-kube-controllers ready: true, restart count 0
Jan 23 09:23:14.638: INFO: metrics-server-c9574f845-cwq45 started at 2023-01-23 09:10:34 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:14.638: INFO: Container metrics-server ready: true, restart count 0
Jan 23 09:23:15.048: INFO:
Latency metrics for node capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:15.048: INFO:
Logging node info for node capz-conf-y1oqv9-md-0-jmtm2
Jan 23 09:23:15.187: INFO: Node Info: &Node{ObjectMeta:{capz-conf-y1oqv9-md-0-jmtm2 c0ebcac5-557a-4bd6-8bed-63d80d8ca915 1904 0 2023-01-23 09:11:52 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:westus3 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-y1oqv9-md-0-jmtm2 kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:westus3 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-y1oqv9 cluster.x-k8s.io/cluster-namespace:capz-conf-y1oqv9 cluster.x-k8s.io/machine:capz-conf-y1oqv9-md-0-65bcc4d778-9r7t6 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-y1oqv9-md-0-65bcc4d778 kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.5/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.151.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-23 09:11:52 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-23 09:11:52 +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/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-23 09:12:11 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-23 09:12:20 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {manager Update v1 2023-01-23 09:12:22 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kubelet Update v1 2023-01-23 09:22:35 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-y1oqv9/providers/Microsoft.Compute/virtualMachines/capz-conf-y1oqv9-md-0-jmtm2,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8344743936 0} {<nil>} 8149164Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-23 09:12:20 +0000 UTC,LastTransitionTime:2023-01-23 09:12:20 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-23 09:22:35 +0000 UTC,LastTransitionTime:2023-01-23 09:11:52 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-23 09:22:35 +0000 UTC,LastTransitionTime:2023-01-23 09:11:52 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-23 09:22:35 +0000 UTC,LastTransitionTime:2023-01-23 09:11:52 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-23 09:22:35 +0000 UTC,LastTransitionTime:2023-01-23 09:12:11 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-y1oqv9-md-0-jmtm2,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:47cb5b12a4fb43c99402e9e23f65f4e8,SystemUUID:0ca67f72-30a0-1d45-82ed-68acd9f5009c,BootID:d9f19248-bfcc-4cad-8361-533d5b594f68,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1204+877c0188a44185,KubeProxyVersion:v1.27.0-alpha.0.1204+877c0188a44185,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:0928b987d89291e341df06d9b567fa293fb8baf6dbd4874e1416fbd07225cf02 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185],SizeBytes:21484016,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Jan 23 09:23:15.187: INFO:
Logging kubelet events for node capz-conf-y1oqv9-md-0-jmtm2
Jan 23 09:23:15.387: INFO:
Logging pods the kubelet thinks is on node capz-conf-y1oqv9-md-0-jmtm2
Jan 23 09:23:15.594: INFO: calico-node-v2pkj started at 2023-01-23 09:11:53 +0000 UTC (2+1 container statuses recorded)
Jan 23 09:23:15.594: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 23 09:23:15.594: INFO: Init container install-cni ready: true, restart count 0
Jan 23 09:23:15.594: INFO: Container calico-node ready: true, restart count 0
Jan 23 09:23:15.594: INFO: kube-proxy-xdqh8 started at 2023-01-23 09:11:53 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:15.594: INFO: Container kube-proxy ready: true, restart count 0
Jan 23 09:23:16.215: INFO:
Latency metrics for node capz-conf-y1oqv9-md-0-jmtm2
Jan 23 09:23:16.215: INFO:
Logging node info for node capz-conf-y1oqv9-md-0-z5lhc
Jan 23 09:23:16.387: INFO: Node Info: &Node{ObjectMeta:{capz-conf-y1oqv9-md-0-z5lhc dff61d1e-deef-4955-b419-b993631489e9 1545 0 2023-01-23 09:12:39 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:westus3 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-y1oqv9-md-0-z5lhc kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:westus3 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-y1oqv9 cluster.x-k8s.io/cluster-namespace:capz-conf-y1oqv9 cluster.x-k8s.io/machine:capz-conf-y1oqv9-md-0-65bcc4d778-54l28 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-y1oqv9-md-0-65bcc4d778 kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.111.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-23 09:12:39 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-23 09:12:39 +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/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {manager Update v1 2023-01-23 09:13:00 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2023-01-23 09:13:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-23 09:13:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-23 09:18:36 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-y1oqv9/providers/Microsoft.Compute/virtualMachines/capz-conf-y1oqv9-md-0-z5lhc,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8344743936 0} {<nil>} 8149164Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-23 09:13:17 +0000 UTC,LastTransitionTime:2023-01-23 09:13:17 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-23 09:18:36 +0000 UTC,LastTransitionTime:2023-01-23 09:12:38 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-23 09:18:36 +0000 UTC,LastTransitionTime:2023-01-23 09:12:38 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-23 09:18:36 +0000 UTC,LastTransitionTime:2023-01-23 09:12:38 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-23 09:18:36 +0000 UTC,LastTransitionTime:2023-01-23 09:13:08 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-y1oqv9-md-0-z5lhc,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:7f7631c000964ca6b8e41181986a42dc,SystemUUID:5dc55c5b-72a4-6b4b-ac06-ab9c1b53af73,BootID:ca144385-ae50-40ce-bdd3-5a45a95a3eac,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1204+877c0188a44185,KubeProxyVersion:v1.27.0-alpha.0.1204+877c0188a44185,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:0928b987d89291e341df06d9b567fa293fb8baf6dbd4874e1416fbd07225cf02 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185],SizeBytes:21484016,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Jan 23 09:23:16.387: INFO:
Logging kubelet events for node capz-conf-y1oqv9-md-0-z5lhc
Jan 23 09:23:16.587: INFO:
Logging pods the kubelet thinks is on node capz-conf-y1oqv9-md-0-z5lhc
Jan 23 09:23:16.795: INFO: calico-node-vnrl7 started at 2023-01-23 09:12:43 +0000 UTC (2+1 container statuses recorded)
Jan 23 09:23:16.795: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 23 09:23:16.795: INFO: Init container install-cni ready: true, restart count 0
Jan 23 09:23:16.795: INFO: Container calico-node ready: true, restart count 0
Jan 23 09:23:16.795: INFO: kube-proxy-cn4p2 started at 2023-01-23 09:12:43 +0000 UTC (0+1 container statuses recorded)
Jan 23 09:23:16.795: INFO: Container kube-proxy ready: true, restart count 0
Jan 23 09:23:17.417: INFO:
Latency metrics for node capz-conf-y1oqv9-md-0-z5lhc
Jan 23 09:23:17.626: INFO: Running kubectl logs on non-ready containers in kube-system
Jan 23 09:23:17.987: INFO: Failed to get logs of pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb)
Jan 23 09:23:17.987: INFO: Logs of kube-system/kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb:kube-apiserver on node capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:17.987: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb:kube-apiserver
�[38;5;9m[FAILED]�[0m in [SynchronizedBeforeSuite] - test/e2e/e2e.go:251 �[38;5;243m@ 01/23/23 09:23:17.987�[0m
�[38;5;243m<< Timeline�[0m
�[38;5;9m[FAILED] Error waiting for all pods to be running and ready: 1 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s
POD NODE PHASE GRACE CONDITIONS
kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending []
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:251�[0m �[38;5;243m@ 01/23/23 09:23:17.987�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.132 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.023�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.337 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.027�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.285 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.023�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.319 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.023�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.355 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.023�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.369 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.027�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.361 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.037�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.350 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.027�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.243 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.041�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.384 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.041�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.341 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.046�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.161 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.045�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.361 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.044�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.395 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.046�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.151 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.047�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.321 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.045�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.124 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.046�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.310 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.044�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.354 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.046�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.117 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.046�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.144 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.041�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.367 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.045�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.168 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.047�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.356 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/23/23 09:23:18.047�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m�[1mSummarizing 25 Failures:�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:251�[0m
�[38;5;9m�[1mRan 0 of 7075 Specs in 605.992 seconds�[0m
�[38;5;9m�[1mFAIL!�[0m -- �[38;5;14m�[1mA BeforeSuite node failed so all tests were skipped.�[0m
I0123 09:13:10.273207 12 e2e.go:126] Starting e2e run "ab04acf0-1f3f-475d-9b44-3c4d86380839" on Ginkgo node 1
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.96s)
FAIL
I0123 09:13:10.532189 14 e2e.go:126] Starting e2e run "06ab23fe-decc-4c4c-8f27-259686c0e0ac" on Ginkgo node 2
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.56s)
FAIL
I0123 09:13:10.341681 16 e2e.go:126] Starting e2e run "d974feb6-b057-4def-83da-c54161511cfc" on Ginkgo node 3
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.74s)
FAIL
I0123 09:13:10.371830 18 e2e.go:126] Starting e2e run "35e0c578-b71b-44f4-8286-a9396c75cd70" on Ginkgo node 4
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.72s)
FAIL
I0123 09:13:10.378075 31 e2e.go:126] Starting e2e run "7c815b96-3bed-4999-864b-b3e77785cf15" on Ginkgo node 5
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.73s)
FAIL
I0123 09:13:10.615539 39 e2e.go:126] Starting e2e run "2c52a052-1032-428f-9c1f-6f4b34888f7b" on Ginkgo node 6
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.47s)
FAIL
I0123 09:13:10.614856 49 e2e.go:126] Starting e2e run "f2944f50-fe64-405e-b429-4437a3ad7e51" on Ginkgo node 7
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.54s)
FAIL
I0123 09:13:10.769273 56 e2e.go:126] Starting e2e run "1668723a-e377-43b5-a487-0528d5f27127" on Ginkgo node 8
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.31s)
FAIL
I0123 09:13:10.731374 68 e2e.go:126] Starting e2e run "b4660a6d-2092-4479-9a20-7e651842577c" on Ginkgo node 9
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.33s)
FAIL
I0123 09:13:10.671773 78 e2e.go:126] Starting e2e run "db22290d-c831-46e9-95a9-f275aedfe377" on Ginkgo node 10
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.44s)
FAIL
I0123 09:13:10.684951 80 e2e.go:126] Starting e2e run "7c8554a4-e527-4bce-a947-5afafc0b04a1" on Ginkgo node 11
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.40s)
FAIL
I0123 09:13:11.076568 89 e2e.go:126] Starting e2e run "5117cc59-88fa-41cc-b47f-aea2fd0adb88" on Ginkgo node 12
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.03s)
FAIL
I0123 09:13:10.956134 103 e2e.go:126] Starting e2e run "4e216bc0-3c1d-479d-bbbf-caccfce50110" on Ginkgo node 13
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.13s)
FAIL
I0123 09:13:10.783904 105 e2e.go:126] Starting e2e run "663863fc-f654-4513-8b96-713e092e22dc" on Ginkgo node 14
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.30s)
FAIL
I0123 09:13:10.976696 111 e2e.go:126] Starting e2e run "b0219db3-47b1-4eb9-bb90-1f5be4a4bb73" on Ginkgo node 15
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.11s)
FAIL
I0123 09:13:11.092975 121 e2e.go:126] Starting e2e run "902754d3-1764-4d0c-b826-22a4f094538e" on Ginkgo node 16
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.02s)
FAIL
I0123 09:13:10.809614 136 e2e.go:126] Starting e2e run "49260d45-1c52-41aa-a5ab-a301ca759c24" on Ginkgo node 17
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.27s)
FAIL
I0123 09:13:10.768001 142 e2e.go:126] Starting e2e run "ac5f46bf-7845-4369-8125-691d815ef8b9" on Ginkgo node 18
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.29s)
FAIL
I0123 09:13:11.112854 145 e2e.go:126] Starting e2e run "4008d3fa-406e-434b-8771-13ef50a72871" on Ginkgo node 19
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (606.98s)
FAIL
I0123 09:13:10.964978 157 e2e.go:126] Starting e2e run "2e1cf1da-edb1-4d67-b8f6-cc3e52ecb417" on Ginkgo node 20
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.12s)
FAIL
I0123 09:13:10.638684 163 e2e.go:126] Starting e2e run "962af21f-1ad8-4755-895d-2f4059812fdd" on Ginkgo node 21
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (607.45s)
FAIL
I0123 09:13:11.259060 180 e2e.go:126] Starting e2e run "00948ca1-346e-4293-bf25-83e7810ea400" on Ginkgo node 22
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (606.83s)
FAIL
I0123 09:13:11.204658 201 e2e.go:126] Starting e2e run "0f9675d6-6946-4426-a259-d9b2bab1f9d1" on Ginkgo node 23
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (606.87s)
FAIL
I0123 09:13:11.216401 206 e2e.go:126] Starting e2e run "218baced-12eb-42ef-806f-4a4ec8e31973" on Ginkgo node 24
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (606.88s)
FAIL
I0123 09:13:11.209608 210 e2e.go:126] Starting e2e run "df40a619-2485-485b-b371-4c13036ad0dc" on Ginkgo node 25
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
�[38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
--- FAIL: TestE2E (606.87s)
FAIL
Ginkgo ran 1 suite in 10m8.505951188s
Test Suite Failed
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--slowSpecThreshold is deprecated use --slow-spec-threshold instead and pass in a duration string (e.g. '5s', not '5.0')�[0m
�[1mLearn more at:�[0m �[38;5;14m�[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed--slowspecthreshold�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m
[AfterEach] Conformance Tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:237
Jan 23 09:23:18.831: INFO: FAILED!
Jan 23 09:23:18.831: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
�[1mSTEP�[0m: Dumping logs from the "capz-conf-y1oqv9" workload cluster
�[1mSTEP�[0m: Dumping workload cluster capz-conf-y1oqv9/capz-conf-y1oqv9 logs
Jan 23 09:23:18.949: INFO: Collecting logs for Linux node capz-conf-y1oqv9-control-plane-9wsvb in cluster capz-conf-y1oqv9 in namespace capz-conf-y1oqv9
Jan 23 09:23:33.372: INFO: Collecting boot logs for AzureMachine capz-conf-y1oqv9-control-plane-9wsvb
Jan 23 09:23:34.572: INFO: Collecting logs for Linux node capz-conf-y1oqv9-md-0-z5lhc in cluster capz-conf-y1oqv9 in namespace capz-conf-y1oqv9
Jan 23 09:23:42.019: INFO: Collecting boot logs for AzureMachine capz-conf-y1oqv9-md-0-z5lhc
Jan 23 09:23:42.484: INFO: Collecting logs for Linux node capz-conf-y1oqv9-md-0-jmtm2 in cluster capz-conf-y1oqv9 in namespace capz-conf-y1oqv9
Jan 23 09:23:52.381: INFO: Collecting boot logs for AzureMachine capz-conf-y1oqv9-md-0-jmtm2
�[1mSTEP�[0m: Dumping workload cluster capz-conf-y1oqv9/capz-conf-y1oqv9 kube-system pod logs
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-v2pkj, container calico-node
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-kube-controllers-657b584867-c6nrc, container calico-kube-controllers
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-vnrl7, container calico-node
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-klq6b, container calico-node
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-v2pkj
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-klq6b
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-vnrl7
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-kube-controllers-657b584867-c6nrc
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-cn4p2
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb
�[1mSTEP�[0m: Collecting events for Pod kube-system/coredns-56f4c55bf9-tvxsr
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb, container kube-controller-manager
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-s7wrt
�[1mSTEP�[0m: Creating log watcher for controller kube-system/etcd-capz-conf-y1oqv9-control-plane-9wsvb, container etcd
�[1mSTEP�[0m: failed to find events of Pod "kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb"
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb, container kube-apiserver
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-s7wrt, container kube-proxy
�[1mSTEP�[0m: Collecting events for Pod kube-system/etcd-capz-conf-y1oqv9-control-plane-9wsvb
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-cn4p2, container kube-proxy
�[1mSTEP�[0m: Collecting events for Pod kube-system/metrics-server-c9574f845-cwq45
�[1mSTEP�[0m: Creating log watcher for controller kube-system/metrics-server-c9574f845-cwq45, container metrics-server
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-xdqh8
�[1mSTEP�[0m: Collecting events for Pod kube-system/coredns-56f4c55bf9-9l9fx
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-xdqh8, container kube-proxy
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-56f4c55bf9-9l9fx, container coredns
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-56f4c55bf9-tvxsr, container coredns
�[1mSTEP�[0m: Fetching kube-system pod logs took 706.411727ms
�[1mSTEP�[0m: Dumping workload cluster capz-conf-y1oqv9/capz-conf-y1oqv9 Azure activity log
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb, container kube-scheduler
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb
�[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb, container kube-apiserver: container "kube-apiserver" in pod "kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb" is not available
�[1mSTEP�[0m: Fetching activity logs took 4.264050725s
Jan 23 09:23:57.766: INFO: Dumping all the Cluster API resources in the "capz-conf-y1oqv9" namespace
Jan 23 09:23:58.135: INFO: Deleting all clusters in the capz-conf-y1oqv9 namespace
�[1mSTEP�[0m: Deleting cluster capz-conf-y1oqv9
INFO: Waiting for the Cluster capz-conf-y1oqv9/capz-conf-y1oqv9 to be deleted
�[1mSTEP�[0m: Waiting for cluster capz-conf-y1oqv9 to be deleted
Jan 23 09:28:48.359: INFO: Deleting namespace used for hosting the "conformance-tests" test spec
INFO: Deleting namespace capz-conf-y1oqv9
Jan 23 09:28:48.379: INFO: Checking if any resources are left over in Azure for spec "conformance-tests"
�[1mSTEP�[0m: Redacting sensitive information from logs
from junit.e2e_suite.1.xml
Filter through log files | View test history on testgrid
capz-e2e Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=internal AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=internal CCM=internal AzureDiskCSIMigration=false: upgrade to v1.23 should create volumes dynamically with intree cloud provider
... skipping 119 lines ... Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 138 100 138 0 0 4181 0 --:--:-- --:--:-- --:--:-- 4181 100 35 100 35 0 0 397 0 --:--:-- --:--:-- --:--:-- 397 using CI_VERSION=v1.27.0-alpha.0.1196+724497cda467b7 using KUBERNETES_VERSION=v1.27.0-alpha.0.1196+724497cda467b7 using IMAGE_TAG=v1.27.0-alpha.0.1204_877c0188a44185 Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.27.0-alpha.0.1204_877c0188a44185 not found: manifest unknown: manifest tagged by "v1.27.0-alpha.0.1204_877c0188a44185" is not found Building Kubernetes make: Entering directory '/home/prow/go/src/k8s.io/kubernetes' +++ [0123 08:37:40] Verifying Prerequisites.... +++ [0123 08:37:41] Building Docker image kube-build:build-e4cdff0e6d-5-v1.26.0-go1.19.5-bullseye.0 +++ [0123 08:40:31] Creating data container kube-build-data-e4cdff0e6d-5-v1.26.0-go1.19.5-bullseye.0 +++ [0123 08:40:52] Syncing sources to container ... skipping 668 lines ... [37m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99[0m [BeforeEach] Conformance Tests /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:55 INFO: Cluster name is capz-conf-y1oqv9 [1mSTEP[0m: Creating namespace "capz-conf-y1oqv9" for hosting the cluster Jan 23 09:05:34.279: INFO: starting to create namespace for hosting the "capz-conf-y1oqv9" test spec 2023/01/23 09:05:34 failed trying to get namespace (capz-conf-y1oqv9):namespaces "capz-conf-y1oqv9" not found INFO: Creating namespace capz-conf-y1oqv9 INFO: Creating event watcher for namespace "capz-conf-y1oqv9" [Measure] conformance-tests /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99 INFO: Creating the workload cluster with name "capz-conf-y1oqv9" using the "conformance-presubmit-artifacts" template (Kubernetes v1.27.0-alpha.0.1196+724497cda467b7, 1 control-plane machines, 2 worker machines) INFO: Getting the cluster template yaml ... skipping 40 lines ... ==================================================== Random Seed: [1m1674465189[0m - will randomize all specs Will run [1m344[0m of [1m7075[0m specs Running in parallel across [1m25[0m processes [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.347 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;243mTimeline >>[0m Jan 23 09:13:12.641: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 23 09:13:12.647: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 23 09:13:12.975: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 23 09:13:13.320: INFO: The status of Pod calico-node-vnrl7 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:13.320: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:13.320: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 23 09:13:13.320: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:13.320: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:13.320: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }] Jan 23 09:13:13.321: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:13.321: INFO: Jan 23 09:13:15.559: INFO: The status of Pod calico-node-vnrl7 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:15.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:15.559: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Jan 23 09:13:15.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:15.559: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:15.559: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }] Jan 23 09:13:15.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:15.559: INFO: Jan 23 09:13:17.560: INFO: The status of Pod calico-node-vnrl7 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:17.560: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:17.560: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Jan 23 09:13:17.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:17.560: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:17.560: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }] Jan 23 09:13:17.560: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:17.560: INFO: Jan 23 09:13:19.552: INFO: The status of Pod calico-node-vnrl7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:19.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:19.552: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Jan 23 09:13:19.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:19.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:19.552: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }] Jan 23 09:13:19.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:19.552: INFO: Jan 23 09:13:21.550: INFO: The status of Pod calico-node-vnrl7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:21.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:21.550: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Jan 23 09:13:21.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:21.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:21.550: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }] Jan 23 09:13:21.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:21.550: INFO: Jan 23 09:13:23.551: INFO: The status of Pod calico-node-vnrl7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:23.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:23.551: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Jan 23 09:13:23.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:23.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:23.551: INFO: calico-node-vnrl7 capz-conf-y1oqv9-md-0-z5lhc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:13:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-23 09:12:39 +0000 UTC }] Jan 23 09:13:23.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:23.551: INFO: Jan 23 09:13:25.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:25.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Jan 23 09:13:25.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:25.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:25.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:25.551: INFO: Jan 23 09:13:27.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:27.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Jan 23 09:13:27.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:27.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:27.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:27.551: INFO: Jan 23 09:13:29.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:29.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Jan 23 09:13:29.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:29.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:29.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:29.550: INFO: Jan 23 09:13:31.560: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:31.560: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Jan 23 09:13:31.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:31.560: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:31.560: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:31.560: INFO: Jan 23 09:13:33.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:33.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Jan 23 09:13:33.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:33.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:33.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:33.551: INFO: Jan 23 09:13:35.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:35.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Jan 23 09:13:35.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:35.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:35.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:35.550: INFO: Jan 23 09:13:37.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:37.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Jan 23 09:13:37.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:37.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:37.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:37.553: INFO: Jan 23 09:13:39.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:39.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Jan 23 09:13:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:39.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:39.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:39.550: INFO: Jan 23 09:13:41.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:41.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Jan 23 09:13:41.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:41.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:41.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:41.550: INFO: Jan 23 09:13:43.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:43.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Jan 23 09:13:43.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:43.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:43.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:43.550: INFO: Jan 23 09:13:45.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:45.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Jan 23 09:13:45.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:45.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:45.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:45.554: INFO: Jan 23 09:13:47.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:47.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Jan 23 09:13:47.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:47.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:47.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:47.551: INFO: Jan 23 09:13:49.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:49.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Jan 23 09:13:49.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:49.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:49.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:49.551: INFO: Jan 23 09:13:51.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:51.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Jan 23 09:13:51.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:51.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:51.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:51.551: INFO: Jan 23 09:13:53.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:53.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Jan 23 09:13:53.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:53.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:53.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:53.551: INFO: Jan 23 09:13:55.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:55.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Jan 23 09:13:55.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:55.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:55.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:55.552: INFO: Jan 23 09:13:57.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:57.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Jan 23 09:13:57.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:57.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:57.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:57.549: INFO: Jan 23 09:13:59.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:13:59.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Jan 23 09:13:59.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:13:59.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:13:59.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:13:59.551: INFO: Jan 23 09:14:01.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:01.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Jan 23 09:14:01.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:01.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:01.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:01.550: INFO: Jan 23 09:14:03.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:03.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Jan 23 09:14:03.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:03.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:03.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:03.550: INFO: Jan 23 09:14:05.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:05.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Jan 23 09:14:05.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:05.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:05.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:05.550: INFO: Jan 23 09:14:07.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:07.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Jan 23 09:14:07.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:07.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:07.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:07.550: INFO: Jan 23 09:14:09.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:09.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Jan 23 09:14:09.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:09.558: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:09.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:09.558: INFO: Jan 23 09:14:11.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:11.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Jan 23 09:14:11.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:11.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:11.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:11.556: INFO: Jan 23 09:14:13.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:13.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Jan 23 09:14:13.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:13.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:13.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:13.552: INFO: Jan 23 09:14:15.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:15.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Jan 23 09:14:15.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:15.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:15.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:15.549: INFO: Jan 23 09:14:17.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:17.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Jan 23 09:14:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:17.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:17.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:17.550: INFO: Jan 23 09:14:19.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:19.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Jan 23 09:14:19.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:19.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:19.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:19.555: INFO: Jan 23 09:14:21.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:21.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Jan 23 09:14:21.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:21.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:21.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:21.549: INFO: Jan 23 09:14:23.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:23.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Jan 23 09:14:23.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:23.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:23.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:23.551: INFO: Jan 23 09:14:25.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:25.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Jan 23 09:14:25.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:25.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:25.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:25.553: INFO: Jan 23 09:14:27.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:27.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Jan 23 09:14:27.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:27.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:27.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:27.550: INFO: Jan 23 09:14:29.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:29.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Jan 23 09:14:29.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:29.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:29.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:29.551: INFO: Jan 23 09:14:31.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:31.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Jan 23 09:14:31.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:31.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:31.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:31.550: INFO: Jan 23 09:14:33.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:33.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Jan 23 09:14:33.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:33.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:33.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:33.551: INFO: Jan 23 09:14:35.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:35.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Jan 23 09:14:35.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:35.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:35.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:35.552: INFO: Jan 23 09:14:37.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:37.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Jan 23 09:14:37.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:37.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:37.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:37.549: INFO: Jan 23 09:14:39.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:39.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Jan 23 09:14:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:39.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:39.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:39.550: INFO: Jan 23 09:14:41.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:41.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Jan 23 09:14:41.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:41.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:41.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:41.551: INFO: Jan 23 09:14:43.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:43.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Jan 23 09:14:43.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:43.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:43.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:43.549: INFO: Jan 23 09:14:45.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:45.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Jan 23 09:14:45.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:45.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:45.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:45.556: INFO: Jan 23 09:14:47.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:47.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Jan 23 09:14:47.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:47.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:47.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:47.550: INFO: Jan 23 09:14:49.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:49.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Jan 23 09:14:49.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:49.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:49.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:49.552: INFO: Jan 23 09:14:51.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:51.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Jan 23 09:14:51.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:51.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:51.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:51.551: INFO: Jan 23 09:14:53.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:53.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Jan 23 09:14:53.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:53.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:53.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:53.555: INFO: Jan 23 09:14:55.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:55.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Jan 23 09:14:55.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:55.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:55.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:55.551: INFO: Jan 23 09:14:57.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:57.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Jan 23 09:14:57.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:57.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:57.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:57.549: INFO: Jan 23 09:14:59.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:14:59.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Jan 23 09:14:59.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:14:59.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:14:59.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:14:59.549: INFO: Jan 23 09:15:01.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:01.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Jan 23 09:15:01.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:01.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:01.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:01.552: INFO: Jan 23 09:15:03.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:03.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Jan 23 09:15:03.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:03.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:03.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:03.550: INFO: Jan 23 09:15:05.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:05.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Jan 23 09:15:05.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:05.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:05.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:05.557: INFO: Jan 23 09:15:07.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:07.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Jan 23 09:15:07.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:07.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:07.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:07.549: INFO: Jan 23 09:15:09.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:09.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Jan 23 09:15:09.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:09.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:09.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:09.550: INFO: Jan 23 09:15:11.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:11.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Jan 23 09:15:11.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:11.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:11.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:11.553: INFO: Jan 23 09:15:13.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:13.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Jan 23 09:15:13.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:13.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:13.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:13.550: INFO: Jan 23 09:15:15.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:15.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Jan 23 09:15:15.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:15.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:15.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:15.551: INFO: Jan 23 09:15:17.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:17.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Jan 23 09:15:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:17.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:17.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:17.550: INFO: Jan 23 09:15:19.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:19.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Jan 23 09:15:19.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:19.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:19.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:19.549: INFO: Jan 23 09:15:21.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:21.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Jan 23 09:15:21.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:21.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:21.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:21.552: INFO: Jan 23 09:15:23.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:23.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Jan 23 09:15:23.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:23.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:23.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:23.551: INFO: Jan 23 09:15:25.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:25.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Jan 23 09:15:25.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:25.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:25.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:25.549: INFO: Jan 23 09:15:27.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:27.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Jan 23 09:15:27.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:27.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:27.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:27.549: INFO: Jan 23 09:15:29.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:29.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Jan 23 09:15:29.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:29.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:29.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:29.549: INFO: Jan 23 09:15:31.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:31.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Jan 23 09:15:31.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:31.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:31.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:31.552: INFO: Jan 23 09:15:33.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:33.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Jan 23 09:15:33.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:33.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:33.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:33.551: INFO: Jan 23 09:15:35.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:35.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Jan 23 09:15:35.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:35.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:35.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:35.551: INFO: Jan 23 09:15:37.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:37.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Jan 23 09:15:37.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:37.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:37.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:37.549: INFO: Jan 23 09:15:39.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:39.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Jan 23 09:15:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:39.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:39.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:39.550: INFO: Jan 23 09:15:41.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:41.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Jan 23 09:15:41.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:41.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:41.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:41.549: INFO: Jan 23 09:15:43.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:43.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Jan 23 09:15:43.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:43.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:43.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:43.549: INFO: Jan 23 09:15:45.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:45.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Jan 23 09:15:45.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:45.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:45.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:45.549: INFO: Jan 23 09:15:47.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:47.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Jan 23 09:15:47.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:47.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:47.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:47.550: INFO: Jan 23 09:15:49.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:49.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Jan 23 09:15:49.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:49.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:49.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:49.553: INFO: Jan 23 09:15:51.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:51.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Jan 23 09:15:51.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:51.559: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:51.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:51.559: INFO: Jan 23 09:15:53.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:53.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Jan 23 09:15:53.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:53.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:53.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:53.549: INFO: Jan 23 09:15:55.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:55.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Jan 23 09:15:55.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:55.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:55.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:55.549: INFO: Jan 23 09:15:57.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:57.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Jan 23 09:15:57.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:57.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:57.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:57.555: INFO: Jan 23 09:15:59.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:15:59.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Jan 23 09:15:59.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:15:59.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:15:59.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:15:59.551: INFO: Jan 23 09:16:01.786: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:01.786: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Jan 23 09:16:01.786: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:01.786: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:01.786: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:01.786: INFO: Jan 23 09:16:03.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:03.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Jan 23 09:16:03.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:03.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:03.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:03.549: INFO: Jan 23 09:16:05.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:05.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Jan 23 09:16:05.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:05.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:05.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:05.550: INFO: Jan 23 09:16:07.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:07.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Jan 23 09:16:07.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:07.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:07.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:07.550: INFO: Jan 23 09:16:09.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:09.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Jan 23 09:16:09.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:09.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:09.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:09.550: INFO: Jan 23 09:16:11.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:11.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Jan 23 09:16:11.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:11.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:11.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:11.551: INFO: Jan 23 09:16:13.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:13.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Jan 23 09:16:13.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:13.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:13.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:13.551: INFO: Jan 23 09:16:15.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:15.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Jan 23 09:16:15.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:15.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:15.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:15.551: INFO: Jan 23 09:16:17.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:17.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Jan 23 09:16:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:17.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:17.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:17.550: INFO: Jan 23 09:16:19.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:19.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Jan 23 09:16:19.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:19.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:19.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:19.553: INFO: Jan 23 09:16:21.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:21.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Jan 23 09:16:21.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:21.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:21.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:21.557: INFO: Jan 23 09:16:23.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:23.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Jan 23 09:16:23.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:23.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:23.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:23.550: INFO: Jan 23 09:16:25.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:25.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Jan 23 09:16:25.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:25.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:25.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:25.550: INFO: Jan 23 09:16:27.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:27.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Jan 23 09:16:27.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:27.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:27.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:27.550: INFO: Jan 23 09:16:29.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:29.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Jan 23 09:16:29.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:29.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:29.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:29.551: INFO: Jan 23 09:16:31.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:31.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Jan 23 09:16:31.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:31.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:31.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:31.552: INFO: Jan 23 09:16:33.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:33.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Jan 23 09:16:33.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:33.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:33.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:33.555: INFO: Jan 23 09:16:35.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:35.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Jan 23 09:16:35.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:35.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:35.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:35.553: INFO: Jan 23 09:16:37.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:37.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Jan 23 09:16:37.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:37.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:37.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:37.554: INFO: Jan 23 09:16:39.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:39.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Jan 23 09:16:39.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:39.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:39.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:39.549: INFO: Jan 23 09:16:41.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:41.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Jan 23 09:16:41.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:41.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:41.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:41.549: INFO: Jan 23 09:16:43.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:43.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Jan 23 09:16:43.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:43.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:43.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:43.550: INFO: Jan 23 09:16:45.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:45.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Jan 23 09:16:45.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:45.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:45.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:45.551: INFO: Jan 23 09:16:47.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:47.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Jan 23 09:16:47.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:47.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:47.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:47.550: INFO: Jan 23 09:16:49.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:49.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Jan 23 09:16:49.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:49.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:49.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:49.550: INFO: Jan 23 09:16:51.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:51.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Jan 23 09:16:51.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:51.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:51.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:51.552: INFO: Jan 23 09:16:53.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:53.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Jan 23 09:16:53.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:53.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:53.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:53.550: INFO: Jan 23 09:16:55.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:55.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Jan 23 09:16:55.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:55.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:55.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:55.549: INFO: Jan 23 09:16:57.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:57.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Jan 23 09:16:57.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:57.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:57.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:57.550: INFO: Jan 23 09:16:59.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:16:59.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Jan 23 09:16:59.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:16:59.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:16:59.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:16:59.555: INFO: Jan 23 09:17:01.576: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:01.576: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Jan 23 09:17:01.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:01.576: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:01.576: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:01.576: INFO: Jan 23 09:17:03.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:03.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Jan 23 09:17:03.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:03.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:03.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:03.551: INFO: Jan 23 09:17:05.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:05.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Jan 23 09:17:05.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:05.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:05.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:05.549: INFO: Jan 23 09:17:07.569: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:07.569: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Jan 23 09:17:07.569: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:07.569: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:07.569: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:07.569: INFO: Jan 23 09:17:09.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:09.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Jan 23 09:17:09.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:09.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:09.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:09.549: INFO: Jan 23 09:17:11.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:11.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Jan 23 09:17:11.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:11.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:11.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:11.550: INFO: Jan 23 09:17:13.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:13.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Jan 23 09:17:13.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:13.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:13.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:13.551: INFO: Jan 23 09:17:15.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:15.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Jan 23 09:17:15.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:15.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:15.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:15.549: INFO: Jan 23 09:17:17.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:17.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Jan 23 09:17:17.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:17.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:17.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:17.552: INFO: Jan 23 09:17:19.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:19.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Jan 23 09:17:19.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:19.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:19.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:19.551: INFO: Jan 23 09:17:21.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:21.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Jan 23 09:17:21.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:21.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:21.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:21.551: INFO: Jan 23 09:17:23.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:23.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Jan 23 09:17:23.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:23.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:23.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:23.549: INFO: Jan 23 09:17:25.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:25.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Jan 23 09:17:25.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:25.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:25.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:25.550: INFO: Jan 23 09:17:27.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:27.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Jan 23 09:17:27.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:27.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:27.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:27.550: INFO: Jan 23 09:17:29.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:29.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Jan 23 09:17:29.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:29.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:29.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:29.549: INFO: Jan 23 09:17:31.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:31.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Jan 23 09:17:31.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:31.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:31.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:31.556: INFO: Jan 23 09:17:33.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:33.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Jan 23 09:17:33.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:33.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:33.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:33.551: INFO: Jan 23 09:17:35.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:35.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Jan 23 09:17:35.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:35.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:35.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:35.551: INFO: Jan 23 09:17:37.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:37.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Jan 23 09:17:37.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:37.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:37.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:37.550: INFO: Jan 23 09:17:39.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:39.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Jan 23 09:17:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:39.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:39.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:39.550: INFO: Jan 23 09:17:41.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:41.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Jan 23 09:17:41.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:41.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:41.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:41.553: INFO: Jan 23 09:17:43.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:43.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Jan 23 09:17:43.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:43.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:43.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:43.551: INFO: Jan 23 09:17:45.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:45.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Jan 23 09:17:45.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:45.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:45.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:45.553: INFO: Jan 23 09:17:47.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:47.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Jan 23 09:17:47.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:47.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:47.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:47.552: INFO: Jan 23 09:17:49.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:49.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Jan 23 09:17:49.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:49.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:49.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:49.551: INFO: Jan 23 09:17:51.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:51.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Jan 23 09:17:51.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:51.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:51.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:51.553: INFO: Jan 23 09:17:53.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:53.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Jan 23 09:17:53.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:53.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:53.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:53.552: INFO: Jan 23 09:17:55.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:55.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Jan 23 09:17:55.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:55.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:55.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:55.554: INFO: Jan 23 09:17:57.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:57.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Jan 23 09:17:57.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:57.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:57.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:57.554: INFO: Jan 23 09:17:59.548: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:17:59.548: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Jan 23 09:17:59.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:17:59.548: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:17:59.548: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:17:59.548: INFO: Jan 23 09:18:01.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:01.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Jan 23 09:18:01.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:01.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:01.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:01.550: INFO: Jan 23 09:18:03.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:03.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Jan 23 09:18:03.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:03.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:03.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:03.550: INFO: Jan 23 09:18:05.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:05.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Jan 23 09:18:05.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:05.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:05.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:05.549: INFO: Jan 23 09:18:07.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:07.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Jan 23 09:18:07.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:07.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:07.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:07.556: INFO: Jan 23 09:18:09.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:09.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Jan 23 09:18:09.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:09.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:09.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:09.555: INFO: Jan 23 09:18:11.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:11.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Jan 23 09:18:11.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:11.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:11.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:11.554: INFO: Jan 23 09:18:13.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:13.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Jan 23 09:18:13.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:13.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:13.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:13.549: INFO: Jan 23 09:18:15.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:15.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Jan 23 09:18:15.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:15.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:15.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:15.550: INFO: Jan 23 09:18:17.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:17.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Jan 23 09:18:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:17.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:17.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:17.550: INFO: Jan 23 09:18:19.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:19.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Jan 23 09:18:19.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:19.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:19.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:19.550: INFO: Jan 23 09:18:21.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:21.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Jan 23 09:18:21.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:21.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:21.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:21.551: INFO: Jan 23 09:18:23.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:23.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Jan 23 09:18:23.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:23.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:23.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:23.555: INFO: Jan 23 09:18:25.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:25.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Jan 23 09:18:25.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:25.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:25.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:25.551: INFO: Jan 23 09:18:27.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:27.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Jan 23 09:18:27.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:27.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:27.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:27.549: INFO: Jan 23 09:18:29.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:29.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Jan 23 09:18:29.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:29.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:29.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:29.551: INFO: Jan 23 09:18:31.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:31.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Jan 23 09:18:31.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:31.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:31.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:31.551: INFO: Jan 23 09:18:33.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:33.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Jan 23 09:18:33.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:33.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:33.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:33.550: INFO: Jan 23 09:18:35.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:35.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Jan 23 09:18:35.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:35.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:35.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:35.551: INFO: Jan 23 09:18:37.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:37.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Jan 23 09:18:37.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:37.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:37.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:37.550: INFO: Jan 23 09:18:39.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:39.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Jan 23 09:18:39.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:39.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:39.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:39.551: INFO: Jan 23 09:18:41.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:41.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Jan 23 09:18:41.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:41.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:41.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:41.550: INFO: Jan 23 09:18:43.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:43.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Jan 23 09:18:43.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:43.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:43.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:43.551: INFO: Jan 23 09:18:45.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:45.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Jan 23 09:18:45.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:45.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:45.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:45.550: INFO: Jan 23 09:18:47.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:47.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Jan 23 09:18:47.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:47.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:47.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:47.549: INFO: Jan 23 09:18:49.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:49.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Jan 23 09:18:49.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:49.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:49.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:49.551: INFO: Jan 23 09:18:51.564: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:51.564: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Jan 23 09:18:51.564: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:51.564: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:51.564: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:51.564: INFO: Jan 23 09:18:53.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:53.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Jan 23 09:18:53.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:53.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:53.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:53.550: INFO: Jan 23 09:18:55.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:55.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Jan 23 09:18:55.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:55.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:55.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:55.549: INFO: Jan 23 09:18:57.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:57.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Jan 23 09:18:57.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:57.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:57.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:57.549: INFO: Jan 23 09:18:59.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:18:59.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Jan 23 09:18:59.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:18:59.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:18:59.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:18:59.549: INFO: Jan 23 09:19:01.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:01.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Jan 23 09:19:01.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:01.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:01.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:01.551: INFO: Jan 23 09:19:03.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:03.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Jan 23 09:19:03.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:03.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:03.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:03.550: INFO: Jan 23 09:19:05.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:05.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Jan 23 09:19:05.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:05.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:05.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:05.549: INFO: Jan 23 09:19:07.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:07.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Jan 23 09:19:07.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:07.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:07.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:07.552: INFO: Jan 23 09:19:09.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:09.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Jan 23 09:19:09.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:09.559: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:09.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:09.559: INFO: Jan 23 09:19:11.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:11.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Jan 23 09:19:11.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:11.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:11.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:11.550: INFO: Jan 23 09:19:13.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:13.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Jan 23 09:19:13.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:13.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:13.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:13.550: INFO: Jan 23 09:19:15.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:15.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Jan 23 09:19:15.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:15.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:15.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:15.552: INFO: Jan 23 09:19:17.548: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:17.548: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Jan 23 09:19:17.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:17.548: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:17.548: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:17.548: INFO: Jan 23 09:19:19.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:19.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Jan 23 09:19:19.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:19.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:19.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:19.550: INFO: Jan 23 09:19:21.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:21.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Jan 23 09:19:21.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:21.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:21.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:21.552: INFO: Jan 23 09:19:23.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:23.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Jan 23 09:19:23.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:23.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:23.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:23.550: INFO: Jan 23 09:19:25.549: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:25.549: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Jan 23 09:19:25.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:25.549: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:25.549: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:25.549: INFO: Jan 23 09:19:27.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:27.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Jan 23 09:19:27.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:27.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:27.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:27.554: INFO: Jan 23 09:19:29.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:29.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Jan 23 09:19:29.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:29.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:29.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:29.556: INFO: Jan 23 09:19:31.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:31.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Jan 23 09:19:31.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:31.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:31.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:31.557: INFO: Jan 23 09:19:33.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:33.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Jan 23 09:19:33.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:33.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:33.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:33.552: INFO: Jan 23 09:19:35.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:35.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Jan 23 09:19:35.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:35.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:35.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:35.552: INFO: Jan 23 09:19:37.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:37.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Jan 23 09:19:37.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:37.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:37.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:37.552: INFO: Jan 23 09:19:39.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:39.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Jan 23 09:19:39.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:39.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:39.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:39.554: INFO: Jan 23 09:19:41.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:41.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Jan 23 09:19:41.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:41.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:41.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:41.557: INFO: Jan 23 09:19:43.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:43.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Jan 23 09:19:43.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:43.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:43.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:43.557: INFO: Jan 23 09:19:45.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:45.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Jan 23 09:19:45.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:45.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:45.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:45.556: INFO: Jan 23 09:19:47.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:47.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Jan 23 09:19:47.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:47.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:47.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:47.553: INFO: Jan 23 09:19:49.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:49.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Jan 23 09:19:49.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:49.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:49.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:49.557: INFO: Jan 23 09:19:51.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:51.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Jan 23 09:19:51.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:51.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:51.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:51.557: INFO: Jan 23 09:19:53.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:53.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Jan 23 09:19:53.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:53.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:53.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:53.557: INFO: Jan 23 09:19:55.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:55.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Jan 23 09:19:55.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:55.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:55.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:55.554: INFO: Jan 23 09:19:57.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:57.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Jan 23 09:19:57.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:57.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:57.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:57.553: INFO: Jan 23 09:19:59.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:19:59.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Jan 23 09:19:59.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:19:59.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:19:59.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:19:59.555: INFO: Jan 23 09:20:01.565: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:01.565: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Jan 23 09:20:01.565: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:01.565: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:01.565: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:01.565: INFO: Jan 23 09:20:03.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:03.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Jan 23 09:20:03.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:03.561: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:03.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:03.561: INFO: Jan 23 09:20:05.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:05.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Jan 23 09:20:05.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:05.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:05.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:05.555: INFO: Jan 23 09:20:07.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:07.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Jan 23 09:20:07.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:07.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:07.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:07.556: INFO: Jan 23 09:20:09.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:09.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Jan 23 09:20:09.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:09.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:09.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:09.553: INFO: Jan 23 09:20:11.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:11.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Jan 23 09:20:11.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:11.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:11.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:11.555: INFO: Jan 23 09:20:13.562: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:13.562: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Jan 23 09:20:13.562: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:13.562: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:13.562: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:13.562: INFO: Jan 23 09:20:15.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:15.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Jan 23 09:20:15.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:15.558: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:15.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:15.558: INFO: Jan 23 09:20:17.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:17.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Jan 23 09:20:17.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:17.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:17.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:17.555: INFO: Jan 23 09:20:19.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:19.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Jan 23 09:20:19.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:19.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:19.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:19.557: INFO: Jan 23 09:20:21.564: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:21.564: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Jan 23 09:20:21.564: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:21.564: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:21.564: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:21.564: INFO: Jan 23 09:20:23.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:23.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Jan 23 09:20:23.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:23.561: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:23.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:23.561: INFO: Jan 23 09:20:25.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:25.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Jan 23 09:20:25.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:25.558: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:25.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:25.558: INFO: Jan 23 09:20:27.560: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:27.560: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Jan 23 09:20:27.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:27.560: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:27.560: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:27.560: INFO: Jan 23 09:20:29.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:29.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Jan 23 09:20:29.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:29.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:29.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:29.556: INFO: Jan 23 09:20:31.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:31.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Jan 23 09:20:31.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:31.559: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:31.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:31.559: INFO: Jan 23 09:20:33.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:33.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Jan 23 09:20:33.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:33.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:33.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:33.556: INFO: Jan 23 09:20:35.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:35.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Jan 23 09:20:35.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:35.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:35.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:35.554: INFO: Jan 23 09:20:37.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:37.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Jan 23 09:20:37.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:37.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:37.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:37.555: INFO: Jan 23 09:20:39.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:39.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Jan 23 09:20:39.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:39.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:39.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:39.556: INFO: Jan 23 09:20:41.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:41.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Jan 23 09:20:41.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:41.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:41.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:41.555: INFO: Jan 23 09:20:43.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:43.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Jan 23 09:20:43.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:43.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:43.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:43.553: INFO: Jan 23 09:20:45.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:45.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Jan 23 09:20:45.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:45.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:45.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:45.554: INFO: Jan 23 09:20:47.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:47.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Jan 23 09:20:47.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:47.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:47.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:47.553: INFO: Jan 23 09:20:49.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:49.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Jan 23 09:20:49.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:49.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:49.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:49.555: INFO: Jan 23 09:20:51.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:51.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Jan 23 09:20:51.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:51.561: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:51.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:51.561: INFO: Jan 23 09:20:53.569: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:53.569: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Jan 23 09:20:53.569: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:53.569: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:53.569: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:53.569: INFO: Jan 23 09:20:55.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:55.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Jan 23 09:20:55.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:55.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:55.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:55.557: INFO: Jan 23 09:20:57.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:57.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Jan 23 09:20:57.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:57.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:57.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:57.557: INFO: Jan 23 09:20:59.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:20:59.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Jan 23 09:20:59.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:20:59.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:20:59.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:20:59.553: INFO: Jan 23 09:21:01.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:01.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Jan 23 09:21:01.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:01.558: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:01.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:01.558: INFO: Jan 23 09:21:03.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:03.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Jan 23 09:21:03.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:03.561: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:03.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:03.561: INFO: Jan 23 09:21:05.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:05.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Jan 23 09:21:05.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:05.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:05.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:05.553: INFO: Jan 23 09:21:07.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:07.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Jan 23 09:21:07.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:07.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:07.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:07.553: INFO: Jan 23 09:21:09.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:09.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Jan 23 09:21:09.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:09.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:09.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:09.555: INFO: Jan 23 09:21:11.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:11.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Jan 23 09:21:11.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:11.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:11.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:11.556: INFO: Jan 23 09:21:13.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:13.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Jan 23 09:21:13.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:13.559: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:13.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:13.559: INFO: Jan 23 09:21:15.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:15.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Jan 23 09:21:15.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:15.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:15.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:15.556: INFO: Jan 23 09:21:17.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:17.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Jan 23 09:21:17.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:17.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:17.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:17.554: INFO: Jan 23 09:21:19.563: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:19.563: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Jan 23 09:21:19.563: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:19.563: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:19.563: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:19.563: INFO: Jan 23 09:21:21.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:21.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Jan 23 09:21:21.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:21.561: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:21.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:21.561: INFO: Jan 23 09:21:23.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:23.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Jan 23 09:21:23.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:23.558: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:23.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:23.558: INFO: Jan 23 09:21:25.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:25.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Jan 23 09:21:25.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:25.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:25.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:25.553: INFO: Jan 23 09:21:27.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:27.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Jan 23 09:21:27.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:27.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:27.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:27.553: INFO: Jan 23 09:21:29.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:29.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Jan 23 09:21:29.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:29.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:29.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:29.551: INFO: Jan 23 09:21:31.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:31.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Jan 23 09:21:31.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:31.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:31.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:31.553: INFO: Jan 23 09:21:33.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:33.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Jan 23 09:21:33.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:33.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:33.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:33.556: INFO: Jan 23 09:21:35.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:35.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Jan 23 09:21:35.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:35.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:35.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:35.554: INFO: Jan 23 09:21:37.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:37.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Jan 23 09:21:37.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:37.558: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:37.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:37.558: INFO: Jan 23 09:21:39.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:39.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Jan 23 09:21:39.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:39.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:39.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:39.554: INFO: Jan 23 09:21:41.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:41.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Jan 23 09:21:41.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:41.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:41.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:41.553: INFO: Jan 23 09:21:43.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:43.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Jan 23 09:21:43.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:43.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:43.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:43.556: INFO: Jan 23 09:21:45.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:45.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Jan 23 09:21:45.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:45.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:45.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:45.557: INFO: Jan 23 09:21:47.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:47.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Jan 23 09:21:47.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:47.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:47.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:47.552: INFO: Jan 23 09:21:49.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:49.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Jan 23 09:21:49.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:49.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:49.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:49.554: INFO: Jan 23 09:21:51.560: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:51.560: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Jan 23 09:21:51.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:51.560: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:51.560: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:51.560: INFO: Jan 23 09:21:53.562: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:53.562: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Jan 23 09:21:53.562: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:53.562: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:53.562: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:53.562: INFO: Jan 23 09:21:55.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:55.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Jan 23 09:21:55.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:55.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:55.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:55.558: INFO: Jan 23 09:21:57.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:57.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Jan 23 09:21:57.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:57.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:57.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:57.552: INFO: Jan 23 09:21:59.552: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:21:59.552: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Jan 23 09:21:59.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:21:59.552: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:21:59.552: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:21:59.552: INFO: Jan 23 09:22:01.563: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:01.563: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Jan 23 09:22:01.563: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:01.563: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:01.563: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:01.563: INFO: Jan 23 09:22:03.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:03.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Jan 23 09:22:03.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:03.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:03.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:03.556: INFO: Jan 23 09:22:05.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:05.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Jan 23 09:22:05.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:05.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:05.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:05.555: INFO: Jan 23 09:22:07.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:07.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Jan 23 09:22:07.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:07.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:07.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:07.553: INFO: Jan 23 09:22:09.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:09.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Jan 23 09:22:09.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:09.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:09.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:09.553: INFO: Jan 23 09:22:11.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:11.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Jan 23 09:22:11.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:11.559: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:11.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:11.559: INFO: Jan 23 09:22:13.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:13.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Jan 23 09:22:13.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:13.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:13.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:13.554: INFO: Jan 23 09:22:15.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:15.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Jan 23 09:22:15.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:15.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:15.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:15.556: INFO: Jan 23 09:22:17.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:17.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Jan 23 09:22:17.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:17.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:17.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:17.555: INFO: Jan 23 09:22:19.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:19.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Jan 23 09:22:19.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:19.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:19.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:19.556: INFO: Jan 23 09:22:21.558: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:21.558: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Jan 23 09:22:21.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:21.558: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:21.558: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:21.558: INFO: Jan 23 09:22:23.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:23.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Jan 23 09:22:23.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:23.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:23.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:23.554: INFO: Jan 23 09:22:25.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:25.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Jan 23 09:22:25.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:25.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:25.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:25.553: INFO: Jan 23 09:22:27.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:27.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Jan 23 09:22:27.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:27.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:27.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:27.554: INFO: Jan 23 09:22:29.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:29.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Jan 23 09:22:29.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:29.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:29.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:29.550: INFO: Jan 23 09:22:31.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:31.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Jan 23 09:22:31.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:31.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:31.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:31.553: INFO: Jan 23 09:22:33.562: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:33.562: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Jan 23 09:22:33.562: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:33.562: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:33.562: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:33.562: INFO: Jan 23 09:22:35.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:35.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Jan 23 09:22:35.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:35.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:35.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:35.557: INFO: Jan 23 09:22:37.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:37.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Jan 23 09:22:37.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:37.561: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:37.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:37.561: INFO: Jan 23 09:22:39.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:39.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Jan 23 09:22:39.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:39.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:39.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:39.555: INFO: Jan 23 09:22:41.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:41.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Jan 23 09:22:41.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:41.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:41.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:41.556: INFO: Jan 23 09:22:43.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:43.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Jan 23 09:22:43.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:43.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:43.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:43.555: INFO: Jan 23 09:22:45.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:45.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Jan 23 09:22:45.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:45.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:45.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:45.557: INFO: Jan 23 09:22:47.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:47.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Jan 23 09:22:47.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:47.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:47.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:47.554: INFO: Jan 23 09:22:49.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:49.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Jan 23 09:22:49.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:49.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:49.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:49.557: INFO: Jan 23 09:22:51.559: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:51.559: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Jan 23 09:22:51.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:51.559: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:51.559: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:51.559: INFO: Jan 23 09:22:53.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:53.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Jan 23 09:22:53.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:53.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:53.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:53.554: INFO: Jan 23 09:22:55.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:55.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Jan 23 09:22:55.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:55.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:55.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:55.554: INFO: Jan 23 09:22:57.553: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:57.553: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Jan 23 09:22:57.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:57.553: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:57.553: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:57.553: INFO: Jan 23 09:22:59.551: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:22:59.551: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Jan 23 09:22:59.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:22:59.551: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:22:59.551: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:22:59.551: INFO: Jan 23 09:23:01.555: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:23:01.555: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Jan 23 09:23:01.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:23:01.555: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:23:01.555: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:23:01.555: INFO: Jan 23 09:23:03.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:23:03.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Jan 23 09:23:03.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:23:03.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:23:03.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:23:03.556: INFO: Jan 23 09:23:05.556: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:23:05.556: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Jan 23 09:23:05.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:23:05.556: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:23:05.556: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:23:05.556: INFO: Jan 23 09:23:07.554: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:23:07.554: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Jan 23 09:23:07.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:23:07.554: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:23:07.554: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:23:07.554: INFO: Jan 23 09:23:09.550: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:23:09.550: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Jan 23 09:23:09.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:23:09.550: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:23:09.550: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:23:09.550: INFO: Jan 23 09:23:11.557: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:23:11.557: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Jan 23 09:23:11.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:23:11.557: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:23:11.557: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:23:11.557: INFO: Jan 23 09:23:13.561: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:23:13.561: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 23 09:23:13.561: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:23:13.561: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:23:13.561: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:23:13.561: INFO: Jan 23 09:23:13.814: INFO: The status of Pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 23 09:23:13.814: INFO: 13 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 23 09:23:13.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 23 09:23:13.814: INFO: POD NODE PHASE GRACE CONDITIONS Jan 23 09:23:13.814: INFO: kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] Jan 23 09:23:13.814: INFO: [1mSTEP:[0m Collecting events from namespace "kube-system". [38;5;243m@ 01/23/23 09:23:13.814[0m ... skipping 19 lines ... Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-tvxsr Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-946zt Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-946zt Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:42 +0000 UTC - event for kube-proxy-946zt: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-946zt to capz-conf-y1oqv9-control-plane-9wsvb Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:43 +0000 UTC - event for kube-proxy-946zt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Failed: Error: cannot find volume "kube-proxy" to mount into container "kube-proxy" Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:43 +0000 UTC - event for kube-proxy-946zt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:43 +0000 UTC - event for kube-proxy-946zt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Container image "gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.1196_724497cda467b7" already present on machine Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:44 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Killing: Stopping container kube-controller-manager Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:44 +0000 UTC - event for kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Killing: Stopping container kube-scheduler Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:56 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "capzci.azurecr.io/kube-controller-manager:v1.27.0-alpha.0.1204_877c0188a44185" Jan 23 09:23:13.891: INFO: At 2023-01-23 09:09:57 +0000 UTC - event for kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "capzci.azurecr.io/kube-scheduler:v1.27.0-alpha.0.1204_877c0188a44185" Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:01 +0000 UTC - event for kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container kube-controller-manager ... skipping 20 lines ... Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:27 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container upgrade-ipam Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:28 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container upgrade-ipam Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:31 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:31 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container install-cni Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:31 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container install-cni Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:33 +0000 UTC - event for kube-proxy-s7wrt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185" in 5.944252602s (12.3873728s including waiting) Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:34 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "ca8f39c57f0b4fc0e0c799c43d07c10d1220e36762c433879157a7ab4bceded1": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:34 +0000 UTC - event for kube-proxy-s7wrt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container kube-proxy Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:34 +0000 UTC - event for kube-proxy-s7wrt: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container kube-proxy Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/calico-kube-controllers-657b584867-c6nrc Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "fc224f7e6e7c67523299b7cc714660912423b3553d8eee0b9014cba0d0bf6d37": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-56f4c55bf9-9l9fx Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "8a9c89995202d7f51715db6934764c96c59bf7bb832ecdd0da47101b37a213a8": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-56f4c55bf9-tvxsr Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for metrics-server-c9574f845-cwq45: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-c9574f845-cwq45 Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:35 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a3e766dcfad2c005fb90e660919f1e49502df18adb3df401ce8e2fd3e9616d40": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:42 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.152507128s (7.152512828s including waiting) Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:43 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:43 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container calico-node Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:43 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container calico-node Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:44 +0000 UTC - event for calico-node-klq6b: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:45 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:47 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container coredns Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:47 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container coredns Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:47 +0000 UTC - event for coredns-56f4c55bf9-9l9fx: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:49 +0000 UTC - event for coredns-56f4c55bf9-tvxsr: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container coredns ... skipping 2 lines ... Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:50 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0" Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:50 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.748253971s (4.748410873s including waiting) Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:50 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container metrics-server Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:50 +0000 UTC - event for metrics-server-c9574f845-cwq45: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container metrics-server Jan 23 09:23:13.891: INFO: At 2023-01-23 09:10:56 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Started: Started container calico-kube-controllers Jan 23 09:23:13.892: INFO: At 2023-01-23 09:10:56 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Created: Created container calico-kube-controllers Jan 23 09:23:13.892: INFO: At 2023-01-23 09:10:56 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Unhealthy: Readiness probe failed: initialized to false Jan 23 09:23:13.892: INFO: At 2023-01-23 09:10:56 +0000 UTC - event for calico-kube-controllers-657b584867-c6nrc: {kubelet capz-conf-y1oqv9-control-plane-9wsvb} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.936713244s (6.325842494s including waiting) Jan 23 09:23:13.892: INFO: At 2023-01-23 09:11:52 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-v2pkj Jan 23 09:23:13.892: INFO: At 2023-01-23 09:11:52 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-xdqh8 Jan 23 09:23:13.892: INFO: At 2023-01-23 09:11:58 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 23 09:23:13.892: INFO: At 2023-01-23 09:11:58 +0000 UTC - event for kube-proxy-xdqh8: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185" ... skipping 7 lines ... Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:11 +0000 UTC - event for kube-proxy-xdqh8: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185" in 6.289183447s (12.937268171s including waiting) Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:12 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:12 +0000 UTC - event for kube-proxy-xdqh8: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Started: Started container kube-proxy Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:19 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Created: Created container calico-node Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:19 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.153259189s (7.153263689s including waiting) Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:19 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Started: Started container calico-node Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:20 +0000 UTC - event for calico-node-v2pkj: {kubelet capz-conf-y1oqv9-md-0-jmtm2} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:39 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-vnrl7 Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:39 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-cn4p2 Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:56 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 23 09:23:13.892: INFO: At 2023-01-23 09:12:56 +0000 UTC - event for kube-proxy-cn4p2: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1204_877c0188a44185" Jan 23 09:23:13.892: INFO: At 2023-01-23 09:13:03 +0000 UTC - event for calico-node-vnrl7: {kubelet capz-conf-y1oqv9-md-0-z5lhc} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.118557316s (7.118740523s including waiting) ... skipping 83 lines ... Jan 23 09:23:16.795: INFO: Container calico-node ready: true, restart count 0 Jan 23 09:23:16.795: INFO: kube-proxy-cn4p2 started at 2023-01-23 09:12:43 +0000 UTC (0+1 container statuses recorded) Jan 23 09:23:16.795: INFO: Container kube-proxy ready: true, restart count 0 Jan 23 09:23:17.417: INFO: Latency metrics for node capz-conf-y1oqv9-md-0-z5lhc Jan 23 09:23:17.626: INFO: Running kubectl logs on non-ready containers in kube-system Jan 23 09:23:17.987: INFO: Failed to get logs of pod kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb) Jan 23 09:23:17.987: INFO: Logs of kube-system/kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb:kube-apiserver on node capz-conf-y1oqv9-control-plane-9wsvb Jan 23 09:23:17.987: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb:kube-apiserver [38;5;9m[FAILED][0m in [SynchronizedBeforeSuite] - test/e2e/e2e.go:251 [38;5;243m@ 01/23/23 09:23:17.987[0m [38;5;243m<< Timeline[0m [38;5;9m[FAILED] Error waiting for all pods to be running and ready: 1 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s POD NODE PHASE GRACE CONDITIONS kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb capz-conf-y1oqv9-control-plane-9wsvb Pending [] [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:251[0m [38;5;243m@ 01/23/23 09:23:17.987[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.132 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.023[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.337 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.027[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.285 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.023[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.319 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.023[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.355 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.023[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.369 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.027[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.361 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.037[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.350 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.027[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.243 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.041[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.384 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.041[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.341 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.046[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.161 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.045[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.361 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.044[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.395 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.046[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.151 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.047[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.321 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.045[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.124 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.046[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.310 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.044[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.354 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.046[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.117 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.046[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.144 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.041[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.367 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.045[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.168 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.047[0m [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [605.356 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. [0m [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/23/23 09:23:18.047[0m [38;5;243m------------------------------[0m [38;5;9m[1mSummarizing 25 Failures:[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;9m[FAIL][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:251[0m [38;5;9m[1mRan 0 of 7075 Specs in 605.992 seconds[0m [38;5;9m[1mFAIL![0m -- [38;5;14m[1mA BeforeSuite node failed so all tests were skipped.[0m I0123 09:13:10.273207 12 e2e.go:126] Starting e2e run "ab04acf0-1f3f-475d-9b44-3c4d86380839" on Ginkgo node 1 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.96s) FAIL I0123 09:13:10.532189 14 e2e.go:126] Starting e2e run "06ab23fe-decc-4c4c-8f27-259686c0e0ac" on Ginkgo node 2 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.56s) FAIL I0123 09:13:10.341681 16 e2e.go:126] Starting e2e run "d974feb6-b057-4def-83da-c54161511cfc" on Ginkgo node 3 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.74s) FAIL I0123 09:13:10.371830 18 e2e.go:126] Starting e2e run "35e0c578-b71b-44f4-8286-a9396c75cd70" on Ginkgo node 4 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.72s) FAIL I0123 09:13:10.378075 31 e2e.go:126] Starting e2e run "7c815b96-3bed-4999-864b-b3e77785cf15" on Ginkgo node 5 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.73s) FAIL I0123 09:13:10.615539 39 e2e.go:126] Starting e2e run "2c52a052-1032-428f-9c1f-6f4b34888f7b" on Ginkgo node 6 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.47s) FAIL I0123 09:13:10.614856 49 e2e.go:126] Starting e2e run "f2944f50-fe64-405e-b429-4437a3ad7e51" on Ginkgo node 7 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.54s) FAIL I0123 09:13:10.769273 56 e2e.go:126] Starting e2e run "1668723a-e377-43b5-a487-0528d5f27127" on Ginkgo node 8 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.31s) FAIL I0123 09:13:10.731374 68 e2e.go:126] Starting e2e run "b4660a6d-2092-4479-9a20-7e651842577c" on Ginkgo node 9 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.33s) FAIL I0123 09:13:10.671773 78 e2e.go:126] Starting e2e run "db22290d-c831-46e9-95a9-f275aedfe377" on Ginkgo node 10 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.44s) FAIL I0123 09:13:10.684951 80 e2e.go:126] Starting e2e run "7c8554a4-e527-4bce-a947-5afafc0b04a1" on Ginkgo node 11 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.40s) FAIL I0123 09:13:11.076568 89 e2e.go:126] Starting e2e run "5117cc59-88fa-41cc-b47f-aea2fd0adb88" on Ginkgo node 12 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.03s) FAIL I0123 09:13:10.956134 103 e2e.go:126] Starting e2e run "4e216bc0-3c1d-479d-bbbf-caccfce50110" on Ginkgo node 13 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.13s) FAIL I0123 09:13:10.783904 105 e2e.go:126] Starting e2e run "663863fc-f654-4513-8b96-713e092e22dc" on Ginkgo node 14 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.30s) FAIL I0123 09:13:10.976696 111 e2e.go:126] Starting e2e run "b0219db3-47b1-4eb9-bb90-1f5be4a4bb73" on Ginkgo node 15 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.11s) FAIL I0123 09:13:11.092975 121 e2e.go:126] Starting e2e run "902754d3-1764-4d0c-b826-22a4f094538e" on Ginkgo node 16 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.02s) FAIL I0123 09:13:10.809614 136 e2e.go:126] Starting e2e run "49260d45-1c52-41aa-a5ab-a301ca759c24" on Ginkgo node 17 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.27s) FAIL I0123 09:13:10.768001 142 e2e.go:126] Starting e2e run "ac5f46bf-7845-4369-8125-691d815ef8b9" on Ginkgo node 18 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.29s) FAIL I0123 09:13:11.112854 145 e2e.go:126] Starting e2e run "4008d3fa-406e-434b-8771-13ef50a72871" on Ginkgo node 19 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (606.98s) FAIL I0123 09:13:10.964978 157 e2e.go:126] Starting e2e run "2e1cf1da-edb1-4d67-b8f6-cc3e52ecb417" on Ginkgo node 20 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.12s) FAIL I0123 09:13:10.638684 163 e2e.go:126] Starting e2e run "962af21f-1ad8-4755-895d-2f4059812fdd" on Ginkgo node 21 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (607.45s) FAIL I0123 09:13:11.259060 180 e2e.go:126] Starting e2e run "00948ca1-346e-4293-bf25-83e7810ea400" on Ginkgo node 22 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (606.83s) FAIL I0123 09:13:11.204658 201 e2e.go:126] Starting e2e run "0f9675d6-6946-4426-a259-d9b2bab1f9d1" on Ginkgo node 23 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (606.87s) FAIL I0123 09:13:11.216401 206 e2e.go:126] Starting e2e run "218baced-12eb-42ef-806f-4a4ec8e31973" on Ginkgo node 24 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (606.88s) FAIL I0123 09:13:11.209608 210 e2e.go:126] Starting e2e run "df40a619-2485-485b-b371-4c13036ad0dc" on Ginkgo node 25 [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m [38;5;11m--ginkgo.progress is deprecated . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m --- FAIL: TestE2E (606.87s) FAIL Ginkgo ran 1 suite in 10m8.505951188s Test Suite Failed [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11m--slowSpecThreshold is deprecated use --slow-spec-threshold instead and pass in a duration string (e.g. '5s', not '5.0')[0m [1mLearn more at:[0m [38;5;14m[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed--slowspecthreshold[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0[0m [AfterEach] Conformance Tests /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:237 Jan 23 09:23:18.831: INFO: FAILED! Jan 23 09:23:18.831: INFO: Cleaning up after "Conformance Tests conformance-tests" spec [1mSTEP[0m: Dumping logs from the "capz-conf-y1oqv9" workload cluster [1mSTEP[0m: Dumping workload cluster capz-conf-y1oqv9/capz-conf-y1oqv9 logs Jan 23 09:23:18.949: INFO: Collecting logs for Linux node capz-conf-y1oqv9-control-plane-9wsvb in cluster capz-conf-y1oqv9 in namespace capz-conf-y1oqv9 Jan 23 09:23:33.372: INFO: Collecting boot logs for AzureMachine capz-conf-y1oqv9-control-plane-9wsvb ... skipping 19 lines ... [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-cn4p2 [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb [1mSTEP[0m: Collecting events for Pod kube-system/coredns-56f4c55bf9-tvxsr [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-y1oqv9-control-plane-9wsvb, container kube-controller-manager [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-s7wrt [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-capz-conf-y1oqv9-control-plane-9wsvb, container etcd [1mSTEP[0m: failed to find events of Pod "kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb, container kube-apiserver [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-s7wrt, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/etcd-capz-conf-y1oqv9-control-plane-9wsvb [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-cn4p2, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/metrics-server-c9574f845-cwq45 [1mSTEP[0m: Creating log watcher for controller kube-system/metrics-server-c9574f845-cwq45, container metrics-server ... skipping 3 lines ... [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-56f4c55bf9-9l9fx, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-56f4c55bf9-tvxsr, container coredns [1mSTEP[0m: Fetching kube-system pod logs took 706.411727ms [1mSTEP[0m: Dumping workload cluster capz-conf-y1oqv9/capz-conf-y1oqv9 Azure activity log [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb, container kube-scheduler [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-capz-conf-y1oqv9-control-plane-9wsvb [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb, container kube-apiserver: container "kube-apiserver" in pod "kube-apiserver-capz-conf-y1oqv9-control-plane-9wsvb" is not available [1mSTEP[0m: Fetching activity logs took 4.264050725s Jan 23 09:23:57.766: INFO: Dumping all the Cluster API resources in the "capz-conf-y1oqv9" namespace Jan 23 09:23:58.135: INFO: Deleting all clusters in the capz-conf-y1oqv9 namespace [1mSTEP[0m: Deleting cluster capz-conf-y1oqv9 INFO: Waiting for the Cluster capz-conf-y1oqv9/capz-conf-y1oqv9 to be deleted [1mSTEP[0m: Waiting for cluster capz-conf-y1oqv9 to be deleted ... skipping 5 lines ... [91m[1m• Failure [1405.663 seconds][0m Conformance Tests [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:44[0m [91m[1mconformance-tests [Measurement][0m [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99[0m [91mUnexpected error: <*errors.withStack | 0xc0029c47e0>: { error: <*errors.withMessage | 0xc000450280>{ cause: <*errors.errorString | 0xc001a5e5c0>{ s: "error container run failed with exit code 1", }, msg: "Unable to run conformance tests", }, stack: [0x2ef56b8, 0x32ed787, 0x1878d97, 0x32ed553, 0x143a565, 0x1439a5c, 0x187a5fc, 0x187b611, 0x187b005, 0x187a69b, 0x1880929, 0x1880312, 0x188cc11, 0x188c936, 0x188bf85, 0x188e645, 0x189bea9, 0x189bcbe, 0x32f26f8, 0x148fccb, 0x13c7801], } Unable to run conformance tests: error container run failed with exit code 1 occurred[0m /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:232 [91mFull Stack Trace[0m sigs.k8s.io/cluster-api-provider-azure/test/e2e.glob..func3.2.2() ... skipping 41 lines ... JUnit report was created: /logs/artifacts/junit.e2e_suite.1.xml [91m[1mSummarizing 1 Failure:[0m [91m[1m[Fail] [0m[90mConformance Tests [0m[91m[1m[Measurement] conformance-tests [0m [37m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:232[0m [1m[91mRan 1 of 25 Specs in 1560.121 seconds[0m [1m[91mFAIL![0m -- [32m[1m0 Passed[0m | [91m[1m1 Failed[0m | [33m[1m0 Pending[0m | [36m[1m24 Skipped[0m --- FAIL: TestE2E (1560.14s) FAIL [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [1m[38;5;10mGinkgo 2.0[0m is under active development and will introduce several new features, improvements, and a small handful of breaking changes. A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021. [1mPlease give the RC a try and send us feedback![0m - To learn more, view the migration guide at [38;5;14m[4mhttps://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md[0m ... skipping 13 lines ... [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=1.16.5[0m Ginkgo ran 1 suite in 28m7.031109538s Test Suite Failed [38;5;228mGinkgo 2.0 is coming soon![0m [38;5;228m==========================[0m [1m[38;5;10mGinkgo 2.0[0m is under active development and will introduce several new features, improvements, and a small handful of breaking changes. A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021. [1mPlease give the RC a try and send us feedback![0m - To learn more, view the migration guide at [38;5;14m[4mhttps://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md[0m - For instructions on using the Release Candidate visit [38;5;14m[4mhttps://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta[0m - To comment, chime in at [38;5;14m[4mhttps://github.com/onsi/ginkgo/issues/711[0m To [1m[38;5;204msilence this notice[0m, set the environment variable: [1mACK_GINKGO_RC=true[0m Alternatively you can: [1mtouch $HOME/.ack-ginkgo-rc[0m make[2]: *** [Makefile:652: test-e2e-run] Error 1 make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[1]: *** [Makefile:669: test-e2e-local] Error 2 make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make: *** [Makefile:679: test-conformance] Error 2 ================ REDACTING LOGS ================ All sensitive variables are redacted + EXIT_VALUE=2 + set +o xtrace Cleaning up after docker in docker. ================================================================================ ... skipping 7 lines ...