Recent runs || View in Spyglass
PR | princepereira: Windows Kube-Proxy implementation of ProxyTerminatingEndpoints feature |
Result | SUCCESS |
Tests | 4 failed / 6 succeeded |
Started | |
Elapsed | 49m3s |
Revision | a48cd77756e800a5f0abb35bc5b1c06637822bae |
Refs |
113776 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:249 k8s.io/kubernetes/test/e2e.setupSuite() test/e2e/e2e.go:249 +0x4de k8s.io/kubernetes/test/e2e.glob..func1() test/e2e/e2e.go:81 +0x8f reflect.Value.call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0x75b6e72, 0x4}, {0xc0000b7f20, 0x0, 0x0?}) /usr/local/go/src/reflect/value.go:584 +0x8c5 reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0xc0000b7f20?, 0x0?, 0x0?}) /usr/local/go/src/reflect/value.go:368 +0xbcfrom junit.kubetest.01.xml
[SynchronizedBeforeSuite] TOP-LEVEL test/e2e/e2e.go:77 Nov 18 11:14:47.895: INFO: >>> kubeConfig: /tmp/kubeconfig Nov 18 11:14:47.919: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Nov 18 11:14:48.114: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Nov 18 11:14:48.245: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:48.245: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:48.245: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:48.245: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Nov 18 11:14:48.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:14:48.245: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:14:48.245: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:48.245: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:48.245: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:48.245: INFO: Nov 18 11:14:50.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:50.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:50.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:50.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Nov 18 11:14:50.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:14:50.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:14:50.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:50.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:50.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:50.370: INFO: Nov 18 11:14:52.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:52.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:52.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:52.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Nov 18 11:14:52.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:14:52.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:14:52.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:52.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:52.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:52.370: INFO: Nov 18 11:14:54.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:54.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:54.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:54.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Nov 18 11:14:54.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:14:54.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:14:54.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:54.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:54.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:54.368: INFO: Nov 18 11:14:56.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:56.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:56.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:56.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Nov 18 11:14:56.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:14:56.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:14:56.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:56.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:56.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:56.369: INFO: Nov 18 11:14:58.372: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:58.372: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:58.372: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:14:58.372: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Nov 18 11:14:58.372: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:14:58.372: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:14:58.372: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:58.372: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:58.372: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:14:58.372: INFO: Nov 18 11:15:00.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:00.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:00.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:00.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Nov 18 11:15:00.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:00.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:00.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:00.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:00.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:00.369: INFO: Nov 18 11:15:02.370: INFO: The status of Pod calico-node-windows-pw4bf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:02.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:02.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:02.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:02.370: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Nov 18 11:15:02.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:02.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:02.370: INFO: calico-node-windows-pw4bf capz-conf-84hb2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:16 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:15:01 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:15:01 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:49 +0000 UTC }] Nov 18 11:15:02.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:02.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:02.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:02.370: INFO: Nov 18 11:15:04.370: INFO: The status of Pod calico-node-windows-pw4bf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:04.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:04.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:04.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:04.370: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Nov 18 11:15:04.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:04.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:04.370: INFO: calico-node-windows-pw4bf capz-conf-84hb2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:16 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:15:01 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:15:01 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:49 +0000 UTC }] Nov 18 11:15:04.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:04.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:04.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:04.370: INFO: Nov 18 11:15:06.371: INFO: The status of Pod calico-node-windows-pw4bf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:06.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:06.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:06.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:06.371: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Nov 18 11:15:06.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:06.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:06.371: INFO: calico-node-windows-pw4bf capz-conf-84hb2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:16 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:15:01 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:15:01 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:49 +0000 UTC }] Nov 18 11:15:06.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:06.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:06.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:06.371: INFO: Nov 18 11:15:08.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:08.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:08.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:08.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Nov 18 11:15:08.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:08.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:08.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:08.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:08.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:08.368: INFO: Nov 18 11:15:10.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:10.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:10.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:10.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Nov 18 11:15:10.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:10.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:10.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:10.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:10.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:10.371: INFO: Nov 18 11:15:12.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:12.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:12.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:12.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Nov 18 11:15:12.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:12.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:12.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:12.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:12.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:12.371: INFO: Nov 18 11:15:14.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:14.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:14.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:14.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Nov 18 11:15:14.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:14.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:14.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:14.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:14.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:14.371: INFO: Nov 18 11:15:16.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:16.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:16.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:16.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Nov 18 11:15:16.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:16.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:16.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:16.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:16.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:16.369: INFO: Nov 18 11:15:18.373: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:18.373: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:18.373: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:18.373: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Nov 18 11:15:18.373: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:18.373: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:18.373: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:18.373: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:18.373: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:18.373: INFO: Nov 18 11:15:20.389: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:20.389: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:20.389: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:20.389: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Nov 18 11:15:20.389: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:20.389: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:20.389: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:20.389: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:20.389: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:20.389: INFO: Nov 18 11:15:22.383: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:22.383: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:22.383: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:22.383: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Nov 18 11:15:22.383: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:22.383: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:22.383: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:22.383: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:22.383: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:22.383: INFO: Nov 18 11:15:24.384: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:24.384: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:24.384: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:24.384: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Nov 18 11:15:24.384: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:24.384: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:24.384: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:24.384: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:24.384: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:24.385: INFO: Nov 18 11:15:26.384: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:26.384: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:26.384: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:26.384: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Nov 18 11:15:26.384: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:26.384: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:26.384: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:26.384: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:26.384: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:26.384: INFO: Nov 18 11:15:28.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:28.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:28.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:28.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Nov 18 11:15:28.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:28.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:28.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:28.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:28.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:28.382: INFO: Nov 18 11:15:30.390: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:30.390: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:30.390: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:30.390: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Nov 18 11:15:30.390: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:30.390: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:30.390: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:30.390: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:30.390: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:30.390: INFO: Nov 18 11:15:32.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:32.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:32.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:32.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Nov 18 11:15:32.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:32.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:32.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:32.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:32.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:32.382: INFO: Nov 18 11:15:34.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:34.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:34.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:34.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Nov 18 11:15:34.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:34.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:34.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:34.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:34.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:34.382: INFO: Nov 18 11:15:36.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:36.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:36.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:36.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Nov 18 11:15:36.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:36.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:36.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:36.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:36.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:36.382: INFO: Nov 18 11:15:38.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:38.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:38.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:38.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Nov 18 11:15:38.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:38.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:38.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:38.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:38.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:38.382: INFO: Nov 18 11:15:40.385: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:40.385: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:40.385: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:40.385: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Nov 18 11:15:40.385: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:40.385: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:40.385: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:40.385: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:40.385: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:40.385: INFO: Nov 18 11:15:42.387: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:42.387: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:42.387: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:42.387: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Nov 18 11:15:42.387: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:42.387: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:42.387: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:42.387: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:42.387: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:42.387: INFO: Nov 18 11:15:44.384: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:44.384: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:44.384: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:44.384: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Nov 18 11:15:44.384: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:44.384: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:44.384: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:44.384: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:44.384: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:44.384: INFO: Nov 18 11:15:46.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:46.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:46.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:46.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Nov 18 11:15:46.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:46.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:46.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:46.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:46.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:46.382: INFO: Nov 18 11:15:48.383: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:48.383: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:48.383: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:48.383: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Nov 18 11:15:48.383: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:48.383: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:48.383: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:48.383: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:48.383: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:48.383: INFO: Nov 18 11:15:50.381: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:50.381: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:50.381: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:50.381: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Nov 18 11:15:50.381: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:50.381: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:50.381: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:50.381: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:50.381: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:50.381: INFO: Nov 18 11:15:52.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:52.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:52.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:52.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Nov 18 11:15:52.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:52.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:52.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:52.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:52.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:52.369: INFO: Nov 18 11:15:54.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:54.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:54.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:54.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Nov 18 11:15:54.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:54.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:54.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:54.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:54.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:54.368: INFO: Nov 18 11:15:56.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:56.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:56.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:56.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Nov 18 11:15:56.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:56.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:56.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:56.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:56.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:56.370: INFO: Nov 18 11:15:58.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:58.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:58.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:15:58.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Nov 18 11:15:58.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:15:58.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:15:58.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:58.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:58.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:15:58.368: INFO: Nov 18 11:16:00.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:00.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:00.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:00.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Nov 18 11:16:00.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:00.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:00.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:00.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:00.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:00.368: INFO: Nov 18 11:16:02.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:02.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:02.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:02.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Nov 18 11:16:02.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:02.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:02.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:02.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:02.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:02.367: INFO: Nov 18 11:16:04.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:04.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:04.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:04.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Nov 18 11:16:04.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:04.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:04.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:04.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:04.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:04.369: INFO: Nov 18 11:16:06.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:06.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:06.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:06.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Nov 18 11:16:06.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:06.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:06.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:06.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:06.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:06.368: INFO: Nov 18 11:16:08.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:08.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:08.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:08.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Nov 18 11:16:08.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:08.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:08.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:08.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:08.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:08.368: INFO: Nov 18 11:16:10.376: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:10.376: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:10.376: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:10.376: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Nov 18 11:16:10.376: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:10.376: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:10.376: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:10.376: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:10.376: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:10.376: INFO: Nov 18 11:16:12.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:12.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:12.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:12.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Nov 18 11:16:12.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:12.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:12.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:12.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:12.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:12.369: INFO: Nov 18 11:16:14.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:14.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:14.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:14.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Nov 18 11:16:14.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:14.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:14.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:14.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:14.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:14.368: INFO: Nov 18 11:16:16.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:16.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:16.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:16.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Nov 18 11:16:16.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:16.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:16.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:16.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:16.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:16.369: INFO: Nov 18 11:16:18.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:18.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:18.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:18.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Nov 18 11:16:18.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:18.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:18.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:18.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:18.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:18.369: INFO: Nov 18 11:16:20.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:20.372: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:20.372: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:20.372: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Nov 18 11:16:20.372: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:20.372: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:20.372: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:20.372: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:20.372: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:20.372: INFO: Nov 18 11:16:22.372: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:22.372: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:22.372: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:22.372: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Nov 18 11:16:22.372: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:22.372: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:22.372: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:22.372: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:22.372: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:22.372: INFO: Nov 18 11:16:24.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:24.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:24.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:24.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Nov 18 11:16:24.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:24.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:24.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:24.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:24.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:24.370: INFO: Nov 18 11:16:26.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:26.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:26.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:26.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Nov 18 11:16:26.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:26.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:26.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:26.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:26.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:26.369: INFO: Nov 18 11:16:28.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:28.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:28.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:28.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Nov 18 11:16:28.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:28.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:28.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:28.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:28.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:28.369: INFO: Nov 18 11:16:30.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:30.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:30.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:30.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Nov 18 11:16:30.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:30.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:30.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:30.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:30.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:30.368: INFO: Nov 18 11:16:32.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:32.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:32.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:32.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Nov 18 11:16:32.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:32.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:32.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:32.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:32.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:32.369: INFO: Nov 18 11:16:34.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:34.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:34.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:34.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Nov 18 11:16:34.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:34.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:34.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:34.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:34.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:34.370: INFO: Nov 18 11:16:36.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:36.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:36.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:36.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Nov 18 11:16:36.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:36.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:36.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:36.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:36.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:36.369: INFO: Nov 18 11:16:38.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:38.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:38.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:38.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Nov 18 11:16:38.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:38.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:38.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:38.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:38.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:38.367: INFO: Nov 18 11:16:40.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:40.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:40.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:40.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Nov 18 11:16:40.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:40.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:40.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:40.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:40.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:40.368: INFO: Nov 18 11:16:42.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:42.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:42.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:42.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Nov 18 11:16:42.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:42.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:42.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:42.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:42.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:42.370: INFO: Nov 18 11:16:44.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:44.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:44.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:44.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Nov 18 11:16:44.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:44.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:44.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:44.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:44.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:44.368: INFO: Nov 18 11:16:46.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:46.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:46.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:46.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Nov 18 11:16:46.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:46.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:46.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:46.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:46.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:46.367: INFO: Nov 18 11:16:48.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:48.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:48.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:48.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Nov 18 11:16:48.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:48.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:48.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:48.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:48.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:48.368: INFO: Nov 18 11:16:50.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:50.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:50.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:50.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Nov 18 11:16:50.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:50.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:50.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:50.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:50.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:50.370: INFO: Nov 18 11:16:52.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:52.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:52.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:52.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Nov 18 11:16:52.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:52.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:52.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:52.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:52.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:52.368: INFO: Nov 18 11:16:54.373: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:54.373: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:54.373: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:54.373: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Nov 18 11:16:54.373: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:54.373: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:54.373: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:54.373: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:54.373: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:54.373: INFO: Nov 18 11:16:56.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:56.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:56.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:56.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Nov 18 11:16:56.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:56.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:56.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:56.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:56.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:56.368: INFO: Nov 18 11:16:58.376: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:58.376: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:58.376: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:16:58.376: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Nov 18 11:16:58.376: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:16:58.376: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:16:58.376: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:58.376: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:58.376: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:16:58.376: INFO: Nov 18 11:17:00.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:00.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:00.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:00.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Nov 18 11:17:00.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:00.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:00.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:00.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:00.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:00.368: INFO: Nov 18 11:17:02.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:02.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:02.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:02.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Nov 18 11:17:02.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:02.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:02.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:02.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:02.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:02.369: INFO: Nov 18 11:17:04.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:04.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:04.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:04.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Nov 18 11:17:04.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:04.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:04.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:04.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:04.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:04.367: INFO: Nov 18 11:17:06.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:06.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:06.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:06.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Nov 18 11:17:06.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:06.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:06.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:06.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:06.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:06.369: INFO: Nov 18 11:17:08.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:08.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:08.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:08.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Nov 18 11:17:08.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:08.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:08.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:08.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:08.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:08.371: INFO: Nov 18 11:17:10.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:10.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:10.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:10.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Nov 18 11:17:10.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:10.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:10.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:10.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:10.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:10.368: INFO: Nov 18 11:17:12.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:12.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:12.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:12.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Nov 18 11:17:12.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:12.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:12.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:12.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:12.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:12.367: INFO: Nov 18 11:17:14.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:14.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:14.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:14.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Nov 18 11:17:14.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:14.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:14.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:14.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:14.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:14.370: INFO: Nov 18 11:17:16.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:16.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:16.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:16.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Nov 18 11:17:16.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:16.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:16.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:16.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:16.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:16.368: INFO: Nov 18 11:17:18.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:18.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:18.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:18.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Nov 18 11:17:18.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:18.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:18.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:18.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:18.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:18.368: INFO: Nov 18 11:17:20.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:20.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:20.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:20.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Nov 18 11:17:20.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:20.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:20.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:20.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:20.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:20.369: INFO: Nov 18 11:17:22.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:22.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:22.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:22.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Nov 18 11:17:22.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:22.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:22.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:22.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:22.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:22.367: INFO: Nov 18 11:17:24.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:24.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:24.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:24.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Nov 18 11:17:24.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:24.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:24.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:24.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:24.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:24.367: INFO: Nov 18 11:17:26.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:26.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:26.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:26.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Nov 18 11:17:26.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:26.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:26.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:26.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:26.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:26.369: INFO: Nov 18 11:17:28.374: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:28.374: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:28.374: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:28.374: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Nov 18 11:17:28.374: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:28.374: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:28.374: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:28.374: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:28.374: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:28.374: INFO: Nov 18 11:17:30.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:30.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:30.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:30.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Nov 18 11:17:30.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:30.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:30.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:30.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:30.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:30.368: INFO: Nov 18 11:17:32.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:32.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:32.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:32.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Nov 18 11:17:32.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:32.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:32.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:32.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:32.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:32.368: INFO: Nov 18 11:17:34.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:34.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:34.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:34.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Nov 18 11:17:34.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:34.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:34.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:34.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:34.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:34.368: INFO: Nov 18 11:17:36.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:36.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:36.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:36.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Nov 18 11:17:36.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:36.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:36.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:36.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:36.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:36.368: INFO: Nov 18 11:17:38.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:38.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:38.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:38.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Nov 18 11:17:38.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:38.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:38.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:38.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:38.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:38.369: INFO: Nov 18 11:17:40.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:40.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:40.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:40.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Nov 18 11:17:40.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:40.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:40.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:40.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:40.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:40.370: INFO: Nov 18 11:17:42.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:42.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:42.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:42.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Nov 18 11:17:42.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:42.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:42.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:42.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:42.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:42.368: INFO: Nov 18 11:17:44.473: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:44.473: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:44.473: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:44.473: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Nov 18 11:17:44.473: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:44.473: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:44.473: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:44.473: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:44.473: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:44.473: INFO: Nov 18 11:17:46.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:46.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:46.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:46.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Nov 18 11:17:46.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:46.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:46.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:46.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:46.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:46.369: INFO: Nov 18 11:17:48.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:48.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:48.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:48.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Nov 18 11:17:48.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:48.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:48.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:48.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:48.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:48.369: INFO: Nov 18 11:17:50.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:50.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:50.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:50.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Nov 18 11:17:50.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:50.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:50.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:50.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:50.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:50.368: INFO: Nov 18 11:17:52.377: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:52.377: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:52.377: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:52.377: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Nov 18 11:17:52.377: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:52.377: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:52.377: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:52.377: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:52.378: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:52.378: INFO: Nov 18 11:17:54.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:54.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:54.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:54.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Nov 18 11:17:54.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:54.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:54.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:54.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:54.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:54.370: INFO: Nov 18 11:17:56.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:56.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:56.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:56.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Nov 18 11:17:56.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:56.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:56.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:56.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:56.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:56.368: INFO: Nov 18 11:17:58.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:58.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:58.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:17:58.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Nov 18 11:17:58.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:17:58.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:17:58.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:58.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:58.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:17:58.368: INFO: Nov 18 11:18:00.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:00.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:00.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:00.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Nov 18 11:18:00.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:00.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:00.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:00.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:00.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:00.369: INFO: Nov 18 11:18:02.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:02.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:02.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:02.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Nov 18 11:18:02.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:02.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:02.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:02.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:02.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:02.369: INFO: Nov 18 11:18:04.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:04.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:04.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:04.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Nov 18 11:18:04.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:04.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:04.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:04.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:04.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:04.371: INFO: Nov 18 11:18:06.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:06.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:06.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:06.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Nov 18 11:18:06.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:06.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:06.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:06.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:06.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:06.370: INFO: Nov 18 11:18:08.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:08.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:08.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:08.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Nov 18 11:18:08.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:08.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:08.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:08.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:08.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:08.370: INFO: Nov 18 11:18:10.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:10.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:10.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:10.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Nov 18 11:18:10.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:10.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:10.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:10.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:10.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:10.368: INFO: Nov 18 11:18:12.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:12.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:12.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:12.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Nov 18 11:18:12.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:12.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:12.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:12.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:12.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:12.368: INFO: Nov 18 11:18:14.374: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:14.374: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:14.374: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:14.374: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Nov 18 11:18:14.374: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:14.374: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:14.374: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:14.374: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:14.374: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:14.374: INFO: Nov 18 11:18:16.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:16.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:16.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:16.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Nov 18 11:18:16.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:16.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:16.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:16.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:16.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:16.368: INFO: Nov 18 11:18:18.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:18.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:18.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:18.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Nov 18 11:18:18.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:18.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:18.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:18.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:18.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:18.368: INFO: Nov 18 11:18:20.375: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:20.375: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:20.375: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:20.375: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Nov 18 11:18:20.375: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:20.375: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:20.375: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:20.375: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:20.375: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:20.375: INFO: Nov 18 11:18:22.383: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:22.383: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:22.383: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:22.383: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Nov 18 11:18:22.383: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:22.383: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:22.383: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:22.383: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:22.383: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:22.383: INFO: Nov 18 11:18:24.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:24.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:24.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:24.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Nov 18 11:18:24.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:24.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:24.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:24.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:24.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:24.382: INFO: Nov 18 11:18:26.386: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:26.386: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:26.386: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:26.386: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Nov 18 11:18:26.386: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:26.386: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:26.386: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:26.386: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:26.386: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:26.386: INFO: Nov 18 11:18:28.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:28.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:28.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:28.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Nov 18 11:18:28.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:28.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:28.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:28.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:28.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:28.382: INFO: Nov 18 11:18:30.387: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:30.387: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:30.387: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:30.387: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Nov 18 11:18:30.387: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:30.387: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:30.387: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:30.387: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:30.387: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:30.387: INFO: Nov 18 11:18:32.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:32.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:32.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:32.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Nov 18 11:18:32.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:32.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:32.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:32.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:32.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:32.382: INFO: Nov 18 11:18:34.383: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:34.383: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:34.383: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:34.383: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Nov 18 11:18:34.383: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:34.383: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:34.383: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:34.383: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:34.383: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:34.383: INFO: Nov 18 11:18:36.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:36.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:36.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:36.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Nov 18 11:18:36.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:36.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:36.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:36.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:36.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:36.382: INFO: Nov 18 11:18:38.383: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:38.383: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:38.383: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:38.383: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Nov 18 11:18:38.383: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:38.383: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:38.383: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:38.383: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:38.383: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:38.383: INFO: Nov 18 11:18:40.383: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:40.383: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:40.383: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:40.383: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Nov 18 11:18:40.383: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:40.383: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:40.383: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:40.383: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:40.383: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:40.383: INFO: Nov 18 11:18:42.384: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:42.384: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:42.384: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:42.384: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Nov 18 11:18:42.384: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:42.384: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:42.384: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:42.384: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:42.384: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:42.384: INFO: Nov 18 11:18:44.383: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:44.383: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:44.383: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:44.383: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Nov 18 11:18:44.383: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:44.383: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:44.383: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:44.383: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:44.383: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:44.383: INFO: Nov 18 11:18:46.383: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:46.383: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:46.383: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:46.383: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Nov 18 11:18:46.383: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:46.383: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:46.383: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:46.383: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:46.383: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:46.383: INFO: Nov 18 11:18:48.381: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:48.381: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:48.381: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:48.381: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Nov 18 11:18:48.381: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:48.381: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:48.381: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:48.381: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:48.381: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:48.381: INFO: Nov 18 11:18:50.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:50.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:50.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:50.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Nov 18 11:18:50.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:50.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:50.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:50.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:50.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:50.382: INFO: Nov 18 11:18:52.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:52.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:52.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:52.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Nov 18 11:18:52.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:52.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:52.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:52.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:52.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:52.369: INFO: Nov 18 11:18:54.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:54.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:54.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:54.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Nov 18 11:18:54.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:54.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:54.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:54.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:54.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:54.367: INFO: Nov 18 11:18:56.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:56.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:56.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:56.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Nov 18 11:18:56.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:56.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:56.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:56.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:56.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:56.368: INFO: Nov 18 11:18:58.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:58.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:58.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:18:58.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Nov 18 11:18:58.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:18:58.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:18:58.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:58.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:58.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:18:58.369: INFO: Nov 18 11:19:00.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:00.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:00.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:00.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Nov 18 11:19:00.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:00.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:00.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:00.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:00.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:00.367: INFO: Nov 18 11:19:02.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:02.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:02.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:02.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Nov 18 11:19:02.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:02.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:02.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:02.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:02.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:02.368: INFO: Nov 18 11:19:04.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:04.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:04.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:04.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Nov 18 11:19:04.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:04.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:04.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:04.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:04.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:04.368: INFO: Nov 18 11:19:06.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:06.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:06.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:06.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Nov 18 11:19:06.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:06.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:06.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:06.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:06.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:06.369: INFO: Nov 18 11:19:08.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:08.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:08.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:08.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Nov 18 11:19:08.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:08.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:08.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:08.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:08.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:08.370: INFO: Nov 18 11:19:10.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:10.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:10.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:10.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Nov 18 11:19:10.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:10.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:10.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:10.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:10.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:10.369: INFO: Nov 18 11:19:12.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:12.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:12.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:12.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Nov 18 11:19:12.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:12.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:12.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:12.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:12.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:12.367: INFO: Nov 18 11:19:14.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:14.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:14.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:14.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Nov 18 11:19:14.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:14.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:14.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:14.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:14.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:14.368: INFO: Nov 18 11:19:16.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:16.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:16.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:16.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Nov 18 11:19:16.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:16.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:16.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:16.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:16.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:16.368: INFO: Nov 18 11:19:18.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:18.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:18.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:18.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Nov 18 11:19:18.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:18.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:18.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:18.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:18.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:18.371: INFO: Nov 18 11:19:20.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:20.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:20.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:20.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Nov 18 11:19:20.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:20.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:20.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:20.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:20.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:20.368: INFO: Nov 18 11:19:22.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:22.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:22.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:22.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Nov 18 11:19:22.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:22.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:22.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:22.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:22.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:22.368: INFO: Nov 18 11:19:24.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:24.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:24.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:24.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Nov 18 11:19:24.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:24.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:24.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:24.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:24.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:24.368: INFO: Nov 18 11:19:26.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:26.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:26.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:26.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Nov 18 11:19:26.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:26.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:26.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:26.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:26.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:26.368: INFO: Nov 18 11:19:28.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:28.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:28.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:28.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Nov 18 11:19:28.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:28.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:28.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:28.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:28.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:28.369: INFO: Nov 18 11:19:30.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:30.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:30.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:30.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Nov 18 11:19:30.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:30.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:30.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:30.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:30.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:30.367: INFO: Nov 18 11:19:32.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:32.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:32.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:32.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Nov 18 11:19:32.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:32.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:32.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:32.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:32.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:32.368: INFO: Nov 18 11:19:34.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:34.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:34.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:34.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Nov 18 11:19:34.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:34.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:34.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:34.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:34.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:34.368: INFO: Nov 18 11:19:36.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:36.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:36.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:36.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Nov 18 11:19:36.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:36.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:36.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:36.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:36.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:36.369: INFO: Nov 18 11:19:38.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:38.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:38.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:38.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Nov 18 11:19:38.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:38.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:38.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:38.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:38.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:38.370: INFO: Nov 18 11:19:40.486: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:40.486: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:40.486: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:40.486: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Nov 18 11:19:40.486: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:40.486: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:40.486: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:40.486: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:40.486: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:40.486: INFO: Nov 18 11:19:42.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:42.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:42.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:42.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Nov 18 11:19:42.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:42.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:42.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:42.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:42.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:42.371: INFO: Nov 18 11:19:44.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:44.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:44.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:44.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Nov 18 11:19:44.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:44.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:44.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:44.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:44.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:44.369: INFO: Nov 18 11:19:46.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:46.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:46.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:46.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Nov 18 11:19:46.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:46.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:46.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:46.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:46.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:46.370: INFO: Nov 18 11:19:48.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:48.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:48.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:48.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Nov 18 11:19:48.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:48.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:48.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:48.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:48.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:48.368: INFO: Nov 18 11:19:50.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:50.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:50.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:50.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Nov 18 11:19:50.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:50.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:50.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:50.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:50.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:50.368: INFO: Nov 18 11:19:52.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:52.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:52.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:52.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Nov 18 11:19:52.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:52.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:52.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:52.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:52.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:52.369: INFO: Nov 18 11:19:54.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:54.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:54.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:54.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Nov 18 11:19:54.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:54.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:54.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:54.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:54.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:54.370: INFO: Nov 18 11:19:56.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:56.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:56.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:56.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Nov 18 11:19:56.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:56.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:56.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:56.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:56.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:56.368: INFO: Nov 18 11:19:58.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:58.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:58.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:19:58.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Nov 18 11:19:58.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:19:58.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:19:58.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:58.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:58.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:19:58.368: INFO: Nov 18 11:20:00.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:00.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:00.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:00.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Nov 18 11:20:00.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:00.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:00.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:00.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:00.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:00.368: INFO: Nov 18 11:20:02.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:02.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:02.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:02.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Nov 18 11:20:02.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:02.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:02.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:02.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:02.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:02.369: INFO: Nov 18 11:20:04.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:04.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:04.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:04.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Nov 18 11:20:04.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:04.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:04.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:04.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:04.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:04.368: INFO: Nov 18 11:20:06.380: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:06.380: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:06.380: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:06.380: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Nov 18 11:20:06.380: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:06.380: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:06.380: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:06.380: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:06.380: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:06.380: INFO: Nov 18 11:20:08.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:08.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:08.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:08.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Nov 18 11:20:08.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:08.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:08.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:08.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:08.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:08.368: INFO: Nov 18 11:20:10.377: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:10.377: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:10.377: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:10.377: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Nov 18 11:20:10.377: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:10.377: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:10.377: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:10.377: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:10.377: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:10.377: INFO: Nov 18 11:20:12.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:12.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:12.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:12.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Nov 18 11:20:12.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:12.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:12.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:12.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:12.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:12.369: INFO: Nov 18 11:20:14.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:14.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:14.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:14.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Nov 18 11:20:14.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:14.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:14.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:14.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:14.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:14.369: INFO: Nov 18 11:20:16.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:16.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:16.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:16.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Nov 18 11:20:16.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:16.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:16.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:16.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:16.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:16.369: INFO: Nov 18 11:20:18.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:18.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:18.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:18.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Nov 18 11:20:18.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:18.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:18.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:18.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:18.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:18.370: INFO: Nov 18 11:20:20.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:20.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:20.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:20.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Nov 18 11:20:20.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:20.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:20.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:20.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:20.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:20.369: INFO: Nov 18 11:20:22.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:22.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:22.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:22.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Nov 18 11:20:22.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:22.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:22.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:22.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:22.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:22.369: INFO: Nov 18 11:20:24.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:24.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:24.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:24.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Nov 18 11:20:24.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:24.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:24.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:24.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:24.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:24.369: INFO: Nov 18 11:20:26.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:26.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:26.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:26.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Nov 18 11:20:26.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:26.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:26.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:26.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:26.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:26.369: INFO: Nov 18 11:20:28.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:28.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:28.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:28.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Nov 18 11:20:28.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:28.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:28.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:28.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:28.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:28.370: INFO: Nov 18 11:20:30.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:30.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:30.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:30.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Nov 18 11:20:30.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:30.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:30.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:30.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:30.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:30.368: INFO: Nov 18 11:20:32.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:32.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:32.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:32.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Nov 18 11:20:32.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:32.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:32.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:32.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:32.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:32.371: INFO: Nov 18 11:20:34.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:34.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:34.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:34.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Nov 18 11:20:34.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:34.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:34.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:34.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:34.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:34.370: INFO: Nov 18 11:20:36.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:36.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:36.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:36.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Nov 18 11:20:36.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:36.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:36.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:36.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:36.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:36.369: INFO: Nov 18 11:20:38.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:38.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:38.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:38.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Nov 18 11:20:38.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:38.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:38.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:38.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:38.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:38.371: INFO: Nov 18 11:20:40.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:40.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:40.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:40.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Nov 18 11:20:40.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:40.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:40.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:40.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:40.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:40.369: INFO: Nov 18 11:20:42.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:42.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:42.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:42.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Nov 18 11:20:42.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:42.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:42.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:42.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:42.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:42.368: INFO: Nov 18 11:20:44.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:44.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:44.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:44.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Nov 18 11:20:44.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:44.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:44.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:44.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:44.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:44.369: INFO: Nov 18 11:20:46.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:46.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:46.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:46.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Nov 18 11:20:46.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:46.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:46.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:46.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:46.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:46.369: INFO: Nov 18 11:20:48.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:48.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:48.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:48.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Nov 18 11:20:48.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:48.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:48.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:48.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:48.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:48.369: INFO: Nov 18 11:20:50.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:50.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:50.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:50.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Nov 18 11:20:50.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:50.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:50.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:50.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:50.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:50.367: INFO: Nov 18 11:20:52.377: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:52.377: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:52.377: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:52.377: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Nov 18 11:20:52.377: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:52.377: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:52.377: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:52.377: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:52.377: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:52.377: INFO: Nov 18 11:20:54.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:54.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:54.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:54.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Nov 18 11:20:54.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:54.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:54.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:54.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:54.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:54.369: INFO: Nov 18 11:20:56.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:56.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:56.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:56.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Nov 18 11:20:56.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:56.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:56.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:56.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:56.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:56.369: INFO: Nov 18 11:20:58.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:58.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:58.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:20:58.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Nov 18 11:20:58.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:20:58.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:20:58.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:58.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:58.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:20:58.368: INFO: Nov 18 11:21:00.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:00.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:00.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:00.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Nov 18 11:21:00.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:00.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:00.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:00.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:00.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:00.371: INFO: Nov 18 11:21:02.374: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:02.374: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:02.374: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:02.374: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Nov 18 11:21:02.374: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:02.374: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:02.374: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:02.374: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:02.374: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:02.374: INFO: Nov 18 11:21:04.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:04.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:04.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:04.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Nov 18 11:21:04.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:04.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:04.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:04.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:04.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:04.371: INFO: Nov 18 11:21:06.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:06.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:06.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:06.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Nov 18 11:21:06.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:06.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:06.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:06.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:06.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:06.368: INFO: Nov 18 11:21:08.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:08.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:08.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:08.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Nov 18 11:21:08.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:08.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:08.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:08.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:08.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:08.368: INFO: Nov 18 11:21:10.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:10.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:10.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:10.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Nov 18 11:21:10.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:10.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:10.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:10.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:10.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:10.368: INFO: Nov 18 11:21:12.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:12.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:12.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:12.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Nov 18 11:21:12.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:12.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:12.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:12.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:12.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:12.368: INFO: Nov 18 11:21:14.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:14.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:14.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:14.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Nov 18 11:21:14.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:14.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:14.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:14.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:14.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:14.368: INFO: Nov 18 11:21:16.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:16.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:16.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:16.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Nov 18 11:21:16.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:16.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:16.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:16.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:16.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:16.368: INFO: Nov 18 11:21:18.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:18.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:18.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:18.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Nov 18 11:21:18.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:18.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:18.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:18.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:18.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:18.367: INFO: Nov 18 11:21:20.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:20.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:20.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:20.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Nov 18 11:21:20.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:20.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:20.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:20.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:20.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:20.368: INFO: Nov 18 11:21:22.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:22.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:22.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:22.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Nov 18 11:21:22.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:22.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:22.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:22.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:22.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:22.369: INFO: Nov 18 11:21:24.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:24.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:24.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:24.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Nov 18 11:21:24.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:24.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:24.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:24.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:24.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:24.370: INFO: Nov 18 11:21:26.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:26.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:26.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:26.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Nov 18 11:21:26.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:26.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:26.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:26.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:26.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:26.371: INFO: Nov 18 11:21:28.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:28.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:28.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:28.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Nov 18 11:21:28.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:28.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:28.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:28.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:28.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:28.370: INFO: Nov 18 11:21:30.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:30.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:30.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:30.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Nov 18 11:21:30.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:30.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:30.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:30.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:30.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:30.369: INFO: Nov 18 11:21:32.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:32.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:32.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:32.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Nov 18 11:21:32.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:32.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:32.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:32.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:32.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:32.370: INFO: Nov 18 11:21:34.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:34.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:34.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:34.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Nov 18 11:21:34.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:34.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:34.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:34.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:34.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:34.370: INFO: Nov 18 11:21:36.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:36.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:36.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:36.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Nov 18 11:21:36.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:36.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:36.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:36.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:36.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:36.369: INFO: Nov 18 11:21:38.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:38.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:38.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:38.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Nov 18 11:21:38.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:38.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:38.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:38.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:38.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:38.367: INFO: Nov 18 11:21:40.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:40.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:40.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:40.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Nov 18 11:21:40.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:40.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:40.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:40.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:40.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:40.368: INFO: Nov 18 11:21:42.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:42.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:42.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:42.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Nov 18 11:21:42.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:42.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:42.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:42.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:42.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:42.368: INFO: Nov 18 11:21:44.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:44.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:44.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:44.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Nov 18 11:21:44.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:44.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:44.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:44.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:44.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:44.368: INFO: Nov 18 11:21:46.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:46.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:46.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:46.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Nov 18 11:21:46.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:46.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:46.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:46.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:46.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:46.370: INFO: Nov 18 11:21:48.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:48.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:48.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:48.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Nov 18 11:21:48.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:48.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:48.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:48.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:48.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:48.370: INFO: Nov 18 11:21:50.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:50.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:50.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:50.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Nov 18 11:21:50.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:50.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:50.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:50.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:50.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:50.369: INFO: Nov 18 11:21:52.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:52.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:52.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:52.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Nov 18 11:21:52.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:52.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:52.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:52.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:52.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:52.368: INFO: Nov 18 11:21:54.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:54.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:54.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:54.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Nov 18 11:21:54.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:54.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:54.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:54.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:54.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:54.370: INFO: Nov 18 11:21:56.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:56.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:56.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:56.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Nov 18 11:21:56.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:56.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:56.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:56.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:56.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:56.369: INFO: Nov 18 11:21:58.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:58.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:58.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:21:58.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Nov 18 11:21:58.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:21:58.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:21:58.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:58.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:58.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:21:58.370: INFO: Nov 18 11:22:00.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:00.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:00.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:00.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Nov 18 11:22:00.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:00.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:00.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:00.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:00.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:00.368: INFO: Nov 18 11:22:02.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:02.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:02.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:02.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Nov 18 11:22:02.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:02.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:02.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:02.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:02.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:02.368: INFO: Nov 18 11:22:04.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:04.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:04.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:04.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Nov 18 11:22:04.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:04.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:04.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:04.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:04.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:04.369: INFO: Nov 18 11:22:06.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:06.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:06.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:06.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Nov 18 11:22:06.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:06.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:06.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:06.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:06.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:06.368: INFO: Nov 18 11:22:08.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:08.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:08.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:08.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Nov 18 11:22:08.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:08.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:08.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:08.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:08.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:08.370: INFO: Nov 18 11:22:10.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:10.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:10.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:10.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Nov 18 11:22:10.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:10.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:10.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:10.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:10.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:10.370: INFO: Nov 18 11:22:12.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:12.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:12.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:12.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Nov 18 11:22:12.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:12.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:12.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:12.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:12.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:12.370: INFO: Nov 18 11:22:14.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:14.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:14.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:14.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Nov 18 11:22:14.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:14.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:14.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:14.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:14.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:14.369: INFO: Nov 18 11:22:16.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:16.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:16.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:16.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Nov 18 11:22:16.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:16.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:16.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:16.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:16.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:16.368: INFO: Nov 18 11:22:18.378: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:18.378: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:18.378: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:18.378: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Nov 18 11:22:18.378: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:18.378: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:18.378: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:18.378: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:18.378: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:18.378: INFO: Nov 18 11:22:20.372: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:20.372: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:20.372: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:20.372: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Nov 18 11:22:20.372: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:20.372: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:20.372: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:20.372: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:20.372: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:20.372: INFO: Nov 18 11:22:22.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:22.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:22.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:22.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Nov 18 11:22:22.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:22.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:22.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:22.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:22.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:22.370: INFO: Nov 18 11:22:24.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:24.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:24.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:24.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Nov 18 11:22:24.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:24.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:24.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:24.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:24.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:24.369: INFO: Nov 18 11:22:26.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:26.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:26.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:26.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Nov 18 11:22:26.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:26.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:26.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:26.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:26.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:26.368: INFO: Nov 18 11:22:28.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:28.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:28.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:28.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Nov 18 11:22:28.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:28.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:28.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:28.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:28.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:28.367: INFO: Nov 18 11:22:30.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:30.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:30.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:30.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Nov 18 11:22:30.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:30.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:30.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:30.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:30.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:30.368: INFO: Nov 18 11:22:32.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:32.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:32.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:32.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Nov 18 11:22:32.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:32.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:32.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:32.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:32.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:32.369: INFO: Nov 18 11:22:34.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:34.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:34.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:34.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Nov 18 11:22:34.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:34.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:34.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:34.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:34.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:34.370: INFO: Nov 18 11:22:36.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:36.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:36.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:36.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Nov 18 11:22:36.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:36.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:36.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:36.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:36.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:36.368: INFO: Nov 18 11:22:38.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:38.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:38.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:38.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Nov 18 11:22:38.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:38.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:38.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:38.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:38.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:38.370: INFO: Nov 18 11:22:40.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:40.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:40.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:40.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Nov 18 11:22:40.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:40.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:40.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:40.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:40.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:40.369: INFO: Nov 18 11:22:42.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:42.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:42.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:42.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Nov 18 11:22:42.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:42.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:42.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:42.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:42.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:42.367: INFO: Nov 18 11:22:44.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:44.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:44.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:44.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Nov 18 11:22:44.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:44.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:44.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:44.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:44.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:44.367: INFO: Nov 18 11:22:46.372: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:46.372: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:46.372: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:46.372: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Nov 18 11:22:46.372: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:46.372: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:46.372: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:46.372: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:46.372: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:46.372: INFO: Nov 18 11:22:48.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:48.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:48.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:48.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Nov 18 11:22:48.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:48.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:48.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:48.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:48.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:48.370: INFO: Nov 18 11:22:50.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:50.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:50.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:50.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Nov 18 11:22:50.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:50.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:50.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:50.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:50.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:50.368: INFO: Nov 18 11:22:52.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:52.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:52.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:52.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Nov 18 11:22:52.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:52.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:52.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:52.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:52.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:52.368: INFO: Nov 18 11:22:54.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:54.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:54.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:54.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Nov 18 11:22:54.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:54.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:54.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:54.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:54.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:54.369: INFO: Nov 18 11:22:56.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:56.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:56.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:56.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Nov 18 11:22:56.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:56.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:56.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:56.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:56.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:56.368: INFO: Nov 18 11:22:58.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:58.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:58.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:22:58.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Nov 18 11:22:58.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:22:58.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:22:58.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:58.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:58.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:22:58.369: INFO: Nov 18 11:23:00.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:00.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:00.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:00.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Nov 18 11:23:00.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:00.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:00.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:00.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:00.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:00.368: INFO: Nov 18 11:23:02.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:02.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:02.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:02.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Nov 18 11:23:02.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:02.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:02.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:02.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:02.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:02.367: INFO: Nov 18 11:23:04.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:04.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:04.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:04.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Nov 18 11:23:04.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:04.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:04.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:04.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:04.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:04.367: INFO: Nov 18 11:23:06.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:06.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:06.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:06.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Nov 18 11:23:06.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:06.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:06.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:06.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:06.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:06.369: INFO: Nov 18 11:23:08.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:08.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:08.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:08.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Nov 18 11:23:08.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:08.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:08.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:08.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:08.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:08.368: INFO: Nov 18 11:23:10.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:10.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:10.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:10.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Nov 18 11:23:10.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:10.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:10.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:10.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:10.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:10.369: INFO: Nov 18 11:23:12.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:12.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:12.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:12.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Nov 18 11:23:12.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:12.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:12.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:12.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:12.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:12.369: INFO: Nov 18 11:23:14.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:14.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:14.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:14.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Nov 18 11:23:14.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:14.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:14.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:14.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:14.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:14.367: INFO: Nov 18 11:23:16.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:16.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:16.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:16.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Nov 18 11:23:16.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:16.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:16.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:16.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:16.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:16.368: INFO: Nov 18 11:23:18.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:18.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:18.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:18.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Nov 18 11:23:18.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:18.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:18.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:18.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:18.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:18.369: INFO: Nov 18 11:23:20.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:20.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:20.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:20.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Nov 18 11:23:20.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:20.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:20.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:20.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:20.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:20.369: INFO: Nov 18 11:23:22.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:22.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:22.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:22.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Nov 18 11:23:22.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:22.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:22.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:22.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:22.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:22.368: INFO: Nov 18 11:23:24.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:24.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:24.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:24.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Nov 18 11:23:24.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:24.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:24.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:24.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:24.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:24.368: INFO: Nov 18 11:23:26.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:26.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:26.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:26.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Nov 18 11:23:26.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:26.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:26.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:26.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:26.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:26.368: INFO: Nov 18 11:23:28.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:28.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:28.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:28.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Nov 18 11:23:28.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:28.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:28.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:28.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:28.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:28.367: INFO: Nov 18 11:23:30.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:30.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:30.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:30.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Nov 18 11:23:30.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:30.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:30.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:30.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:30.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:30.369: INFO: Nov 18 11:23:32.366: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:32.366: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:32.366: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:32.366: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Nov 18 11:23:32.366: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:32.366: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:32.366: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:32.366: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:32.366: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:32.366: INFO: Nov 18 11:23:34.376: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:34.376: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:34.376: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:34.376: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Nov 18 11:23:34.376: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:34.376: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:34.376: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:34.376: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:34.376: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:34.376: INFO: Nov 18 11:23:36.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:36.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:36.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:36.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Nov 18 11:23:36.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:36.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:36.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:36.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:36.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:36.368: INFO: Nov 18 11:23:38.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:38.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:38.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:38.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Nov 18 11:23:38.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:38.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:38.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:38.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:38.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:38.369: INFO: Nov 18 11:23:40.384: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:40.384: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:40.384: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:40.384: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Nov 18 11:23:40.384: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:40.384: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:40.384: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:40.384: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:40.384: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:40.384: INFO: Nov 18 11:23:42.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:42.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:42.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:42.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Nov 18 11:23:42.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:42.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:42.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:42.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:42.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:42.368: INFO: Nov 18 11:23:44.367: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:44.367: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:44.367: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:44.367: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Nov 18 11:23:44.367: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:44.367: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:44.367: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:44.367: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:44.367: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:44.367: INFO: Nov 18 11:23:46.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:46.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:46.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:46.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Nov 18 11:23:46.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:46.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:46.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:46.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:46.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:46.369: INFO: Nov 18 11:23:48.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:48.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:48.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:48.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Nov 18 11:23:48.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:48.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:48.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:48.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:48.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:48.382: INFO: Nov 18 11:23:50.382: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:50.382: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:50.382: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:50.382: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Nov 18 11:23:50.382: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:50.382: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:50.382: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:50.382: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:50.382: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:50.382: INFO: Nov 18 11:23:52.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:52.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:52.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:52.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Nov 18 11:23:52.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:52.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:52.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:52.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:52.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:52.370: INFO: Nov 18 11:23:54.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:54.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:54.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:54.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Nov 18 11:23:54.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:54.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:54.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:54.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:54.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:54.368: INFO: Nov 18 11:23:56.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:56.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:56.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:56.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Nov 18 11:23:56.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:56.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:56.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:56.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:56.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:56.369: INFO: Nov 18 11:23:58.378: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:58.378: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:58.378: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:23:58.378: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Nov 18 11:23:58.378: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:23:58.378: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:23:58.378: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:58.378: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:58.378: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:23:58.378: INFO: Nov 18 11:24:00.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:00.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:00.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:00.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Nov 18 11:24:00.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:00.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:00.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:00.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:00.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:00.369: INFO: Nov 18 11:24:02.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:02.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:02.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:02.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Nov 18 11:24:02.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:02.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:02.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:02.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:02.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:02.368: INFO: Nov 18 11:24:04.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:04.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:04.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:04.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Nov 18 11:24:04.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:04.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:04.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:04.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:04.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:04.368: INFO: Nov 18 11:24:06.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:06.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:06.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:06.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Nov 18 11:24:06.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:06.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:06.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:06.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:06.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:06.369: INFO: Nov 18 11:24:08.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:08.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:08.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:08.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Nov 18 11:24:08.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:08.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:08.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:08.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:08.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:08.369: INFO: Nov 18 11:24:10.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:10.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:10.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:10.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Nov 18 11:24:10.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:10.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:10.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:10.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:10.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:10.370: INFO: Nov 18 11:24:12.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:12.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:12.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:12.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Nov 18 11:24:12.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:12.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:12.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:12.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:12.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:12.369: INFO: Nov 18 11:24:14.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:14.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:14.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:14.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Nov 18 11:24:14.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:14.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:14.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:14.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:14.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:14.369: INFO: Nov 18 11:24:16.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:16.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:16.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:16.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Nov 18 11:24:16.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:16.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:16.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:16.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:16.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:16.370: INFO: Nov 18 11:24:18.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:18.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:18.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:18.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Nov 18 11:24:18.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:18.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:18.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:18.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:18.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:18.369: INFO: Nov 18 11:24:20.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:20.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:20.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:20.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Nov 18 11:24:20.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:20.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:20.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:20.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:20.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:20.370: INFO: Nov 18 11:24:22.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:22.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:22.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:22.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Nov 18 11:24:22.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:22.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:22.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:22.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:22.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:22.369: INFO: Nov 18 11:24:24.372: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:24.372: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:24.372: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:24.372: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Nov 18 11:24:24.372: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:24.372: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:24.372: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:24.372: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:24.372: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:24.372: INFO: Nov 18 11:24:26.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:26.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:26.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:26.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Nov 18 11:24:26.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:26.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:26.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:26.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:26.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:26.368: INFO: Nov 18 11:24:28.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:28.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:28.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:28.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Nov 18 11:24:28.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:28.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:28.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:28.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:28.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:28.369: INFO: Nov 18 11:24:30.370: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:30.370: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:30.370: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:30.370: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Nov 18 11:24:30.370: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:30.370: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:30.370: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:30.370: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:30.370: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:30.370: INFO: Nov 18 11:24:32.372: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:32.372: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:32.372: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:32.372: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Nov 18 11:24:32.372: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:32.372: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:32.372: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:32.372: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:32.372: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:32.372: INFO: Nov 18 11:24:34.369: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:34.369: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:34.369: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:34.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Nov 18 11:24:34.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:34.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:34.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:34.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:34.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:34.369: INFO: Nov 18 11:24:36.371: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:36.371: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:36.371: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:36.371: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Nov 18 11:24:36.371: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:36.371: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:36.371: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:36.371: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:36.371: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:36.371: INFO: Nov 18 11:24:38.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:38.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:38.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:38.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Nov 18 11:24:38.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:38.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:38.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:38.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:38.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:38.368: INFO: Nov 18 11:24:40.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:40.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:40.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:40.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Nov 18 11:24:40.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:40.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:40.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:40.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:40.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:40.368: INFO: Nov 18 11:24:42.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:42.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:42.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:42.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Nov 18 11:24:42.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:42.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:42.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:42.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:42.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:42.368: INFO: Nov 18 11:24:44.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:44.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:44.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:44.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Nov 18 11:24:44.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:44.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:44.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:44.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:44.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:44.368: INFO: Nov 18 11:24:46.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:46.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:46.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:46.369: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Nov 18 11:24:46.369: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:46.369: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:46.369: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:46.369: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:46.369: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:46.369: INFO: Nov 18 11:24:48.368: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:48.368: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:48.368: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:48.368: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Nov 18 11:24:48.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:48.368: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:48.368: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.368: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.368: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.368: INFO: Nov 18 11:24:48.487: INFO: The status of Pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:48.487: INFO: The status of Pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:48.487: INFO: The status of Pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 18 11:24:48.487: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Nov 18 11:24:48.487: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 18 11:24:48.487: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:48.487: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.487: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.487: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.487: INFO: �[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/18/22 11:24:48.487�[0m �[1mSTEP:�[0m Found 130 events. �[38;5;243m11/18/22 11:24:48.539�[0m Nov 18 11:24:48.539: INFO: At 2022-11-18 11:01:53 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-82yxks-control-plane-2zgnt_4da90bc4-8cad-41fe-bab0-86fa940b0806 became leader Nov 18 11:24:48.539: INFO: At 2022-11-18 11:01:54 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-82yxks-control-plane-2zgnt_5a081a9d-4b5d-416b-b4ac-425ffd542ac4 became leader Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:03 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:03 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-nrdnr Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:03 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-svrrj Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:03 +0000 UTC - event for coredns-787d4945fb-nrdnr: {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.. Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:03 +0000 UTC - event for coredns-787d4945fb-svrrj: {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.. Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:03 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-8dftp Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:03 +0000 UTC - event for kube-proxy-8dftp: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-8dftp to capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:05 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-8dftp Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:08 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-8lk4p Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:08 +0000 UTC - event for kube-proxy-8lk4p: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-8lk4p to capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:09 +0000 UTC - event for kube-proxy-8lk4p: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_fbd3976770c82f" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:11 +0000 UTC - event for kube-proxy-8lk4p: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_fbd3976770c82f" in 2.179452647s (2.179464347s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:11 +0000 UTC - event for kube-proxy-8lk4p: {kubelet capz-conf-82yxks-control-plane-2zgnt} Started: Started container kube-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:11 +0000 UTC - event for kube-proxy-8lk4p: {kubelet capz-conf-82yxks-control-plane-2zgnt} Created: Created container kube-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:27 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:27 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-ndzgn Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:27 +0000 UTC - event for metrics-server-c9574f845-ndzgn: {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.. Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:29 +0000 UTC - event for calico-kube-controllers: {controllermanager } NoPods: No matching pods found Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:29 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:29 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-kk9m2 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:29 +0000 UTC - event for calico-kube-controllers-657b584867-kk9m2: {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.. Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:29 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-tq8ln Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:29 +0000 UTC - event for calico-node-tq8ln: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-tq8ln to capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:29 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:35 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Started: Started container upgrade-ipam Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:35 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 5.864056374s (5.864070274s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:35 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Created: Created container upgrade-ipam Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:39 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Created: Created container install-cni Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:39 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Started: Started container install-cni Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:39 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:41 +0000 UTC - event for calico-kube-controllers-657b584867-kk9m2: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-kk9m2 to capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:41 +0000 UTC - event for coredns-787d4945fb-nrdnr: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-nrdnr to capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:41 +0000 UTC - event for coredns-787d4945fb-svrrj: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-svrrj to capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:41 +0000 UTC - event for metrics-server-c9574f845-ndzgn: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-ndzgn to capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:42 +0000 UTC - event for calico-kube-controllers-657b584867-kk9m2: {kubelet capz-conf-82yxks-control-plane-2zgnt} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "fd1c6ecc215c1ea79bcf3de914a4581452137fd2188240ab21cb3a17f124a81e": 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/ Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:42 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:42 +0000 UTC - event for coredns-787d4945fb-nrdnr: {kubelet capz-conf-82yxks-control-plane-2zgnt} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "963c5581409a0a927402c7280d4262850f5e78b8199fa77c5357d632db418f55": 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/ Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:42 +0000 UTC - event for coredns-787d4945fb-svrrj: {kubelet capz-conf-82yxks-control-plane-2zgnt} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "20cf1f2244edf82ef115e55ddc52129529e2a7fea4b8debbdacc3d5de81f0adf": 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/ Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:42 +0000 UTC - event for metrics-server-c9574f845-ndzgn: {kubelet capz-conf-82yxks-control-plane-2zgnt} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0da3ed1ff950c5e1a4dab74baf97ea17214dab7dbfaaa2a58b62bbda7ebf8be2": 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/ Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:48 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Started: Started container calico-node Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:48 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 6.286594602s (6.286600302s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:48 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Created: Created container calico-node Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:49 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} 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 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:50 +0000 UTC - event for calico-node-tq8ln: {kubelet capz-conf-82yxks-control-plane-2zgnt} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:53 +0000 UTC - event for metrics-server-c9574f845-ndzgn: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:54 +0000 UTC - event for calico-kube-controllers-657b584867-kk9m2: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:55 +0000 UTC - event for coredns-787d4945fb-svrrj: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:55 +0000 UTC - event for coredns-787d4945fb-svrrj: {kubelet capz-conf-82yxks-control-plane-2zgnt} Created: Created container coredns Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:55 +0000 UTC - event for coredns-787d4945fb-svrrj: {kubelet capz-conf-82yxks-control-plane-2zgnt} Started: Started container coredns Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:56 +0000 UTC - event for coredns-787d4945fb-svrrj: {kubelet capz-conf-82yxks-control-plane-2zgnt} Unhealthy: Readiness probe failed: Get "http://192.168.193.67:8181/ready": dial tcp 192.168.193.67:8181: connect: connection refused Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:57 +0000 UTC - event for metrics-server-c9574f845-ndzgn: {kubelet capz-conf-82yxks-control-plane-2zgnt} Started: Started container metrics-server Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:57 +0000 UTC - event for metrics-server-c9574f845-ndzgn: {kubelet capz-conf-82yxks-control-plane-2zgnt} Created: Created container metrics-server Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:57 +0000 UTC - event for metrics-server-c9574f845-ndzgn: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.83418285s (3.834344748s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:59 +0000 UTC - event for coredns-787d4945fb-nrdnr: {kubelet capz-conf-82yxks-control-plane-2zgnt} Started: Started container coredns Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:59 +0000 UTC - event for coredns-787d4945fb-nrdnr: {kubelet capz-conf-82yxks-control-plane-2zgnt} Created: Created container coredns Nov 18 11:24:48.539: INFO: At 2022-11-18 11:02:59 +0000 UTC - event for coredns-787d4945fb-nrdnr: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine Nov 18 11:24:48.539: INFO: At 2022-11-18 11:03:00 +0000 UTC - event for coredns-787d4945fb-nrdnr: {kubelet capz-conf-82yxks-control-plane-2zgnt} Unhealthy: Readiness probe failed: Get "http://192.168.193.68:8181/ready": dial tcp 192.168.193.68:8181: connect: connection refused Nov 18 11:24:48.539: INFO: At 2022-11-18 11:03:03 +0000 UTC - event for calico-kube-controllers-657b584867-kk9m2: {kubelet capz-conf-82yxks-control-plane-2zgnt} Unhealthy: Readiness probe failed: Failed to read status file /status/status.json: unexpected end of JSON input Nov 18 11:24:48.539: INFO: At 2022-11-18 11:03:03 +0000 UTC - event for calico-kube-controllers-657b584867-kk9m2: {kubelet capz-conf-82yxks-control-plane-2zgnt} Started: Started container calico-kube-controllers Nov 18 11:24:48.539: INFO: At 2022-11-18 11:03:03 +0000 UTC - event for calico-kube-controllers-657b584867-kk9m2: {kubelet capz-conf-82yxks-control-plane-2zgnt} Created: Created container calico-kube-controllers Nov 18 11:24:48.539: INFO: At 2022-11-18 11:03:03 +0000 UTC - event for calico-kube-controllers-657b584867-kk9m2: {kubelet capz-conf-82yxks-control-plane-2zgnt} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.807898484s (8.355868299s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:19 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-26mms Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:19 +0000 UTC - event for calico-node-windows-26mms: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-26mms to capz-conf-qhg64 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:19 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-4lz46 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:19 +0000 UTC - event for containerd-logger-4lz46: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-4lz46 to capz-conf-qhg64 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:19 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-mt8xz Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:19 +0000 UTC - event for kube-proxy-windows-mt8xz: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-mt8xz to capz-conf-qhg64 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:21 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} FailedMount: MountVolume.SetUp failed for volume "calico-static-rules" : failed to sync configmap cache: timed out waiting for the condition Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:21 +0000 UTC - event for containerd-logger-4lz46: {kubelet capz-conf-qhg64} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:36 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:36 +0000 UTC - event for containerd-logger-4lz46: {kubelet capz-conf-qhg64} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:36 +0000 UTC - event for kube-proxy-windows-mt8xz: {kubelet capz-conf-qhg64} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess" already present on machine Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:36 +0000 UTC - event for kube-proxy-windows-mt8xz: {kubelet capz-conf-qhg64} Started: Started container kube-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:36 +0000 UTC - event for kube-proxy-windows-mt8xz: {kubelet capz-conf-qhg64} Created: Created container kube-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:40 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 4.1683872s (4.1684769s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:40 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Created: Created container install-cni Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:41 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Started: Started container install-cni Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:42 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-9gdf6 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:42 +0000 UTC - event for csi-proxy-9gdf6: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-9gdf6 to capz-conf-qhg64 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:43 +0000 UTC - event for csi-proxy-9gdf6: {kubelet capz-conf-qhg64} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:45 +0000 UTC - event for containerd-logger-4lz46: {kubelet capz-conf-qhg64} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.5132931s (8.6699634s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:46 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:49 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-pw4bf Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:49 +0000 UTC - event for calico-node-windows-pw4bf: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-pw4bf to capz-conf-84hb2 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:49 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-6bf8w Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:49 +0000 UTC - event for containerd-logger-6bf8w: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-6bf8w to capz-conf-84hb2 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:49 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-mt7vs Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:49 +0000 UTC - event for kube-proxy-windows-mt7vs: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-mt7vs to capz-conf-84hb2 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:50 +0000 UTC - event for containerd-logger-4lz46: {kubelet capz-conf-qhg64} Created: Created container containerd-logger Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:50 +0000 UTC - event for containerd-logger-4lz46: {kubelet capz-conf-qhg64} Started: Started container containerd-logger Nov 18 11:24:48.539: INFO: At 2022-11-18 11:13:51 +0000 UTC - event for containerd-logger-6bf8w: {kubelet capz-conf-84hb2} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:00 +0000 UTC - event for csi-proxy-9gdf6: {kubelet capz-conf-qhg64} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 14.9690088s (16.8897601s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:00 +0000 UTC - event for csi-proxy-9gdf6: {kubelet capz-conf-qhg64} Created: Created container csi-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:00 +0000 UTC - event for csi-proxy-9gdf6: {kubelet capz-conf-qhg64} Started: Started container csi-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:02 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 2.5365188s (16.3433462s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:02 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Created: Created container calico-node-startup Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:02 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Started: Started container calico-node-startup Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:02 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:03 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 297.3672ms (297.3672ms including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:06 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:06 +0000 UTC - event for kube-proxy-windows-mt7vs: {kubelet capz-conf-84hb2} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess" already present on machine Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:07 +0000 UTC - event for containerd-logger-6bf8w: {kubelet capz-conf-84hb2} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:07 +0000 UTC - event for kube-proxy-windows-mt7vs: {kubelet capz-conf-84hb2} Started: Started container kube-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:07 +0000 UTC - event for kube-proxy-windows-mt7vs: {kubelet capz-conf-84hb2} Created: Created container kube-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:08 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Created: Created container calico-node-felix Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:08 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Started: Started container calico-node-felix Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:10 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Started: Started container install-cni Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:10 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 3.4973536s (3.4973536s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:10 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Created: Created container install-cni Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:12 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-fwsjd Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:12 +0000 UTC - event for csi-proxy-fwsjd: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-fwsjd to capz-conf-84hb2 Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:13 +0000 UTC - event for csi-proxy-fwsjd: {kubelet capz-conf-84hb2} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:15 +0000 UTC - event for containerd-logger-6bf8w: {kubelet capz-conf-84hb2} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.6587766s (8.0430549s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:16 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:21 +0000 UTC - event for containerd-logger-6bf8w: {kubelet capz-conf-84hb2} Created: Created container containerd-logger Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:22 +0000 UTC - event for containerd-logger-6bf8w: {kubelet capz-conf-84hb2} Started: Started container containerd-logger Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:29 +0000 UTC - event for calico-node-windows-26mms: {kubelet capz-conf-qhg64} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 264.1454ms (264.1454ms including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:30 +0000 UTC - event for csi-proxy-fwsjd: {kubelet capz-conf-84hb2} Created: Created container csi-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:30 +0000 UTC - event for csi-proxy-fwsjd: {kubelet capz-conf-84hb2} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 15.2687404s (17.0525331s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:30 +0000 UTC - event for csi-proxy-fwsjd: {kubelet capz-conf-84hb2} Started: Started container csi-proxy Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:32 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Created: Created container calico-node-startup Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:32 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 2.5108405s (16.661997s including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:33 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess" Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:33 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 262.2531ms (262.2531ms including waiting) Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:33 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Started: Started container calico-node-startup Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:38 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Created: Created container calico-node-felix Nov 18 11:24:48.539: INFO: At 2022-11-18 11:14:38 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Started: Started container calico-node-felix Nov 18 11:24:48.539: INFO: At 2022-11-18 11:15:01 +0000 UTC - event for calico-node-windows-pw4bf: {kubelet capz-conf-84hb2} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 334.7295ms (334.7295ms including waiting) Nov 18 11:24:48.589: INFO: POD NODE PHASE GRACE CONDITIONS Nov 18 11:24:48.589: INFO: calico-kube-controllers-657b584867-kk9m2 capz-conf-82yxks-control-plane-2zgnt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:03:04 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:03:04 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:41 +0000 UTC }] Nov 18 11:24:48.589: INFO: calico-node-tq8ln capz-conf-82yxks-control-plane-2zgnt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:42 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:59 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:59 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:29 +0000 UTC }] Nov 18 11:24:48.589: INFO: calico-node-windows-26mms capz-conf-qhg64 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:33 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:19 +0000 UTC }] Nov 18 11:24:48.589: INFO: calico-node-windows-pw4bf capz-conf-84hb2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:15:07 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:15:07 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:49 +0000 UTC }] Nov 18 11:24:48.589: INFO: containerd-logger-4lz46 capz-conf-qhg64 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:51 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:51 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:19 +0000 UTC }] Nov 18 11:24:48.589: INFO: containerd-logger-6bf8w capz-conf-84hb2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:50 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:22 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:22 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:49 +0000 UTC }] Nov 18 11:24:48.589: INFO: coredns-787d4945fb-nrdnr capz-conf-82yxks-control-plane-2zgnt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:03:12 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:03:12 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:41 +0000 UTC }] Nov 18 11:24:48.589: INFO: coredns-787d4945fb-svrrj capz-conf-82yxks-control-plane-2zgnt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:03:11 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:03:11 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:41 +0000 UTC }] Nov 18 11:24:48.589: INFO: csi-proxy-9gdf6 capz-conf-qhg64 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:42 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:01 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:01 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:42 +0000 UTC }] Nov 18 11:24:48.589: INFO: csi-proxy-fwsjd capz-conf-84hb2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:12 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:31 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:31 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:12 +0000 UTC }] Nov 18 11:24:48.589: INFO: etcd-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:05 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:14 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:14 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:05 +0000 UTC }] Nov 18 11:24:48.589: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.589: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.589: INFO: kube-proxy-8lk4p capz-conf-82yxks-control-plane-2zgnt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:12 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:12 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:08 +0000 UTC }] Nov 18 11:24:48.589: INFO: kube-proxy-windows-mt7vs capz-conf-84hb2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:50 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:07 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:14:07 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:49 +0000 UTC }] Nov 18 11:24:48.589: INFO: kube-proxy-windows-mt8xz capz-conf-qhg64 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:37 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:37 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:13:19 +0000 UTC }] Nov 18 11:24:48.589: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Nov 18 11:24:48.589: INFO: metrics-server-c9574f845-ndzgn capz-conf-82yxks-control-plane-2zgnt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:03:22 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:03:22 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 11:02:41 +0000 UTC }] Nov 18 11:24:48.589: INFO: Nov 18 11:24:49.095: INFO: Logging node info for node capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:49.287: INFO: Node Info: &Node{ObjectMeta:{capz-conf-82yxks-control-plane-2zgnt dfe63f5e-fa6e-4dae-83af-ed0e67e3f239 2605 0 2022-11-18 11:02:02 +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:eastus2 failure-domain.beta.kubernetes.io/zone:eastus2-2 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-82yxks-control-plane-2zgnt 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:eastus2 topology.kubernetes.io/zone:eastus2-2] map[cluster.x-k8s.io/cluster-name:capz-conf-82yxks cluster.x-k8s.io/cluster-namespace:capz-conf-82yxks cluster.x-k8s.io/machine:capz-conf-82yxks-control-plane-q9dgs cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-82yxks-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.193.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-18 11:02:02 +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":{}}} } {kubeadm Update v1 2022-11-18 11:02:03 +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":{}}}} } {manager Update v1 2022-11-18 11:02:26 +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 2022-11-18 11:02:41 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-18 11:02:48 +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 2022-11-18 11:23:28 +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-82yxks/providers/Microsoft.Compute/virtualMachines/capz-conf-82yxks-control-plane-2zgnt,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: {{8344719360 0} {<nil>} 8149140Ki 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: {{8239861760 0} {<nil>} 8046740Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2022-11-18 11:02:48 +0000 UTC,LastTransitionTime:2022-11-18 11:02:48 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-18 11:23:28 +0000 UTC,LastTransitionTime:2022-11-18 11:01:34 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 11:23:28 +0000 UTC,LastTransitionTime:2022-11-18 11:01:34 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 11:23:28 +0000 UTC,LastTransitionTime:2022-11-18 11:01:34 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 11:23:28 +0000 UTC,LastTransitionTime:2022-11-18 11:02:41 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-82yxks-control-plane-2zgnt,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:c978d2c02188477f9be6e6facc390f9a,SystemUUID:058bdc45-ae49-4447-907a-2c09997760b9,BootID:61fa29d2-51fc-4b3d-800d-bd1e2200dde1,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.30+fbd3976770c82f,KubeProxyVersion:v1.27.0-alpha.0.30+fbd3976770c82f,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:b83c1d70989e1fe87583607bf5aee1ee34e52773d4755b95f5cf5a451962f3a4 registry.k8s.io/etcd:3.5.5-0],SizeBytes:102417044,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:6f72b851544986cb0921b53ea655ec04c36131248f16d4ad110cb3ca0c369dc1 registry.k8s.io/etcd:3.5.4-0],SizeBytes:102157811,},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:d21364e0c633a2e2e59c3839983222a0cbd1a20b5f65447dc135d776a3fee704 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:35317342,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:4188262a351f156e8027ff81693d771c35b34b668cbd61e59c4a4490dd5c08f3 registry.k8s.io/kube-apiserver:v1.25.3],SizeBytes:34238163,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:4cba827b4565c9d11a9a8648070fa8c3e89f0b9eb88ac1c0a24b5d5a96eda2c1 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:32243894,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:d3a06262256f3e7578d5f77df137a8cdf58f9f498f35b5b56d116e8a7e31dc91 registry.k8s.io/kube-controller-manager:v1.25.3],SizeBytes:31261869,},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:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:74af4dd1f4b40265afc2c24fa21b10d22984f08736e8036c685974aeee2ac2cf gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:21534369,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:3e28658c9fd10358a4da39594346bff855e5bea14e538977fc62cab7cff7e7b4 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_fbd3976770c82f],SizeBytes:21532658,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:6bf25f038543e1f433cb7f2bdda445ed348c7b9279935ebc2ae4f432308ed82f registry.k8s.io/kube-proxy:v1.25.3],SizeBytes:20265805,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:1a77cd3899f75eb90f4ebdb50e81a5a89fbe7984292b185f1168913520813c74 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:17482420,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},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:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Nov 18 11:24:49.293: INFO: Logging kubelet events for node capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:49.483: INFO: Logging pods the kubelet thinks is on node capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:49.719: INFO: coredns-787d4945fb-svrrj started at 2022-11-18 11:02:41 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:49.719: INFO: Container coredns ready: true, restart count 0 Nov 18 11:24:49.719: INFO: calico-kube-controllers-657b584867-kk9m2 started at 2022-11-18 11:02:41 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:49.719: INFO: Container calico-kube-controllers ready: true, restart count 0 Nov 18 11:24:49.719: INFO: etcd-capz-conf-82yxks-control-plane-2zgnt started at 2022-11-18 11:02:05 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:49.719: INFO: Container etcd ready: true, restart count 0 Nov 18 11:24:49.719: INFO: kube-apiserver-capz-conf-82yxks-control-plane-2zgnt started at <nil> (0+0 container statuses recorded) Nov 18 11:24:49.719: INFO: kube-scheduler-capz-conf-82yxks-control-plane-2zgnt started at <nil> (0+0 container statuses recorded) Nov 18 11:24:49.719: INFO: calico-node-tq8ln started at 2022-11-18 11:02:29 +0000 UTC (2+1 container statuses recorded) Nov 18 11:24:49.719: INFO: Init container upgrade-ipam ready: true, restart count 0 Nov 18 11:24:49.719: INFO: Init container install-cni ready: true, restart count 0 Nov 18 11:24:49.719: INFO: Container calico-node ready: true, restart count 0 Nov 18 11:24:49.719: INFO: coredns-787d4945fb-nrdnr started at 2022-11-18 11:02:41 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:49.719: INFO: Container coredns ready: true, restart count 0 Nov 18 11:24:49.719: INFO: kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt started at <nil> (0+0 container statuses recorded) Nov 18 11:24:49.719: INFO: kube-proxy-8lk4p started at 2022-11-18 11:02:08 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:49.719: INFO: Container kube-proxy ready: true, restart count 0 Nov 18 11:24:49.719: INFO: metrics-server-c9574f845-ndzgn started at 2022-11-18 11:02:41 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:49.719: INFO: Container metrics-server ready: true, restart count 0 Nov 18 11:24:50.332: INFO: Latency metrics for node capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:50.332: INFO: Logging node info for node capz-conf-84hb2 Nov 18 11:24:50.482: INFO: Node Info: &Node{ObjectMeta:{capz-conf-84hb2 43db4fbb-0241-4934-8088-2ebd3f92d4c3 2289 0 2022-11-18 11:13:49 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-84hb2 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-82yxks cluster.x-k8s.io/cluster-namespace:capz-conf-82yxks cluster.x-k8s.io/machine:capz-conf-82yxks-md-win-f78f4dc5f-qzbmw cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-82yxks-md-win-f78f4dc5f kubeadm.alpha.kubernetes.io/cri-socket:npipe:////./pipe/containerd-containerd node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.5/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.152.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:8f:3c:e8 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-18 11:13:49 +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:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-18 11:13:50 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-18 11:14:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-18 11:14:41 +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":{}}}} } {Go-http-client Update v1 2022-11-18 11:14:59 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-18 11:19:57 +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-82yxks/providers/Microsoft.Compute/virtualMachines/capz-conf-84hb2,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{136912564224 0} {<nil>} 133703676Ki BinarySI},memory: {{17179398144 0} {<nil>} 16776756Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{123221307598 0} {<nil>} 123221307598 DecimalSI},memory: {{17074540544 0} {<nil>} 16674356Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-18 11:19:57 +0000 UTC,LastTransitionTime:2022-11-18 11:13:49 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 11:19:57 +0000 UTC,LastTransitionTime:2022-11-18 11:13:49 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 11:19:57 +0000 UTC,LastTransitionTime:2022-11-18 11:13:49 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 11:19:57 +0000 UTC,LastTransitionTime:2022-11-18 11:14:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-84hb2,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-84hb2,SystemUUID:8FE3380C-F547-4DEC-922C-09FF67C18081,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.30+fbd3976770c82f-dirty,KubeProxyVersion:v1.27.0-alpha.0.30+fbd3976770c82f-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Nov 18 11:24:50.482: INFO: Logging kubelet events for node capz-conf-84hb2 Nov 18 11:24:50.683: INFO: Logging pods the kubelet thinks is on node capz-conf-84hb2 Nov 18 11:24:50.893: INFO: kube-proxy-windows-mt7vs started at 2022-11-18 11:13:50 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:50.893: INFO: Container kube-proxy ready: true, restart count 0 Nov 18 11:24:50.893: INFO: calico-node-windows-pw4bf started at 2022-11-18 11:13:50 +0000 UTC (1+2 container statuses recorded) Nov 18 11:24:50.893: INFO: Init container install-cni ready: true, restart count 0 Nov 18 11:24:50.893: INFO: Container calico-node-felix ready: true, restart count 1 Nov 18 11:24:50.893: INFO: Container calico-node-startup ready: true, restart count 0 Nov 18 11:24:50.893: INFO: containerd-logger-6bf8w started at 2022-11-18 11:13:50 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:50.893: INFO: Container containerd-logger ready: true, restart count 0 Nov 18 11:24:50.893: INFO: csi-proxy-fwsjd started at 2022-11-18 11:14:12 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:50.893: INFO: Container csi-proxy ready: true, restart count 0 Nov 18 11:24:51.532: INFO: Latency metrics for node capz-conf-84hb2 Nov 18 11:24:51.532: INFO: Logging node info for node capz-conf-qhg64 Nov 18 11:24:51.682: INFO: Node Info: &Node{ObjectMeta:{capz-conf-qhg64 ab893a39-a0d9-4a68-920a-4f83172d005c 2704 0 2022-11-18 11:13:19 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-qhg64 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-82yxks cluster.x-k8s.io/cluster-namespace:capz-conf-82yxks cluster.x-k8s.io/machine:capz-conf-82yxks-md-win-f78f4dc5f-4qg8d cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-82yxks-md-win-f78f4dc5f kubeadm.alpha.kubernetes.io/cri-socket:npipe:////./pipe/containerd-containerd node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.162.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:81:6d:f6 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-18 11:13:19 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-18 11:13:19 +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:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2022-11-18 11:13:42 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-18 11:14:13 +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":{}}}} } {Go-http-client Update v1 2022-11-18 11:14:26 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-18 11:24:33 +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-82yxks/providers/Microsoft.Compute/virtualMachines/capz-conf-qhg64,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{136912564224 0} {<nil>} 133703676Ki BinarySI},memory: {{17179398144 0} {<nil>} 16776756Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{123221307598 0} {<nil>} 123221307598 DecimalSI},memory: {{17074540544 0} {<nil>} 16674356Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-18 11:24:33 +0000 UTC,LastTransitionTime:2022-11-18 11:13:19 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 11:24:33 +0000 UTC,LastTransitionTime:2022-11-18 11:13:19 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 11:24:33 +0000 UTC,LastTransitionTime:2022-11-18 11:13:19 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 11:24:33 +0000 UTC,LastTransitionTime:2022-11-18 11:13:42 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-qhg64,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-qhg64,SystemUUID:8F271A68-8220-4DCD-906A-251B41B81632,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.30+fbd3976770c82f-dirty,KubeProxyVersion:v1.27.0-alpha.0.30+fbd3976770c82f-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Nov 18 11:24:51.682: INFO: Logging kubelet events for node capz-conf-qhg64 Nov 18 11:24:51.883: INFO: Logging pods the kubelet thinks is on node capz-conf-qhg64 Nov 18 11:24:52.091: INFO: kube-proxy-windows-mt8xz started at 2022-11-18 11:13:19 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:52.091: INFO: Container kube-proxy ready: true, restart count 0 Nov 18 11:24:52.091: INFO: containerd-logger-4lz46 started at 2022-11-18 11:13:19 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:52.091: INFO: Container containerd-logger ready: true, restart count 0 Nov 18 11:24:52.092: INFO: calico-node-windows-26mms started at 2022-11-18 11:13:19 +0000 UTC (1+2 container statuses recorded) Nov 18 11:24:52.092: INFO: Init container install-cni ready: true, restart count 0 Nov 18 11:24:52.092: INFO: Container calico-node-felix ready: true, restart count 1 Nov 18 11:24:52.092: INFO: Container calico-node-startup ready: true, restart count 0 Nov 18 11:24:52.092: INFO: csi-proxy-9gdf6 started at 2022-11-18 11:13:42 +0000 UTC (0+1 container statuses recorded) Nov 18 11:24:52.092: INFO: Container csi-proxy ready: true, restart count 0 Nov 18 11:24:52.730: INFO: Latency metrics for node capz-conf-qhg64 Nov 18 11:24:52.893: INFO: Running kubectl logs on non-ready containers in kube-system Nov 18 11:24:53.286: INFO: Failed to get logs of pod kube-apiserver-capz-conf-82yxks-control-plane-2zgnt, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-82yxks-control-plane-2zgnt) Nov 18 11:24:53.286: INFO: Logs of kube-system/kube-apiserver-capz-conf-82yxks-control-plane-2zgnt:kube-apiserver on node capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:53.286: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-82yxks-control-plane-2zgnt:kube-apiserver Nov 18 11:24:53.689: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt) Nov 18 11:24:53.689: INFO: Logs of kube-system/kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt:kube-controller-manager on node capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:53.689: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt:kube-controller-manager Nov 18 11:24:54.083: INFO: Failed to get logs of pod kube-scheduler-capz-conf-82yxks-control-plane-2zgnt, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-82yxks-control-plane-2zgnt) Nov 18 11:24:54.083: INFO: Logs of kube-system/kube-scheduler-capz-conf-82yxks-control-plane-2zgnt:kube-scheduler on node capz-conf-82yxks-control-plane-2zgnt Nov 18 11:24:54.083: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-82yxks-control-plane-2zgnt:kube-scheduler Nov 18 11:24:54.084: FAIL: Error waiting for all pods to be running and ready: 3 / 18 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s POD NODE PHASE GRACE CONDITIONS kube-apiserver-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] kube-controller-manager-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] kube-scheduler-capz-conf-82yxks-control-plane-2zgnt capz-conf-82yxks-control-plane-2zgnt Pending [] Full Stack Trace k8s.io/kubernetes/test/e2e.setupSuite() test/e2e/e2e.go:249 +0x4de k8s.io/kubernetes/test/e2e.glob..func1() test/e2e/e2e.go:81 +0x8f reflect.Value.call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0x75b6e72, 0x4}, {0xc0000b7f20, 0x0, 0x0?}) /usr/local/go/src/reflect/value.go:584 +0x8c5 reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0xc0000b7f20?, 0x0?, 0x0?}) /usr/local/go/src/reflect/value.go:368 +0xbc
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
capz-e2e Conformance Tests conformance-tests
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