PR #104660 pull-kubernetes-e2e-capz-windows-containerd #1609885614965002240
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | claudiubelu: Windows file permissions |
| Result | SUCCESS |
| Tests | 4 failed / 8 succeeded |
| Started | |
| Elapsed | 1h7m |
| Revision | 1b6ed5adff2bc7d1452ba41745152a523322b2aa |
| Refs |
104660 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] 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-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:249 @ 01/02/23 13:11:07.244from junit.kubetest.01.xml
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/02/23 13:00:59.733 Jan 2 13:00:59.734: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 2 13:00:59.740: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 2 13:01:00.218: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 2 13:01:00.625: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:00.625: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:00.625: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:00.625: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:00.625: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:00.625: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 2 13:01:00.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:00.625: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:00.625: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotInitialized containers with incomplete status: [init]} {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:00.625: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:00.625: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:00.625: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:00.625: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:00.625: INFO: Jan 2 13:01:03.031: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:03.031: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:03.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:03.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:03.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:03.031: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Jan 2 13:01:03.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:03.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:03.031: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotInitialized containers with incomplete status: [init]} {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:03.031: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:03.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:03.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:03.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:03.031: INFO: Jan 2 13:01:05.030: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:05.030: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:05.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:05.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:05.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:05.030: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Jan 2 13:01:05.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:05.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:05.030: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotInitialized containers with incomplete status: [init]} {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:05.030: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:05.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:05.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:05.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:05.030: INFO: Jan 2 13:01:07.027: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:07.027: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:07.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:07.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:07.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:07.027: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Jan 2 13:01:07.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:07.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:07.027: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:07.027: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:07.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:07.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:07.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:07.027: INFO: Jan 2 13:01:09.028: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:09.028: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:09.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:09.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:09.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:09.028: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Jan 2 13:01:09.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:09.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:09.028: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:09.028: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:09.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:09.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:09.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:09.028: INFO: Jan 2 13:01:11.032: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:11.032: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:11.032: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:11.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:11.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:11.033: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Jan 2 13:01:11.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:11.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:11.033: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:11.033: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:11.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:11.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:11.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:11.033: INFO: Jan 2 13:01:13.031: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:13.031: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:13.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:13.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:13.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:13.031: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Jan 2 13:01:13.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:13.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:13.031: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:13.031: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:13.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:13.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:13.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:13.031: INFO: Jan 2 13:01:15.029: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:15.029: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:15.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:15.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:15.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:15.029: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Jan 2 13:01:15.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:15.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:15.029: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:15.029: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:15.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:15.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:15.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:15.029: INFO: Jan 2 13:01:17.033: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:17.033: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:17.033: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:17.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:17.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:17.033: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Jan 2 13:01:17.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:17.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:17.033: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:17.033: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:17.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:17.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:17.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:17.033: INFO: Jan 2 13:01:19.032: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:19.032: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:19.032: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:19.032: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:19.032: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:19.033: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Jan 2 13:01:19.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:19.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:19.033: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:19.033: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:19.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:19.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:19.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:19.033: INFO: Jan 2 13:01:21.027: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:21.027: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:21.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:21.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:21.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:21.027: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Jan 2 13:01:21.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:21.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:21.027: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:21.028: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:21.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:21.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:21.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:21.028: INFO: Jan 2 13:01:23.042: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:23.042: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:23.042: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:23.042: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:23.042: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:23.042: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Jan 2 13:01:23.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:23.042: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:23.042: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:23.042: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:23.042: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:23.042: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:23.042: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:23.042: INFO: Jan 2 13:01:25.036: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:25.036: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:25.036: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:25.036: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:25.036: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:25.036: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Jan 2 13:01:25.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:25.036: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:25.036: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:25.036: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:25.036: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:25.036: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:25.036: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:25.036: INFO: Jan 2 13:01:27.028: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:27.028: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:27.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:27.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:27.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:27.028: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Jan 2 13:01:27.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:27.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:27.028: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:27.028: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:27.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:27.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:27.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:27.028: INFO: Jan 2 13:01:29.030: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:29.030: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:29.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:29.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:29.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:29.030: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Jan 2 13:01:29.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:29.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:29.030: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:29.030: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:29.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:29.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:29.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:29.030: INFO: Jan 2 13:01:31.030: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:31.030: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:31.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:31.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:31.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:31.030: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Jan 2 13:01:31.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:31.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:31.031: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:31.031: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:31.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:31.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:31.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:31.031: INFO: Jan 2 13:01:33.026: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:33.026: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:33.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:33.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:33.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:33.026: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Jan 2 13:01:33.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:33.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:33.026: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:33.026: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:33.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:33.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:33.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:33.026: INFO: Jan 2 13:01:35.029: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:35.029: INFO: The status of Pod csi-azuredisk-node-win-lkpgx is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:35.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:35.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:35.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:35.029: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Jan 2 13:01:35.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:35.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:35.029: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:35.029: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:01:35.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:35.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:35.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:35.029: INFO: Jan 2 13:01:37.028: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:37.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:37.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:37.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:37.028: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Jan 2 13:01:37.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:37.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:37.028: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:37.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:37.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:37.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:37.028: INFO: Jan 2 13:01:39.035: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:39.035: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:39.035: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:39.035: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:39.035: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Jan 2 13:01:39.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:39.035: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:39.035: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:39.035: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:39.035: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:39.035: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:39.035: INFO: Jan 2 13:01:41.031: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:41.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:41.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:41.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:41.031: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Jan 2 13:01:41.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:41.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:41.031: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:41.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:41.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:41.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:41.031: INFO: Jan 2 13:01:43.210: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:43.210: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:43.210: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:43.210: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:43.210: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Jan 2 13:01:43.210: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:43.210: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:43.210: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:43.210: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:43.210: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:43.210: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:43.210: INFO: Jan 2 13:01:45.029: INFO: The status of Pod csi-azuredisk-node-win-c2jh9 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:45.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:45.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:45.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:45.030: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Jan 2 13:01:45.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:45.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:45.030: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC ContainersNotReady containers with unready status: [liveness-probe node-driver-registrar azuredisk]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:01:45.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:45.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:45.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:45.030: INFO: Jan 2 13:01:47.035: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:47.035: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:47.035: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:47.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Jan 2 13:01:47.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:47.035: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:47.035: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:47.035: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:47.035: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:47.035: INFO: Jan 2 13:01:49.035: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:49.035: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:49.035: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:49.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Jan 2 13:01:49.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:49.035: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:49.035: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:49.035: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:49.035: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:49.035: INFO: Jan 2 13:01:51.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:51.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:51.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:51.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Jan 2 13:01:51.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:51.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:51.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:51.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:51.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:51.027: INFO: Jan 2 13:01:53.032: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:53.032: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:53.032: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:53.032: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Jan 2 13:01:53.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:53.032: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:53.032: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:53.032: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:53.032: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:53.032: INFO: Jan 2 13:01:55.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:55.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:55.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:55.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Jan 2 13:01:55.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:55.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:55.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:55.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:55.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:55.024: INFO: Jan 2 13:01:57.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:57.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:57.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:57.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Jan 2 13:01:57.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:57.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:57.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:57.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:57.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:57.027: INFO: Jan 2 13:01:59.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:59.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:59.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:01:59.031: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Jan 2 13:01:59.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:01:59.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:01:59.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:59.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:59.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:01:59.031: INFO: Jan 2 13:02:01.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:01.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:01.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:01.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Jan 2 13:02:01.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:01.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:01.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:01.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:01.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:01.027: INFO: Jan 2 13:02:03.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:03.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:03.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:03.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Jan 2 13:02:03.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:03.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:03.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:03.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:03.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:03.027: INFO: Jan 2 13:02:05.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:05.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:05.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:05.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Jan 2 13:02:05.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:05.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:05.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:05.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:05.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:05.030: INFO: Jan 2 13:02:07.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:07.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:07.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:07.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Jan 2 13:02:07.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:07.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:07.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:07.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:07.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:07.030: INFO: Jan 2 13:02:09.035: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:09.035: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:09.035: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:09.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Jan 2 13:02:09.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:09.035: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:09.035: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:09.035: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:09.035: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:09.035: INFO: Jan 2 13:02:11.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:11.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:11.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:11.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Jan 2 13:02:11.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:11.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:11.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:11.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:11.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:11.029: INFO: Jan 2 13:02:13.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:13.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:13.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:13.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Jan 2 13:02:13.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:13.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:13.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:13.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:13.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:13.028: INFO: Jan 2 13:02:15.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:15.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:15.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:15.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Jan 2 13:02:15.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:15.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:15.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:15.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:15.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:15.028: INFO: Jan 2 13:02:17.032: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:17.032: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:17.032: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:17.032: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Jan 2 13:02:17.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:17.032: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:17.032: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:17.032: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:17.032: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:17.032: INFO: Jan 2 13:02:19.033: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:19.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:19.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:19.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Jan 2 13:02:19.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:19.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:19.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:19.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:19.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:19.033: INFO: Jan 2 13:02:21.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:21.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:21.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:21.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Jan 2 13:02:21.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:21.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:21.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:21.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:21.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:21.029: INFO: Jan 2 13:02:23.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:23.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:23.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:23.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Jan 2 13:02:23.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:23.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:23.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:23.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:23.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:23.026: INFO: Jan 2 13:02:25.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:25.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:25.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:25.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Jan 2 13:02:25.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:25.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:25.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:25.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:25.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:25.026: INFO: Jan 2 13:02:27.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:27.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:27.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:27.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Jan 2 13:02:27.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:27.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:27.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:27.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:27.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:27.029: INFO: Jan 2 13:02:29.036: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:29.036: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:29.036: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:29.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Jan 2 13:02:29.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:29.036: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:29.036: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:29.036: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:29.036: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:29.036: INFO: Jan 2 13:02:31.039: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:31.039: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:31.039: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:31.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Jan 2 13:02:31.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:31.039: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:31.039: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:31.039: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:31.039: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:31.039: INFO: Jan 2 13:02:33.206: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:33.206: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:33.206: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:33.206: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Jan 2 13:02:33.206: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:33.206: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:33.206: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:33.206: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:33.206: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:33.206: INFO: Jan 2 13:02:35.036: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:35.036: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:35.036: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:35.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Jan 2 13:02:35.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:35.036: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:35.036: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:35.036: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:35.036: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:35.036: INFO: Jan 2 13:02:37.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:37.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:37.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:37.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Jan 2 13:02:37.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:37.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:37.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:37.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:37.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:37.028: INFO: Jan 2 13:02:39.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:39.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:39.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:39.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Jan 2 13:02:39.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:39.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:39.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:39.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:39.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:39.030: INFO: Jan 2 13:02:41.038: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:41.038: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:41.038: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:41.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Jan 2 13:02:41.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:41.038: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:41.038: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:41.038: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:41.038: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:41.038: INFO: Jan 2 13:02:43.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:43.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:43.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:43.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Jan 2 13:02:43.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:43.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:43.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:43.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:43.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:43.029: INFO: Jan 2 13:02:45.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:45.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:45.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:45.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Jan 2 13:02:45.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:45.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:45.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:45.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:45.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:45.027: INFO: Jan 2 13:02:47.032: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:47.032: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:47.032: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:47.032: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Jan 2 13:02:47.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:47.032: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:47.032: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:47.032: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:47.032: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:47.032: INFO: Jan 2 13:02:49.033: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:49.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:49.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:49.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Jan 2 13:02:49.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:49.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:49.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:49.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:49.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:49.033: INFO: Jan 2 13:02:51.042: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:51.042: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:51.042: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:51.042: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Jan 2 13:02:51.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:51.042: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:51.042: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:51.042: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:51.042: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:51.042: INFO: Jan 2 13:02:53.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:53.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:53.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:53.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Jan 2 13:02:53.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:53.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:53.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:53.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:53.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:53.026: INFO: Jan 2 13:02:55.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:55.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:55.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:55.031: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Jan 2 13:02:55.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:55.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:55.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:55.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:55.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:55.031: INFO: Jan 2 13:02:57.032: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:57.032: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:57.032: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:57.032: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Jan 2 13:02:57.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:57.032: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:57.032: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:57.032: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:57.032: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:57.032: INFO: Jan 2 13:02:59.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:59.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:59.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:02:59.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Jan 2 13:02:59.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:02:59.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:02:59.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:59.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:59.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:02:59.029: INFO: Jan 2 13:03:01.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:01.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:01.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:01.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Jan 2 13:03:01.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:01.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:01.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:01.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:01.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:01.025: INFO: Jan 2 13:03:03.200: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:03.200: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:03.200: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:03.200: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Jan 2 13:03:03.200: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:03.200: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:03.200: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:03.200: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:03.200: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:03.200: INFO: Jan 2 13:03:05.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:05.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:05.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:05.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Jan 2 13:03:05.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:05.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:05.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:05.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:05.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:05.025: INFO: Jan 2 13:03:07.033: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:07.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:07.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:07.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Jan 2 13:03:07.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:07.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:07.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:07.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:07.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:07.033: INFO: Jan 2 13:03:09.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:09.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:09.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:09.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Jan 2 13:03:09.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:09.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:09.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:09.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:09.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:09.027: INFO: Jan 2 13:03:11.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:11.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:11.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:11.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Jan 2 13:03:11.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:11.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:11.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:11.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:11.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:11.028: INFO: Jan 2 13:03:13.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:13.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:13.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:13.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Jan 2 13:03:13.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:13.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:13.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:13.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:13.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:13.025: INFO: Jan 2 13:03:15.204: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:15.204: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:15.204: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:15.204: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Jan 2 13:03:15.204: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:15.204: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:15.204: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:15.204: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:15.204: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:15.204: INFO: Jan 2 13:03:17.033: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:17.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:17.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:17.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Jan 2 13:03:17.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:17.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:17.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:17.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:17.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:17.033: INFO: Jan 2 13:03:19.035: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:19.035: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:19.035: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:19.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Jan 2 13:03:19.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:19.035: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:19.035: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:19.035: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:19.035: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:19.035: INFO: Jan 2 13:03:21.041: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:21.041: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:21.041: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:21.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Jan 2 13:03:21.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:21.041: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:21.041: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:21.041: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:21.041: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:21.041: INFO: Jan 2 13:03:23.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:23.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:23.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:23.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Jan 2 13:03:23.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:23.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:23.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:23.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:23.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:23.027: INFO: Jan 2 13:03:25.032: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:25.032: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:25.032: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:25.032: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Jan 2 13:03:25.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:25.032: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:25.032: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:25.032: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:25.032: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:25.032: INFO: Jan 2 13:03:27.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:27.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:27.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:27.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Jan 2 13:03:27.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:27.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:27.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:27.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:27.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:27.027: INFO: Jan 2 13:03:29.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:29.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:29.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:29.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Jan 2 13:03:29.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:29.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:29.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:29.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:29.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:29.026: INFO: Jan 2 13:03:31.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:31.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:31.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:31.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Jan 2 13:03:31.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:31.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:31.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:31.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:31.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:31.025: INFO: Jan 2 13:03:33.202: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:33.202: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:33.202: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:33.202: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Jan 2 13:03:33.202: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:33.202: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:33.202: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:33.202: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:33.202: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:33.202: INFO: Jan 2 13:03:35.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:35.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:35.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:35.031: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Jan 2 13:03:35.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:35.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:35.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:35.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:35.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:35.031: INFO: Jan 2 13:03:37.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:37.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:37.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:37.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Jan 2 13:03:37.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:37.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:37.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:37.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:37.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:37.028: INFO: Jan 2 13:03:39.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:39.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:39.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:39.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Jan 2 13:03:39.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:39.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:39.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:39.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:39.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:39.027: INFO: Jan 2 13:03:41.036: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:41.036: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:41.036: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:41.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Jan 2 13:03:41.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:41.036: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:41.036: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:41.036: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:41.036: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:41.036: INFO: Jan 2 13:03:43.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:43.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:43.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:43.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Jan 2 13:03:43.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:43.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:43.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:43.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:43.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:43.027: INFO: Jan 2 13:03:45.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:45.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:45.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:45.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Jan 2 13:03:45.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:45.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:45.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:45.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:45.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:45.025: INFO: Jan 2 13:03:47.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:47.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:47.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:47.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Jan 2 13:03:47.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:47.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:47.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:47.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:47.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:47.029: INFO: Jan 2 13:03:49.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:49.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:49.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:49.031: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Jan 2 13:03:49.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:49.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:49.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:49.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:49.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:49.031: INFO: Jan 2 13:03:51.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:51.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:51.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:51.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Jan 2 13:03:51.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:51.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:51.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:51.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:51.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:51.027: INFO: Jan 2 13:03:53.035: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:53.035: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:53.035: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:53.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Jan 2 13:03:53.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:53.035: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:53.035: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:53.035: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:53.035: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:53.035: INFO: Jan 2 13:03:55.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:55.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:55.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:55.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Jan 2 13:03:55.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:55.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:55.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:55.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:55.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:55.028: INFO: Jan 2 13:03:57.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:57.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:57.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:57.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Jan 2 13:03:57.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:57.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:57.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:57.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:57.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:57.026: INFO: Jan 2 13:03:59.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:59.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:59.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:03:59.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Jan 2 13:03:59.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:03:59.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:03:59.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:59.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:59.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:03:59.029: INFO: Jan 2 13:04:01.212: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:01.212: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:01.212: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:01.212: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Jan 2 13:04:01.212: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:01.212: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:01.212: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:01.212: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:01.212: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:01.212: INFO: Jan 2 13:04:03.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:03.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:03.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:03.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Jan 2 13:04:03.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:03.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:03.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:03.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:03.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:03.027: INFO: Jan 2 13:04:05.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:05.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:05.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:05.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Jan 2 13:04:05.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:05.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:05.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:05.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:05.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:05.028: INFO: Jan 2 13:04:07.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:07.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:07.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:07.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Jan 2 13:04:07.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:07.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:07.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:07.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:07.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:07.025: INFO: Jan 2 13:04:09.041: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:09.041: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:09.041: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:09.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Jan 2 13:04:09.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:09.041: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:09.041: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:09.041: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:09.041: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:09.041: INFO: Jan 2 13:04:11.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:11.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:11.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:11.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Jan 2 13:04:11.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:11.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:11.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:11.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:11.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:11.029: INFO: Jan 2 13:04:13.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:13.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:13.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:13.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Jan 2 13:04:13.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:13.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:13.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:13.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:13.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:13.023: INFO: Jan 2 13:04:15.103: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:15.103: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:15.103: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:15.103: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Jan 2 13:04:15.103: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:15.103: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:15.103: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:15.103: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:15.103: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:15.103: INFO: Jan 2 13:04:17.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:17.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:17.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:17.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Jan 2 13:04:17.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:17.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:17.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:17.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:17.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:17.024: INFO: Jan 2 13:04:19.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:19.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:19.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:19.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Jan 2 13:04:19.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:19.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:19.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:19.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:19.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:19.026: INFO: Jan 2 13:04:21.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:21.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:21.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:21.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Jan 2 13:04:21.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:21.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:21.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:21.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:21.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:21.024: INFO: Jan 2 13:04:23.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:23.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:23.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:23.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Jan 2 13:04:23.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:23.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:23.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:23.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:23.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:23.023: INFO: Jan 2 13:04:25.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:25.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:25.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:25.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Jan 2 13:04:25.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:25.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:25.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:25.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:25.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:25.024: INFO: Jan 2 13:04:27.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:27.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:27.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:27.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Jan 2 13:04:27.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:27.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:27.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:27.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:27.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:27.024: INFO: Jan 2 13:04:29.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:29.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:29.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:29.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Jan 2 13:04:29.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:29.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:29.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:29.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:29.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:29.025: INFO: Jan 2 13:04:31.200: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:31.200: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:31.200: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:31.200: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Jan 2 13:04:31.200: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:31.200: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:31.200: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:31.200: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:31.200: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:31.200: INFO: Jan 2 13:04:33.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:33.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:33.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:33.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Jan 2 13:04:33.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:33.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:33.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:33.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:33.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:33.023: INFO: Jan 2 13:04:35.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:35.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:35.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:35.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Jan 2 13:04:35.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:35.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:35.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:35.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:35.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:35.023: INFO: Jan 2 13:04:37.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:37.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:37.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:37.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Jan 2 13:04:37.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:37.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:37.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:37.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:37.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:37.024: INFO: Jan 2 13:04:39.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:39.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:39.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:39.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Jan 2 13:04:39.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:39.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:39.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:39.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:39.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:39.022: INFO: Jan 2 13:04:41.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:41.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:41.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:41.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Jan 2 13:04:41.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:41.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:41.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:41.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:41.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:41.022: INFO: Jan 2 13:04:43.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:43.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:43.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:43.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Jan 2 13:04:43.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:43.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:43.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:43.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:43.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:43.030: INFO: Jan 2 13:04:45.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:45.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:45.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:45.031: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Jan 2 13:04:45.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:45.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:45.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:45.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:45.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:45.031: INFO: Jan 2 13:04:47.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:47.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:47.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:47.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Jan 2 13:04:47.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:47.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:47.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:47.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:47.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:47.023: INFO: Jan 2 13:04:49.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:49.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:49.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:49.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Jan 2 13:04:49.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:49.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:49.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:49.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:49.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:49.023: INFO: Jan 2 13:04:51.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:51.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:51.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:51.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Jan 2 13:04:51.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:51.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:51.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:51.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:51.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:51.023: INFO: Jan 2 13:04:53.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:53.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:53.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:53.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Jan 2 13:04:53.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:53.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:53.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:53.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:53.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:53.026: INFO: Jan 2 13:04:55.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:55.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:55.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:55.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Jan 2 13:04:55.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:55.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:55.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:55.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:55.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:55.023: INFO: Jan 2 13:04:57.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:57.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:57.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:57.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Jan 2 13:04:57.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:57.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:57.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:57.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:57.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:57.024: INFO: Jan 2 13:04:59.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:59.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:59.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:04:59.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Jan 2 13:04:59.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:04:59.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:04:59.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:59.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:59.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:04:59.026: INFO: Jan 2 13:05:01.031: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:01.031: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:01.031: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:01.031: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Jan 2 13:05:01.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:01.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:01.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:01.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:01.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:01.031: INFO: Jan 2 13:05:03.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:03.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:03.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:03.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Jan 2 13:05:03.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:03.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:03.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:03.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:03.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:03.023: INFO: Jan 2 13:05:05.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:05.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:05.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:05.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Jan 2 13:05:05.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:05.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:05.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:05.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:05.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:05.025: INFO: Jan 2 13:05:07.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:07.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:07.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:07.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Jan 2 13:05:07.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:07.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:07.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:07.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:07.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:07.023: INFO: Jan 2 13:05:09.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:09.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:09.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:09.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Jan 2 13:05:09.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:09.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:09.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:09.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:09.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:09.024: INFO: Jan 2 13:05:11.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:11.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:11.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:11.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Jan 2 13:05:11.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:11.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:11.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:11.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:11.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:11.024: INFO: Jan 2 13:05:13.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:13.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:13.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:13.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Jan 2 13:05:13.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:13.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:13.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:13.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:13.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:13.023: INFO: Jan 2 13:05:15.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:15.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:15.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:15.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Jan 2 13:05:15.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:15.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:15.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:15.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:15.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:15.024: INFO: Jan 2 13:05:17.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:17.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:17.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:17.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Jan 2 13:05:17.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:17.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:17.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:17.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:17.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:17.022: INFO: Jan 2 13:05:19.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:19.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:19.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:19.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Jan 2 13:05:19.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:19.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:19.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:19.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:19.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:19.024: INFO: Jan 2 13:05:21.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:21.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:21.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:21.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Jan 2 13:05:21.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:21.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:21.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:21.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:21.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:21.028: INFO: Jan 2 13:05:23.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:23.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:23.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:23.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Jan 2 13:05:23.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:23.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:23.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:23.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:23.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:23.022: INFO: Jan 2 13:05:25.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:25.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:25.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:25.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Jan 2 13:05:25.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:25.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:25.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:25.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:25.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:25.023: INFO: Jan 2 13:05:27.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:27.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:27.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:27.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Jan 2 13:05:27.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:27.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:27.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:27.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:27.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:27.022: INFO: Jan 2 13:05:29.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:29.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:29.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:29.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Jan 2 13:05:29.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:29.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:29.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:29.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:29.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:29.030: INFO: Jan 2 13:05:31.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:31.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:31.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:31.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Jan 2 13:05:31.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:31.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:31.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:31.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:31.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:31.023: INFO: Jan 2 13:05:33.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:33.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:33.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:33.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Jan 2 13:05:33.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:33.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:33.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:33.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:33.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:33.023: INFO: Jan 2 13:05:35.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:35.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:35.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:35.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Jan 2 13:05:35.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:35.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:35.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:35.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:35.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:35.024: INFO: Jan 2 13:05:37.199: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:37.199: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:37.199: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:37.199: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Jan 2 13:05:37.199: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:37.199: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:37.199: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:37.199: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:37.199: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:37.199: INFO: Jan 2 13:05:39.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:39.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:39.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:39.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Jan 2 13:05:39.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:39.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:39.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:39.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:39.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:39.023: INFO: Jan 2 13:05:41.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:41.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:41.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:41.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Jan 2 13:05:41.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:41.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:41.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:41.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:41.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:41.023: INFO: Jan 2 13:05:43.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:43.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:43.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:43.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Jan 2 13:05:43.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:43.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:43.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:43.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:43.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:43.022: INFO: Jan 2 13:05:45.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:45.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:45.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:45.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Jan 2 13:05:45.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:45.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:45.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:45.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:45.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:45.024: INFO: Jan 2 13:05:47.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:47.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:47.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:47.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Jan 2 13:05:47.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:47.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:47.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:47.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:47.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:47.024: INFO: Jan 2 13:05:49.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:49.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:49.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:49.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Jan 2 13:05:49.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:49.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:49.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:49.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:49.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:49.024: INFO: Jan 2 13:05:51.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:51.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:51.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:51.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Jan 2 13:05:51.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:51.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:51.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:51.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:51.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:51.022: INFO: Jan 2 13:05:53.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:53.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:53.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:53.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Jan 2 13:05:53.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:53.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:53.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:53.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:53.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:53.023: INFO: Jan 2 13:05:55.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:55.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:55.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:55.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Jan 2 13:05:55.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:55.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:55.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:55.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:55.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:55.024: INFO: Jan 2 13:05:57.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:57.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:57.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:57.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Jan 2 13:05:57.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:57.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:57.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:57.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:57.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:57.023: INFO: Jan 2 13:05:59.198: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:59.198: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:59.198: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:05:59.198: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Jan 2 13:05:59.198: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:05:59.198: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:05:59.198: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:59.198: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:59.198: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:05:59.198: INFO: Jan 2 13:06:01.063: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:01.063: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:01.063: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:01.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Jan 2 13:06:01.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:01.063: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:01.063: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:01.063: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:01.063: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:01.063: INFO: Jan 2 13:06:03.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:03.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:03.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:03.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Jan 2 13:06:03.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:03.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:03.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:03.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:03.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:03.023: INFO: Jan 2 13:06:05.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:05.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:05.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:05.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Jan 2 13:06:05.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:05.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:05.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:05.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:05.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:05.022: INFO: Jan 2 13:06:07.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:07.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:07.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:07.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Jan 2 13:06:07.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:07.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:07.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:07.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:07.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:07.023: INFO: Jan 2 13:06:09.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:09.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:09.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:09.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Jan 2 13:06:09.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:09.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:09.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:09.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:09.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:09.025: INFO: Jan 2 13:06:11.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:11.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:11.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:11.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Jan 2 13:06:11.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:11.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:11.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:11.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:11.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:11.024: INFO: Jan 2 13:06:13.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:13.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:13.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:13.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Jan 2 13:06:13.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:13.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:13.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:13.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:13.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:13.022: INFO: Jan 2 13:06:15.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:15.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:15.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:15.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Jan 2 13:06:15.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:15.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:15.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:15.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:15.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:15.025: INFO: Jan 2 13:06:17.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:17.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:17.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:17.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Jan 2 13:06:17.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:17.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:17.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:17.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:17.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:17.030: INFO: Jan 2 13:06:19.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:19.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:19.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:19.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Jan 2 13:06:19.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:19.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:19.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:19.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:19.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:19.023: INFO: Jan 2 13:06:21.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:21.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:21.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:21.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Jan 2 13:06:21.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:21.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:21.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:21.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:21.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:21.024: INFO: Jan 2 13:06:23.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:23.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:23.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:23.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Jan 2 13:06:23.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:23.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:23.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:23.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:23.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:23.024: INFO: Jan 2 13:06:25.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:25.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:25.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:25.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Jan 2 13:06:25.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:25.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:25.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:25.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:25.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:25.022: INFO: Jan 2 13:06:27.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:27.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:27.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:27.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Jan 2 13:06:27.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:27.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:27.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:27.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:27.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:27.022: INFO: Jan 2 13:06:29.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:29.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:29.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:29.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Jan 2 13:06:29.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:29.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:29.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:29.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:29.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:29.024: INFO: Jan 2 13:06:31.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:31.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:31.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:31.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Jan 2 13:06:31.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:31.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:31.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:31.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:31.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:31.022: INFO: Jan 2 13:06:33.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:33.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:33.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:33.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Jan 2 13:06:33.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:33.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:33.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:33.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:33.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:33.024: INFO: Jan 2 13:06:35.079: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:35.079: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:35.079: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:35.079: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Jan 2 13:06:35.079: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:35.079: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:35.079: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:35.079: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:35.079: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:35.079: INFO: Jan 2 13:06:37.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:37.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:37.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:37.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Jan 2 13:06:37.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:37.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:37.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:37.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:37.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:37.022: INFO: Jan 2 13:06:39.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:39.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:39.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:39.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Jan 2 13:06:39.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:39.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:39.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:39.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:39.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:39.025: INFO: Jan 2 13:06:41.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:41.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:41.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:41.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Jan 2 13:06:41.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:41.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:41.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:41.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:41.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:41.023: INFO: Jan 2 13:06:43.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:43.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:43.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:43.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Jan 2 13:06:43.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:43.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:43.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:43.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:43.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:43.023: INFO: Jan 2 13:06:45.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:45.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:45.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:45.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Jan 2 13:06:45.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:45.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:45.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:45.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:45.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:45.023: INFO: Jan 2 13:06:47.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:47.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:47.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:47.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Jan 2 13:06:47.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:47.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:47.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:47.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:47.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:47.025: INFO: Jan 2 13:06:49.021: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:49.021: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:49.021: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:49.021: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Jan 2 13:06:49.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:49.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:49.021: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:49.021: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:49.021: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:49.021: INFO: Jan 2 13:06:53.680: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:53.680: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:53.680: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:53.680: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (353 seconds elapsed) Jan 2 13:06:53.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:53.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:53.680: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:53.680: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:53.680: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:53.680: INFO: Jan 2 13:06:55.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:55.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:55.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:55.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Jan 2 13:06:55.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:55.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:55.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:55.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:55.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:55.024: INFO: Jan 2 13:06:57.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:57.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:57.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:57.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Jan 2 13:06:57.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:57.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:57.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:57.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:57.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:57.022: INFO: Jan 2 13:06:59.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:59.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:59.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:06:59.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Jan 2 13:06:59.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:06:59.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:06:59.031: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:59.031: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:59.031: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:06:59.031: INFO: Jan 2 13:07:01.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:01.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:01.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:01.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Jan 2 13:07:01.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:01.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:01.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:01.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:01.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:01.023: INFO: Jan 2 13:07:03.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:03.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:03.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:03.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Jan 2 13:07:03.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:03.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:03.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:03.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:03.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:03.023: INFO: Jan 2 13:07:05.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:05.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:05.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:05.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Jan 2 13:07:05.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:05.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:05.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:05.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:05.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:05.027: INFO: Jan 2 13:07:07.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:07.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:07.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:07.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Jan 2 13:07:07.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:07.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:07.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:07.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:07.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:07.024: INFO: Jan 2 13:07:09.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:09.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:09.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:09.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Jan 2 13:07:09.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:09.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:09.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:09.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:09.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:09.024: INFO: Jan 2 13:07:11.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:11.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:11.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:11.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Jan 2 13:07:11.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:11.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:11.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:11.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:11.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:11.023: INFO: Jan 2 13:07:13.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:13.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:13.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:13.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Jan 2 13:07:13.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:13.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:13.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:13.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:13.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:13.023: INFO: Jan 2 13:07:15.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:15.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:15.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:15.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Jan 2 13:07:15.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:15.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:15.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:15.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:15.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:15.022: INFO: Jan 2 13:07:17.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:17.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:17.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:17.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Jan 2 13:07:17.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:17.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:17.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:17.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:17.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:17.025: INFO: Jan 2 13:07:19.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:19.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:19.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:19.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Jan 2 13:07:19.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:19.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:19.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:19.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:19.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:19.024: INFO: Jan 2 13:07:21.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:21.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:21.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:21.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Jan 2 13:07:21.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:21.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:21.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:21.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:21.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:21.023: INFO: Jan 2 13:07:23.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:23.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:23.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:23.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Jan 2 13:07:23.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:23.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:23.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:23.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:23.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:23.023: INFO: Jan 2 13:07:25.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:25.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:25.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:25.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Jan 2 13:07:25.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:25.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:25.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:25.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:25.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:25.023: INFO: Jan 2 13:07:27.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:27.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:27.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:27.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Jan 2 13:07:27.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:27.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:27.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:27.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:27.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:27.025: INFO: Jan 2 13:07:29.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:29.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:29.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:29.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Jan 2 13:07:29.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:29.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:29.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:29.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:29.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:29.022: INFO: Jan 2 13:07:31.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:31.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:31.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:31.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Jan 2 13:07:31.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:31.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:31.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:31.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:31.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:31.024: INFO: Jan 2 13:07:33.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:33.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:33.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:33.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Jan 2 13:07:33.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:33.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:33.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:33.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:33.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:33.022: INFO: Jan 2 13:07:35.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:35.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:35.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:35.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Jan 2 13:07:35.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:35.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:35.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:35.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:35.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:35.030: INFO: Jan 2 13:07:37.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:37.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:37.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:37.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Jan 2 13:07:37.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:37.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:37.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:37.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:37.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:37.023: INFO: Jan 2 13:07:39.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:39.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:39.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:39.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Jan 2 13:07:39.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:39.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:39.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:39.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:39.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:39.026: INFO: Jan 2 13:07:41.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:41.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:41.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:41.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Jan 2 13:07:41.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:41.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:41.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:41.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:41.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:41.023: INFO: Jan 2 13:07:43.033: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:43.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:43.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:43.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Jan 2 13:07:43.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:43.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:43.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:43.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:43.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:43.033: INFO: Jan 2 13:07:45.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:45.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:45.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:45.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Jan 2 13:07:45.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:45.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:45.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:45.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:45.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:45.024: INFO: Jan 2 13:07:47.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:47.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:47.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:47.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Jan 2 13:07:47.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:47.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:47.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:47.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:47.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:47.024: INFO: Jan 2 13:07:49.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:49.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:49.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:49.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Jan 2 13:07:49.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:49.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:49.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:49.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:49.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:49.022: INFO: Jan 2 13:07:51.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:51.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:51.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:51.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Jan 2 13:07:51.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:51.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:51.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:51.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:51.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:51.024: INFO: Jan 2 13:07:53.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:53.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:53.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:53.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Jan 2 13:07:53.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:53.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:53.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:53.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:53.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:53.022: INFO: Jan 2 13:07:55.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:55.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:55.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:55.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Jan 2 13:07:55.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:55.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:55.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:55.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:55.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:55.022: INFO: Jan 2 13:07:57.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:57.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:57.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:57.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Jan 2 13:07:57.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:57.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:57.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:57.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:57.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:57.025: INFO: Jan 2 13:07:59.021: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:59.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:59.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:07:59.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Jan 2 13:07:59.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:07:59.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:07:59.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:59.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:59.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:07:59.022: INFO: Jan 2 13:08:01.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:01.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:01.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:01.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Jan 2 13:08:01.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:01.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:01.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:01.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:01.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:01.023: INFO: Jan 2 13:08:03.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:03.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:03.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:03.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Jan 2 13:08:03.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:03.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:03.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:03.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:03.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:03.022: INFO: Jan 2 13:08:05.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:05.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:05.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:05.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Jan 2 13:08:05.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:05.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:05.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:05.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:05.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:05.029: INFO: Jan 2 13:08:07.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:07.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:07.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:07.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Jan 2 13:08:07.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:07.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:07.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:07.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:07.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:07.023: INFO: Jan 2 13:08:09.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:09.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:09.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:09.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Jan 2 13:08:09.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:09.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:09.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:09.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:09.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:09.028: INFO: Jan 2 13:08:11.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:11.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:11.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:11.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Jan 2 13:08:11.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:11.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:11.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:11.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:11.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:11.025: INFO: Jan 2 13:08:13.027: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:13.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:13.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:13.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Jan 2 13:08:13.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:13.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:13.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:13.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:13.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:13.027: INFO: Jan 2 13:08:15.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:15.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:15.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:15.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Jan 2 13:08:15.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:15.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:15.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:15.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:15.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:15.023: INFO: Jan 2 13:08:17.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:17.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:17.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:17.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Jan 2 13:08:17.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:17.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:17.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:17.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:17.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:17.023: INFO: Jan 2 13:08:19.021: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:19.021: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:19.021: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:19.021: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Jan 2 13:08:19.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:19.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:19.021: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:19.021: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:19.021: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:19.021: INFO: Jan 2 13:08:21.021: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:21.021: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:21.021: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:21.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Jan 2 13:08:21.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:21.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:21.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:21.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:21.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:21.022: INFO: Jan 2 13:08:23.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:23.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:23.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:23.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Jan 2 13:08:23.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:23.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:23.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:23.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:23.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:23.024: INFO: Jan 2 13:08:25.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:25.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:25.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:25.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Jan 2 13:08:25.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:25.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:25.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:25.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:25.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:25.029: INFO: Jan 2 13:08:27.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:27.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:27.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:27.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Jan 2 13:08:27.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:27.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:27.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:27.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:27.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:27.022: INFO: Jan 2 13:08:29.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:29.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:29.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:29.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Jan 2 13:08:29.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:29.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:29.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:29.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:29.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:29.028: INFO: Jan 2 13:08:31.199: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:31.199: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:31.199: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:31.199: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Jan 2 13:08:31.199: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:31.199: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:31.199: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:31.199: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:31.199: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:31.199: INFO: Jan 2 13:08:33.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:33.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:33.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:33.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Jan 2 13:08:33.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:33.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:33.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:33.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:33.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:33.028: INFO: Jan 2 13:08:35.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:35.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:35.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:35.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Jan 2 13:08:35.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:35.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:35.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:35.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:35.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:35.022: INFO: Jan 2 13:08:37.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:37.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:37.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:37.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Jan 2 13:08:37.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:37.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:37.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:37.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:37.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:37.026: INFO: Jan 2 13:08:39.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:39.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:39.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:39.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Jan 2 13:08:39.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:39.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:39.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:39.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:39.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:39.025: INFO: Jan 2 13:08:41.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:41.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:41.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:41.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Jan 2 13:08:41.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:41.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:41.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:41.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:41.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:41.026: INFO: Jan 2 13:08:43.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:43.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:43.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:43.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Jan 2 13:08:43.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:43.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:43.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:43.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:43.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:43.024: INFO: Jan 2 13:08:45.157: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:45.157: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:45.157: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:45.157: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Jan 2 13:08:45.157: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:45.157: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:45.157: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:45.157: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:45.157: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:45.157: INFO: Jan 2 13:08:47.033: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:47.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:47.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:47.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Jan 2 13:08:47.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:47.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:47.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:47.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:47.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:47.033: INFO: Jan 2 13:08:49.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:49.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:49.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:49.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Jan 2 13:08:49.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:49.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:49.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:49.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:49.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:49.023: INFO: Jan 2 13:08:51.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:51.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:51.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:51.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Jan 2 13:08:51.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:51.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:51.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:51.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:51.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:51.025: INFO: Jan 2 13:08:53.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:53.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:53.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:53.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Jan 2 13:08:53.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:53.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:53.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:53.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:53.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:53.029: INFO: Jan 2 13:08:55.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:55.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:55.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:55.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Jan 2 13:08:55.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:55.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:55.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:55.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:55.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:55.029: INFO: Jan 2 13:08:57.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:57.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:57.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:57.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Jan 2 13:08:57.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:57.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:57.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:57.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:57.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:57.024: INFO: Jan 2 13:08:59.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:59.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:59.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:08:59.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Jan 2 13:08:59.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:08:59.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:08:59.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:59.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:59.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:08:59.023: INFO: Jan 2 13:09:01.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:01.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:01.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:01.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Jan 2 13:09:01.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:01.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:01.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:01.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:01.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:01.024: INFO: Jan 2 13:09:03.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:03.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:03.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:03.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Jan 2 13:09:03.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:03.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:03.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:03.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:03.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:03.029: INFO: Jan 2 13:09:05.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:05.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:05.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:05.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Jan 2 13:09:05.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:05.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:05.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:05.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:05.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:05.026: INFO: Jan 2 13:09:07.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:07.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:07.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:07.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Jan 2 13:09:07.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:07.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:07.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:07.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:07.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:07.023: INFO: Jan 2 13:09:09.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:09.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:09.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:09.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Jan 2 13:09:09.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:09.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:09.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:09.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:09.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:09.023: INFO: Jan 2 13:09:11.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:11.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:11.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:11.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Jan 2 13:09:11.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:11.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:11.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:11.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:11.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:11.024: INFO: Jan 2 13:09:13.043: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:13.043: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:13.043: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:13.043: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Jan 2 13:09:13.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:13.043: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:13.043: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:13.043: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:13.043: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:13.043: INFO: Jan 2 13:09:15.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:15.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:15.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:15.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Jan 2 13:09:15.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:15.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:15.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:15.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:15.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:15.024: INFO: Jan 2 13:09:17.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:17.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:17.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:17.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Jan 2 13:09:17.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:17.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:17.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:17.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:17.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:17.023: INFO: Jan 2 13:09:19.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:19.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:19.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:19.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Jan 2 13:09:19.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:19.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:19.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:19.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:19.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:19.022: INFO: Jan 2 13:09:21.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:21.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:21.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:21.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Jan 2 13:09:21.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:21.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:21.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:21.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:21.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:21.023: INFO: Jan 2 13:09:23.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:23.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:23.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:23.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Jan 2 13:09:23.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:23.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:23.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:23.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:23.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:23.022: INFO: Jan 2 13:09:25.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:25.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:25.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:25.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Jan 2 13:09:25.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:25.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:25.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:25.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:25.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:25.024: INFO: Jan 2 13:09:27.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:27.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:27.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:27.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Jan 2 13:09:27.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:27.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:27.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:27.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:27.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:27.022: INFO: Jan 2 13:09:29.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:29.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:29.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:29.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Jan 2 13:09:29.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:29.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:29.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:29.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:29.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:29.023: INFO: Jan 2 13:09:31.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:31.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:31.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:31.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Jan 2 13:09:31.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:31.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:31.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:31.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:31.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:31.023: INFO: Jan 2 13:09:33.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:33.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:33.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:33.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Jan 2 13:09:33.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:33.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:33.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:33.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:33.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:33.025: INFO: Jan 2 13:09:35.200: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:35.200: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:35.200: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:35.200: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Jan 2 13:09:35.200: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:35.200: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:35.200: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:35.200: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:35.200: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:35.200: INFO: Jan 2 13:09:37.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:37.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:37.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:37.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Jan 2 13:09:37.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:37.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:37.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:37.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:37.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:37.023: INFO: Jan 2 13:09:39.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:39.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:39.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:39.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Jan 2 13:09:39.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:39.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:39.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:39.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:39.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:39.023: INFO: Jan 2 13:09:41.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:41.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:41.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:41.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Jan 2 13:09:41.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:41.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:41.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:41.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:41.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:41.022: INFO: Jan 2 13:09:43.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:43.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:43.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:43.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Jan 2 13:09:43.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:43.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:43.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:43.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:43.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:43.022: INFO: Jan 2 13:09:45.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:45.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:45.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:45.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Jan 2 13:09:45.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:45.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:45.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:45.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:45.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:45.024: INFO: Jan 2 13:09:47.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:47.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:47.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:47.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Jan 2 13:09:47.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:47.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:47.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:47.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:47.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:47.024: INFO: Jan 2 13:09:49.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:49.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:49.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:49.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Jan 2 13:09:49.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:49.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:49.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:49.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:49.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:49.024: INFO: Jan 2 13:09:51.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:51.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:51.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:51.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Jan 2 13:09:51.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:51.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:51.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:51.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:51.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:51.023: INFO: Jan 2 13:09:53.034: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:53.034: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:53.034: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:53.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Jan 2 13:09:53.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:53.034: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:53.034: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:53.034: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:53.034: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:53.034: INFO: Jan 2 13:09:55.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:55.027: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:55.027: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:55.027: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Jan 2 13:09:55.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:55.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:55.027: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:55.027: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:55.027: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:55.027: INFO: Jan 2 13:09:57.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:57.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:57.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:57.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Jan 2 13:09:57.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:57.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:57.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:57.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:57.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:57.022: INFO: Jan 2 13:09:59.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:59.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:59.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:09:59.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Jan 2 13:09:59.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:09:59.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:09:59.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:59.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:59.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:09:59.023: INFO: Jan 2 13:10:01.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:01.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:01.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:01.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Jan 2 13:10:01.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:01.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:01.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:01.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:01.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:01.023: INFO: Jan 2 13:10:03.029: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:03.029: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:03.029: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:03.029: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Jan 2 13:10:03.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:03.029: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:03.029: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:03.029: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:03.029: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:03.029: INFO: Jan 2 13:10:05.038: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:05.038: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:05.038: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:05.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Jan 2 13:10:05.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:05.038: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:05.038: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:05.038: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:05.038: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:05.038: INFO: Jan 2 13:10:07.026: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:07.026: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:07.026: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:07.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Jan 2 13:10:07.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:07.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:07.026: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:07.026: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:07.026: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:07.026: INFO: Jan 2 13:10:09.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:09.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:09.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:09.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Jan 2 13:10:09.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:09.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:09.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:09.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:09.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:09.024: INFO: Jan 2 13:10:11.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:11.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:11.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:11.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Jan 2 13:10:11.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:11.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:11.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:11.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:11.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:11.022: INFO: Jan 2 13:10:13.033: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:13.033: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:13.033: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:13.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Jan 2 13:10:13.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:13.033: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:13.033: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:13.033: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:13.033: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:13.033: INFO: Jan 2 13:10:15.030: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:15.030: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:15.030: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:15.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Jan 2 13:10:15.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:15.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:15.030: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:15.030: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:15.030: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:15.030: INFO: Jan 2 13:10:17.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:17.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:17.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:17.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Jan 2 13:10:17.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:17.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:17.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:17.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:17.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:17.025: INFO: Jan 2 13:10:19.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:19.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:19.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:19.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Jan 2 13:10:19.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:19.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:19.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:19.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:19.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:19.024: INFO: Jan 2 13:10:21.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:21.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:21.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:21.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Jan 2 13:10:21.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:21.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:21.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:21.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:21.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:21.023: INFO: Jan 2 13:10:23.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:23.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:23.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:23.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Jan 2 13:10:23.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:23.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:23.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:23.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:23.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:23.022: INFO: Jan 2 13:10:25.038: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:25.038: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:25.038: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:25.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Jan 2 13:10:25.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:25.038: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:25.038: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:25.038: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:25.038: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:25.038: INFO: Jan 2 13:10:27.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:27.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:27.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:27.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Jan 2 13:10:27.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:27.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:27.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:27.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:27.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:27.023: INFO: Jan 2 13:10:29.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:29.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:29.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:29.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Jan 2 13:10:29.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:29.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:29.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:29.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:29.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:29.024: INFO: Jan 2 13:10:31.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:31.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:31.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:31.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Jan 2 13:10:31.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:31.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:31.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:31.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:31.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:31.028: INFO: Jan 2 13:10:33.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:33.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:33.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:33.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Jan 2 13:10:33.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:33.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:33.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:33.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:33.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:33.022: INFO: Jan 2 13:10:35.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:35.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:35.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:35.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Jan 2 13:10:35.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:35.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:35.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:35.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:35.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:35.022: INFO: Jan 2 13:10:37.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:37.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:37.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:37.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Jan 2 13:10:37.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:37.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:37.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:37.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:37.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:37.022: INFO: Jan 2 13:10:39.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:39.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:39.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:39.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Jan 2 13:10:39.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:39.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:39.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:39.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:39.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:39.025: INFO: Jan 2 13:10:41.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:41.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:41.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:41.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Jan 2 13:10:41.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:41.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:41.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:41.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:41.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:41.023: INFO: Jan 2 13:10:43.028: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:43.028: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:43.028: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:43.028: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Jan 2 13:10:43.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:43.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:43.028: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:43.028: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:43.028: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:43.028: INFO: Jan 2 13:10:45.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:45.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:45.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:45.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Jan 2 13:10:45.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:45.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:45.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:45.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:45.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:45.023: INFO: Jan 2 13:10:47.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:47.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:47.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:47.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Jan 2 13:10:47.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:47.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:47.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:47.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:47.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:47.022: INFO: Jan 2 13:10:49.024: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:49.024: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:49.024: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:49.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Jan 2 13:10:49.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:49.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:49.024: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:49.024: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:49.024: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:49.024: INFO: Jan 2 13:10:51.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:51.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:51.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:51.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Jan 2 13:10:51.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:51.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:51.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:51.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:51.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:51.025: INFO: Jan 2 13:10:53.025: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:53.025: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:53.025: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:53.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Jan 2 13:10:53.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:53.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:53.025: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:53.025: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:53.025: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:53.025: INFO: Jan 2 13:10:55.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:55.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:55.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:55.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Jan 2 13:10:55.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:55.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:55.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:55.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:55.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:55.023: INFO: Jan 2 13:10:57.023: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:57.023: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:57.023: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:57.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Jan 2 13:10:57.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:57.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:57.023: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:57.023: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:57.023: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:57.023: INFO: Jan 2 13:10:59.022: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:59.022: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:59.022: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:10:59.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Jan 2 13:10:59.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:10:59.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:10:59.022: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:59.022: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:59.022: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:10:59.022: INFO: Jan 2 13:11:01.094: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:11:01.094: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:11:01.094: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:11:01.094: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 2 13:11:01.094: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:11:01.094: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:11:01.094: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.094: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.094: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.094: INFO: Jan 2 13:11:01.493: INFO: The status of Pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:11:01.493: INFO: The status of Pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:11:01.493: INFO: The status of Pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 2 13:11:01.493: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (601 seconds elapsed) Jan 2 13:11:01.493: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 2 13:11:01.493: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:11:01.493: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.493: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.493: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.493: INFO: STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/02/23 13:11:01.493 STEP: Found 150 events. - test/e2e/framework/debug/dump.go:46 @ 01/02/23 13:11:01.634 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:03 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-t8nagj-control-plane-c8pmj_8e03a84e-6556-4ffc-a16a-70b8f1369c6e became leader Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:05 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-t8nagj-control-plane-c8pmj_b0fbc4c9-5841-4ea4-aa7b-a3a1879519bf became leader Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:11 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:11 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-zj22k Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:11 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-kpxkv Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:11 +0000 UTC - event for coredns-56f4c55bf9-kpxkv: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:11 +0000 UTC - event for coredns-56f4c55bf9-zj22k: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:11 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-4trtr Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:11 +0000 UTC - event for kube-proxy-4trtr: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-4trtr to capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:12 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-4trtr Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:14 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-gmhrm Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:14 +0000 UTC - event for kube-proxy-gmhrm: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-gmhrm to capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:15 +0000 UTC - event for kube-proxy-gmhrm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.664_53520b42c98526" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:20 +0000 UTC - event for kube-proxy-gmhrm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.664_53520b42c98526" in 4.179884619s (4.179888819s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:20 +0000 UTC - event for kube-proxy-gmhrm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container kube-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:20 +0000 UTC - event for kube-proxy-gmhrm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container kube-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:36 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:36 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-9p2g5 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:56:36 +0000 UTC - event for metrics-server-c9574f845-9p2g5: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:01 +0000 UTC - event for coredns-56f4c55bf9-kpxkv: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-kpxkv to capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:01 +0000 UTC - event for coredns-56f4c55bf9-zj22k: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-zj22k to capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:01 +0000 UTC - event for metrics-server-c9574f845-9p2g5: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-9p2g5 to capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:02 +0000 UTC - event for coredns-56f4c55bf9-kpxkv: {kubelet capz-conf-t8nagj-control-plane-c8pmj} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "711f65f1e7a08f919e9a31f9a1683e7614980ca0eb2d1899f2c19da49144f883": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:02 +0000 UTC - event for coredns-56f4c55bf9-zj22k: {kubelet capz-conf-t8nagj-control-plane-c8pmj} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "18b81fa1de558d076ca65a9d96a42ad46efd22d05d3821a9f62799e64359fb31": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:02 +0000 UTC - event for metrics-server-c9574f845-9p2g5: {kubelet capz-conf-t8nagj-control-plane-c8pmj} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d28e3731a9f7a1d80f613cd94c61117a477ffb3684e73bacff434020acc0c788": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:12 +0000 UTC - event for coredns-56f4c55bf9-zj22k: {kubelet capz-conf-t8nagj-control-plane-c8pmj} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "4560e68079611dada9f9498131a9022f6109b59f2d1f3221c7e176725691bbf8": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:16 +0000 UTC - event for coredns-56f4c55bf9-kpxkv: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container coredns Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:16 +0000 UTC - event for coredns-56f4c55bf9-kpxkv: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container coredns Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:16 +0000 UTC - event for coredns-56f4c55bf9-kpxkv: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:20 +0000 UTC - event for metrics-server-c9574f845-9p2g5: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:25 +0000 UTC - event for coredns-56f4c55bf9-zj22k: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container coredns Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:25 +0000 UTC - event for coredns-56f4c55bf9-zj22k: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container coredns Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:25 +0000 UTC - event for coredns-56f4c55bf9-zj22k: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:29 +0000 UTC - event for metrics-server-c9574f845-9p2g5: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.865142417s (8.534594196s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:30 +0000 UTC - event for metrics-server-c9574f845-9p2g5: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container metrics-server Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:30 +0000 UTC - event for metrics-server-c9574f845-9p2g5: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container metrics-server Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:53 +0000 UTC - event for csi-azuredisk-controller: {deployment-controller } ScalingReplicaSet: Scaled up replica set csi-azuredisk-controller-7875f5db98 to 1 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:53 +0000 UTC - event for csi-azuredisk-controller-7875f5db98: {replicaset-controller } SuccessfulCreate: Created pod: csi-azuredisk-controller-7875f5db98-vvk5h Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:53 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.2.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:53 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-controller-7875f5db98-vvk5h to capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:53 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-wd7zm Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:53 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:53 +0000 UTC - event for csi-azuredisk-node-wd7zm: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-wd7zm to capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:55 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container liveness-probe Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:55 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0" in 1.794430081s (1.794492481s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:55 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:55 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container liveness-probe Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:58 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.2.0" in 2.918160465s (4.580087565s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:58 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container csi-provisioner Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:58 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container csi-provisioner Jan 2 13:11:01.634: INFO: At 2023-01-02 12:57:58 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v3.5.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:00 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:00 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container node-driver-registrar Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:00 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container node-driver-registrar Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:00 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1" in 2.062466205s (4.797980326s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:04 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container csi-attacher Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:04 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v3.5.0" in 3.755609116s (5.624646222s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:04 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container csi-attacher Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:04 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:14 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" in 10.064657835s (13.653757182s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:16 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container azuredisk Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:16 +0000 UTC - event for csi-azuredisk-node-wd7zm: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container azuredisk Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:18 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container csi-snapshotter Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:18 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1" in 4.002965999s (13.911822488s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:18 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:18 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container csi-snapshotter Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container csi-resizer Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0" already present on machine Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0" in 2.822742526s (2.822751926s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" already present on machine Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container csi-resizer Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container azuredisk Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container azuredisk Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Started: Started container liveness-probe Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:21 +0000 UTC - event for csi-azuredisk-controller-7875f5db98-vvk5h: {kubelet capz-conf-t8nagj-control-plane-c8pmj} Created: Created container liveness-probe Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:22 +0000 UTC - event for disk-csi-azure-com: {disk.csi.azure.com/1672664302505-8081-disk.csi.azure.com } LeaderElection: 1672664302505-8081-disk-csi-azure-com became leader Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:22 +0000 UTC - event for external-attacher-leader-disk-csi-azure-com: {external-attacher-leader-disk.csi.azure.com/capz-conf-t8nagj-control-plane-c8pmj } LeaderElection: capz-conf-t8nagj-control-plane-c8pmj became leader Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:22 +0000 UTC - event for external-resizer-disk-csi-azure-com: {external-resizer-disk-csi-azure-com/capz-conf-t8nagj-control-plane-c8pmj } LeaderElection: capz-conf-t8nagj-control-plane-c8pmj became leader Jan 2 13:11:01.634: INFO: At 2023-01-02 12:58:22 +0000 UTC - event for external-snapshotter-leader-disk-csi-azure-com: {external-snapshotter-leader-disk.csi.azure.com/capz-conf-t8nagj-control-plane-c8pmj } LeaderElection: capz-conf-t8nagj-control-plane-c8pmj became leader Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:37 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-m7wcc Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:37 +0000 UTC - event for containerd-logger-m7wcc: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-m7wcc to capz-conf-n4ckt Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:37 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-8j269 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:37 +0000 UTC - event for kube-proxy-windows-8j269: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-8j269 to capz-conf-n4ckt Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:39 +0000 UTC - event for kube-proxy-windows-8j269: {kubelet capz-conf-n4ckt} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:45 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-8fwq6 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:45 +0000 UTC - event for containerd-logger-8fwq6: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-8fwq6 to capz-conf-45mw2 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:45 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-5zngc Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:45 +0000 UTC - event for kube-proxy-windows-5zngc: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-5zngc to capz-conf-45mw2 Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:47 +0000 UTC - event for containerd-logger-8fwq6: {kubelet capz-conf-45mw2} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition Jan 2 13:11:01.634: INFO: At 2023-01-02 12:59:47 +0000 UTC - event for kube-proxy-windows-5zngc: {kubelet capz-conf-45mw2} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:01 +0000 UTC - event for containerd-logger-m7wcc: {kubelet capz-conf-n4ckt} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:01 +0000 UTC - event for kube-proxy-windows-8j269: {kubelet capz-conf-n4ckt} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.662_00aae4c10c204d-calico-hostprocess" already present on machine Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:02 +0000 UTC - event for kube-proxy-windows-8j269: {kubelet capz-conf-n4ckt} Started: Started container kube-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:02 +0000 UTC - event for kube-proxy-windows-8j269: {kubelet capz-conf-n4ckt} Created: Created container kube-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:09 +0000 UTC - event for containerd-logger-8fwq6: {kubelet capz-conf-45mw2} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:09 +0000 UTC - event for kube-proxy-windows-5zngc: {kubelet capz-conf-45mw2} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.662_00aae4c10c204d-calico-hostprocess" already present on machine Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:09 +0000 UTC - event for kube-proxy-windows-5zngc: {kubelet capz-conf-45mw2} Created: Created container kube-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:09 +0000 UTC - event for kube-proxy-windows-5zngc: {kubelet capz-conf-45mw2} Started: Started container kube-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:11 +0000 UTC - event for csi-azuredisk-node-win: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-win-lkpgx Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:11 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-win-lkpgx to capz-conf-n4ckt Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:11 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-72gln Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:11 +0000 UTC - event for csi-proxy-72gln: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-72gln to capz-conf-n4ckt Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:12 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:12 +0000 UTC - event for csi-proxy-72gln: {kubelet capz-conf-n4ckt} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:15 +0000 UTC - event for containerd-logger-8fwq6: {kubelet capz-conf-45mw2} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 6.7119103s (6.7120033s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:15 +0000 UTC - event for containerd-logger-m7wcc: {kubelet capz-conf-n4ckt} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 6.9294686s (13.8614836s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:24 +0000 UTC - event for containerd-logger-m7wcc: {kubelet capz-conf-n4ckt} Started: Started container containerd-logger Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:24 +0000 UTC - event for containerd-logger-m7wcc: {kubelet capz-conf-n4ckt} Created: Created container containerd-logger Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:26 +0000 UTC - event for containerd-logger-8fwq6: {kubelet capz-conf-45mw2} Created: Created container containerd-logger Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:26 +0000 UTC - event for containerd-logger-8fwq6: {kubelet capz-conf-45mw2} Started: Started container containerd-logger Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:26 +0000 UTC - event for csi-azuredisk-node-win: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-win-c2jh9 Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:26 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-win-c2jh9 to capz-conf-45mw2 Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:26 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-mgklp Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:26 +0000 UTC - event for csi-proxy-mgklp: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-mgklp to capz-conf-45mw2 Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:27 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:27 +0000 UTC - event for csi-proxy-mgklp: {kubelet capz-conf-45mw2} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:35 +0000 UTC - event for csi-proxy-72gln: {kubelet capz-conf-n4ckt} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 19.3984475s (22.941818s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:35 +0000 UTC - event for csi-proxy-72gln: {kubelet capz-conf-n4ckt} Started: Started container csi-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:35 +0000 UTC - event for csi-proxy-72gln: {kubelet capz-conf-n4ckt} Created: Created container csi-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:44 +0000 UTC - event for csi-proxy-mgklp: {kubelet capz-conf-45mw2} Created: Created container csi-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:44 +0000 UTC - event for csi-proxy-mgklp: {kubelet capz-conf-45mw2} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 17.6404141s (17.6404141s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:45 +0000 UTC - event for csi-proxy-mgklp: {kubelet capz-conf-45mw2} Started: Started container csi-proxy Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:51 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" in 15.9821713s (38.8973993s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:51 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Created: Created container init Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:51 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Started: Started container init Jan 2 13:11:01.634: INFO: At 2023-01-02 13:00:56 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:00 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" in 16.2784389s (33.8685226s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:01 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Started: Started container init Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:01 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Created: Created container init Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:06 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:16 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0" in 20.0974921s (20.0974921s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:17 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:17 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Started: Started container liveness-probe Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:17 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Created: Created container liveness-probe Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:26 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0" in 20.5733876s (20.5733876s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:26 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Created: Created container liveness-probe Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:27 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1" Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:27 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Started: Started container liveness-probe Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:34 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1" in 16.9995963s (16.9995963s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:34 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Created: Created container node-driver-registrar Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:34 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Started: Started container node-driver-registrar Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:34 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" already present on machine Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:35 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Created: Created container azuredisk Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:35 +0000 UTC - event for csi-azuredisk-node-win-lkpgx: {kubelet capz-conf-n4ckt} Started: Started container azuredisk Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:44 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Started: Started container node-driver-registrar Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:44 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Created: Created container node-driver-registrar Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:44 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1" in 16.8867551s (16.8867551s including waiting) Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:44 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0" already present on machine Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:44 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Created: Created container azuredisk Jan 2 13:11:01.634: INFO: At 2023-01-02 13:01:44 +0000 UTC - event for csi-azuredisk-node-win-c2jh9: {kubelet capz-conf-45mw2} Started: Started container azuredisk Jan 2 13:11:01.790: INFO: POD NODE PHASE GRACE CONDITIONS Jan 2 13:11:01.790: INFO: containerd-logger-8fwq6 capz-conf-45mw2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:59:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:27 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:27 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:59:45 +0000 UTC }] Jan 2 13:11:01.790: INFO: containerd-logger-m7wcc capz-conf-n4ckt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:59:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:59:37 +0000 UTC }] Jan 2 13:11:01.790: INFO: coredns-56f4c55bf9-kpxkv capz-conf-t8nagj-control-plane-c8pmj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:01 +0000 UTC }] Jan 2 13:11:01.790: INFO: coredns-56f4c55bf9-zj22k capz-conf-t8nagj-control-plane-c8pmj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:25 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:25 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:01 +0000 UTC }] Jan 2 13:11:01.790: INFO: csi-azuredisk-controller-7875f5db98-vvk5h capz-conf-t8nagj-control-plane-c8pmj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:58:22 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:58:22 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:53 +0000 UTC }] Jan 2 13:11:01.790: INFO: csi-azuredisk-node-wd7zm capz-conf-t8nagj-control-plane-c8pmj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:58:16 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:58:16 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:53 +0000 UTC }] Jan 2 13:11:01.790: INFO: csi-azuredisk-node-win-c2jh9 capz-conf-45mw2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:06 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:11:01.790: INFO: csi-azuredisk-node-win-lkpgx capz-conf-n4ckt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:56 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:36 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:01:36 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:11:01.790: INFO: csi-proxy-72gln capz-conf-n4ckt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:36 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:36 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:11 +0000 UTC }] Jan 2 13:11:01.790: INFO: csi-proxy-mgklp capz-conf-45mw2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:46 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:46 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:26 +0000 UTC }] Jan 2 13:11:01.790: INFO: etcd-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:56:12 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:56:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:56:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:56:12 +0000 UTC }] Jan 2 13:11:01.790: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.790: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.790: INFO: kube-proxy-gmhrm capz-conf-t8nagj-control-plane-c8pmj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:56:14 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:56:20 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:56:20 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:56:14 +0000 UTC }] Jan 2 13:11:01.790: INFO: kube-proxy-windows-5zngc capz-conf-45mw2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:59:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:09 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:09 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:59:45 +0000 UTC }] Jan 2 13:11:01.790: INFO: kube-proxy-windows-8j269 capz-conf-n4ckt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:59:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:03 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 13:00:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:59:37 +0000 UTC }] Jan 2 13:11:01.790: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] Jan 2 13:11:01.790: INFO: metrics-server-c9574f845-9p2g5 capz-conf-t8nagj-control-plane-c8pmj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:52 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-02 12:57:01 +0000 UTC }] Jan 2 13:11:01.790: INFO: Jan 2 13:11:03.190: INFO: Logging node info for node capz-conf-45mw2 Jan 2 13:11:03.302: INFO: Node Info: &Node{ObjectMeta:{capz-conf-45mw2 e4f2e576-a5c8-45cd-9886-fc2477c4e549 2886 0 2023-01-02 12:59:45 +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:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-45mw2 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-t8nagj cluster.x-k8s.io/cluster-namespace:capz-conf-t8nagj cluster.x-k8s.io/machine:capz-conf-t8nagj-md-win-698d669585-lgq7m cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-t8nagj-md-win-698d669585 csi.volume.kubernetes.io/nodeid:{"disk.csi.azure.com":"capz-conf-45mw2"} 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.181.129 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:67:a4:1d volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-02 12:59:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2023-01-02 12:59:45 +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 2023-01-02 13:00:26 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2023-01-02 13:00:51 +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":{}}}} } {calico-node.exe Update v1 2023-01-02 13:01:34 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2023-01-02 13:06:53 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-t8nagj/providers/Microsoft.Compute/virtualMachines/capz-conf-45mw2,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:2023-01-02 13:06:53 +0000 UTC,LastTransitionTime:2023-01-02 12:59:45 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-02 13:06:53 +0000 UTC,LastTransitionTime:2023-01-02 12:59:45 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-02 13:06:53 +0000 UTC,LastTransitionTime:2023-01-02 12:59:45 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-02 13:06:53 +0000 UTC,LastTransitionTime:2023-01-02 13:00:26 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-45mw2,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-45mw2,SystemUUID:2CBA9C7E-D688-488F-8D6C-2857AD53CD3B,BootID:9,KernelVersion:10.0.17763.3770,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.664+53520b42c98526-dirty,KubeProxyVersion:v1.27.0-alpha.0.664+53520b42c98526-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:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:244bd748a79e016847e4f62080213b1afef7b2dc37bc8ff2c45fbca2cf8a951d mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0],SizeBytes:128638954,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.27.0-alpha.0.662_00aae4c10c204d-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:2fbd1e1a0538a06f2061afd45975df70c942654aa7f86e920720169ee439c2d6 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1],SizeBytes:112027297,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:31547791294872570393470991481c2477a311031d3a03e0ae54eb164347dc34 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0],SizeBytes:111112278,},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:2082c9b6488b3a2839141f472740c36484d5cbc91f7c24d67bc77ea311d4602b docker.io/sigwindowstools/calico-install:v3.24.5-hostprocess],SizeBytes:49820336,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:ba0ac4633a832430a00374ef6cf1c701797017b8d09ccc3fb12db253e250887a docker.io/sigwindowstools/calico-node:v3.24.5-hostprocess],SizeBytes:28623190,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 2 13:11:03.303: INFO: Logging kubelet events for node capz-conf-45mw2 Jan 2 13:11:03.407: INFO: Logging pods the kubelet thinks is on node capz-conf-45mw2 Jan 2 13:11:03.577: INFO: containerd-logger-8fwq6 started at 2023-01-02 12:59:46 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:03.577: INFO: Container containerd-logger ready: true, restart count 0 Jan 2 13:11:03.577: INFO: kube-proxy-windows-5zngc started at 2023-01-02 12:59:46 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:03.577: INFO: Container kube-proxy ready: true, restart count 0 Jan 2 13:11:03.577: INFO: calico-node-windows-7kkkn started at 2023-01-02 12:59:46 +0000 UTC (1+2 container statuses recorded) Jan 2 13:11:03.577: INFO: Init container install-cni ready: true, restart count 0 Jan 2 13:11:03.577: INFO: Container calico-node-felix ready: true, restart count 1 Jan 2 13:11:03.577: INFO: Container calico-node-startup ready: true, restart count 0 Jan 2 13:11:03.577: INFO: csi-proxy-mgklp started at 2023-01-02 13:00:26 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:03.577: INFO: Container csi-proxy ready: true, restart count 0 Jan 2 13:11:03.577: INFO: csi-azuredisk-node-win-c2jh9 started at 2023-01-02 13:00:26 +0000 UTC (1+3 container statuses recorded) Jan 2 13:11:03.577: INFO: Init container init ready: true, restart count 0 Jan 2 13:11:03.577: INFO: Container azuredisk ready: true, restart count 0 Jan 2 13:11:03.577: INFO: Container liveness-probe ready: true, restart count 0 Jan 2 13:11:03.577: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 2 13:11:04.031: INFO: Latency metrics for node capz-conf-45mw2 Jan 2 13:11:04.031: INFO: Logging node info for node capz-conf-n4ckt Jan 2 13:11:04.141: INFO: Node Info: &Node{ObjectMeta:{capz-conf-n4ckt c9b60186-aeae-4936-b1ff-f5a2d1f8a606 2869 0 2023-01-02 12:59:37 +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:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-n4ckt kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-t8nagj cluster.x-k8s.io/cluster-namespace:capz-conf-t8nagj cluster.x-k8s.io/machine:capz-conf-t8nagj-md-win-698d669585-n899t cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-t8nagj-md-win-698d669585 csi.volume.kubernetes.io/nodeid:{"disk.csi.azure.com":"capz-conf-n4ckt"} 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.63.1 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:90:f5:3f volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2023-01-02 12:59:37 +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 2023-01-02 12:59:38 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2023-01-02 13:00:11 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2023-01-02 13:00:55 +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":{}}}} } {calico-node.exe Update v1 2023-01-02 13:01:24 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2023-01-02 13:06:47 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-t8nagj/providers/Microsoft.Compute/virtualMachines/capz-conf-n4ckt,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:2023-01-02 13:06:47 +0000 UTC,LastTransitionTime:2023-01-02 12:59:37 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-02 13:06:47 +0000 UTC,LastTransitionTime:2023-01-02 12:59:37 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-02 13:06:47 +0000 UTC,LastTransitionTime:2023-01-02 12:59:37 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-02 13:06:47 +0000 UTC,LastTransitionTime:2023-01-02 13:00:11 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-n4ckt,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-n4ckt,SystemUUID:66124B18-440B-4BB6-BAE0-8985E9D952D5,BootID:9,KernelVersion:10.0.17763.3770,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.664+53520b42c98526-dirty,KubeProxyVersion:v1.27.0-alpha.0.664+53520b42c98526-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:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:244bd748a79e016847e4f62080213b1afef7b2dc37bc8ff2c45fbca2cf8a951d mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0],SizeBytes:128638954,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.27.0-alpha.0.662_00aae4c10c204d-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:2fbd1e1a0538a06f2061afd45975df70c942654aa7f86e920720169ee439c2d6 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1],SizeBytes:112027297,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:31547791294872570393470991481c2477a311031d3a03e0ae54eb164347dc34 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0],SizeBytes:111112278,},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:2082c9b6488b3a2839141f472740c36484d5cbc91f7c24d67bc77ea311d4602b docker.io/sigwindowstools/calico-install:v3.24.5-hostprocess],SizeBytes:49820336,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:ba0ac4633a832430a00374ef6cf1c701797017b8d09ccc3fb12db253e250887a docker.io/sigwindowstools/calico-node:v3.24.5-hostprocess],SizeBytes:28623190,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 2 13:11:04.142: INFO: Logging kubelet events for node capz-conf-n4ckt Jan 2 13:11:04.246: INFO: Logging pods the kubelet thinks is on node capz-conf-n4ckt Jan 2 13:11:04.405: INFO: csi-proxy-72gln started at 2023-01-02 13:00:11 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:04.406: INFO: Container csi-proxy ready: true, restart count 0 Jan 2 13:11:04.406: INFO: csi-azuredisk-node-win-lkpgx started at 2023-01-02 13:00:11 +0000 UTC (1+3 container statuses recorded) Jan 2 13:11:04.406: INFO: Init container init ready: true, restart count 0 Jan 2 13:11:04.406: INFO: Container azuredisk ready: true, restart count 0 Jan 2 13:11:04.406: INFO: Container liveness-probe ready: true, restart count 0 Jan 2 13:11:04.406: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 2 13:11:04.406: INFO: containerd-logger-m7wcc started at 2023-01-02 12:59:38 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:04.406: INFO: Container containerd-logger ready: true, restart count 0 Jan 2 13:11:04.406: INFO: kube-proxy-windows-8j269 started at 2023-01-02 12:59:38 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:04.406: INFO: Container kube-proxy ready: true, restart count 0 Jan 2 13:11:04.406: INFO: calico-node-windows-5lpn6 started at 2023-01-02 12:59:38 +0000 UTC (1+2 container statuses recorded) Jan 2 13:11:04.406: INFO: Init container install-cni ready: true, restart count 0 Jan 2 13:11:04.406: INFO: Container calico-node-felix ready: true, restart count 1 Jan 2 13:11:04.406: INFO: Container calico-node-startup ready: true, restart count 0 Jan 2 13:11:04.857: INFO: Latency metrics for node capz-conf-n4ckt Jan 2 13:11:04.857: INFO: Logging node info for node capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:04.975: INFO: Node Info: &Node{ObjectMeta:{capz-conf-t8nagj-control-plane-c8pmj 18430091-2ccd-43f0-bd6c-32db1e4e7113 3258 0 2023-01-02 12:56:10 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:northeurope failure-domain.beta.kubernetes.io/zone:northeurope-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-t8nagj-control-plane-c8pmj kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone:northeurope-3 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:northeurope-3] map[cluster.x-k8s.io/cluster-name:capz-conf-t8nagj cluster.x-k8s.io/cluster-namespace:capz-conf-t8nagj cluster.x-k8s.io/machine:capz-conf-t8nagj-control-plane-x2rz4 cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-t8nagj-control-plane csi.volume.kubernetes.io/nodeid:{"disk.csi.azure.com":"capz-conf-t8nagj-control-plane-c8pmj"} 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.39.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-02 12:56:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/control-plane":{},"f:node.kubernetes.io/exclude-from-external-load-balancers":{}}}} } {kubelet Update v1 2023-01-02 12:56:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {manager Update v1 2023-01-02 12:56:33 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2023-01-02 12:57:01 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {calico-node Update v1 2023-01-02 12:57:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-02 13:08:58 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-t8nagj/providers/Microsoft.Compute/virtualMachines/capz-conf-t8nagj-control-plane-c8pmj,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: {{4123176960 0} {<nil>} 4026540Ki 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: {{4018319360 0} {<nil>} 3924140Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-02 12:57:13 +0000 UTC,LastTransitionTime:2023-01-02 12:57:13 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-02 13:08:58 +0000 UTC,LastTransitionTime:2023-01-02 12:55:42 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-02 13:08:58 +0000 UTC,LastTransitionTime:2023-01-02 12:55:42 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-02 13:08:58 +0000 UTC,LastTransitionTime:2023-01-02 12:55:42 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-02 13:08:58 +0000 UTC,LastTransitionTime:2023-01-02 12:57:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-t8nagj-control-plane-c8pmj,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:543c82d8d5e348c587890d50af589c72,SystemUUID:d8d490eb-e8e5-ad48-bee6-dbce6615c32d,BootID:a666ae76-3874-48cc-b32f-4dc181bc3a30,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.664+53520b42c98526,KubeProxyVersion:v1.27.0-alpha.0.664+53520b42c98526,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:244bd748a79e016847e4f62080213b1afef7b2dc37bc8ff2c45fbca2cf8a951d mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.25.0],SizeBytes:94715883,},ContainerImage{Names:[docker.io/calico/cni@sha256:e282ea2914c806b5de2976330a17cfb5e6dcef47147bceb1432ca5c75fd46f50 docker.io/calico/cni:v3.24.5],SizeBytes:87458443,},ContainerImage{Names:[docker.io/calico/node@sha256:5972ad2bcbdc668564d3e26960c9c513b2d7b05581c704747cf7c62ef3a405a6 docker.io/calico/node:v3.24.5],SizeBytes:81584866,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner@sha256:2f9a214fe823b4b5099e7cff4f4d16e7e4298cd086478880845de8858d49a3b3 mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.2.0],SizeBytes:60382210,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-resizer@sha256:544e74bd67c649fd49500e195ff4a4ee675cfd26768574262dc6fa0250373d59 mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0],SizeBytes:57519578,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-attacher@sha256:7e5af2ed16e053822e58f6576423c0bb77e59050c3698986f319d257b4551023 mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v3.5.0],SizeBytes:56936934,},ContainerImage{Names:[docker.io/calico/apiserver@sha256:aabc97c06afa572e5bdcec7c69b8a2e73e24fd3e73b848ffeaafb68fc63f6ac9 docker.io/calico/apiserver:v3.24.5],SizeBytes:35537748,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:d2e78cad0bc1cdefa22a41c58a27e854563a4a01edd3438ffc3d9e4fe322f664 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.662_00aae4c10c204d],SizeBytes:35369926,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:7995f1a41fd2de48acd190369d5d487479f52dd7183a23130a52b22e20b7bccf gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.662_00aae4c10c204d],SizeBytes:32288472,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:2b6acd7f677f76ffe12ecf3ea7df92eb9b1bdb07336d1ac2a54c7631fb753f7e docker.io/calico/kube-controllers:v3.24.5],SizeBytes:31137169,},ContainerImage{Names:[docker.io/calico/typha@sha256:78780437eefce76d541b46d174373fd2160b84fb2f56d421df5a2e49f5207c80 docker.io/calico/typha:v3.24.5],SizeBytes:28370695,},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:[mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter@sha256:a889e925e15f9423f7842f1b769f64cbcf6a20b6956122836fc835cf22d9073f mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1],SizeBytes:22192414,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:a83a1fd6c8d4f71e03b4848928abc1eb7e288d8ccad21865779c77954c15625a gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.662_00aae4c10c204d],SizeBytes:21546874,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:6477f8ac3f19f98d12a767818b29ffc31c79b408bb25a0dd3f8227f7c04230c0 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.664_53520b42c98526],SizeBytes:21544949,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[quay.io/tigera/operator@sha256:c01fc12b477e96facf29b770722fa37d292b9daec23ce14817fe77f7fc542307 quay.io/tigera/operator:v1.28.5],SizeBytes:21105694,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:2929e1821bd45573b1ade54852a48bc56f1d800379f14485265c9717e40130e2 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.662_00aae4c10c204d],SizeBytes:17498641,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:2fbd1e1a0538a06f2061afd45975df70c942654aa7f86e920720169ee439c2d6 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.1],SizeBytes:9578961,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:31547791294872570393470991481c2477a311031d3a03e0ae54eb164347dc34 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.7.0],SizeBytes:8689744,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:392e392d0e11388bf55571155f915b1e8d080cb6824a7a09381537ad2f9b3c83 docker.io/calico/pod2daemon-flexvol:v3.24.5],SizeBytes:7067316,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 2 13:11:04.976: INFO: Logging kubelet events for node capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:05.080: INFO: Logging pods the kubelet thinks is on node capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:05.402: INFO: calico-node-65vws started at 2023-01-02 12:56:33 +0000 UTC (2+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Init container flexvol-driver ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Init container install-cni ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Container calico-node ready: true, restart count 0 Jan 2 13:11:05.402: INFO: metrics-server-c9574f845-9p2g5 started at 2023-01-02 12:57:01 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container metrics-server ready: true, restart count 0 Jan 2 13:11:05.402: INFO: calico-apiserver-6b776f8757-48d8d started at 2023-01-02 12:57:30 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container calico-apiserver ready: true, restart count 0 Jan 2 13:11:05.402: INFO: kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj started at <nil> (0+0 container statuses recorded) Jan 2 13:11:05.402: INFO: etcd-capz-conf-t8nagj-control-plane-c8pmj started at 2023-01-02 12:56:12 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container etcd ready: true, restart count 0 Jan 2 13:11:05.402: INFO: kube-proxy-gmhrm started at 2023-01-02 12:56:14 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container kube-proxy ready: true, restart count 0 Jan 2 13:11:05.402: INFO: kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj started at <nil> (0+0 container statuses recorded) Jan 2 13:11:05.402: INFO: calico-apiserver-6b776f8757-b9vqm started at 2023-01-02 12:57:30 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container calico-apiserver ready: true, restart count 0 Jan 2 13:11:05.402: INFO: csi-azuredisk-node-wd7zm started at 2023-01-02 12:57:53 +0000 UTC (0+3 container statuses recorded) Jan 2 13:11:05.402: INFO: Container azuredisk ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Container liveness-probe ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 2 13:11:05.402: INFO: calico-kube-controllers-67df98bdc8-nwf5h started at 2023-01-02 12:57:01 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container calico-kube-controllers ready: true, restart count 0 Jan 2 13:11:05.402: INFO: kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj started at <nil> (0+0 container statuses recorded) Jan 2 13:11:05.402: INFO: tigera-operator-7795f5d79b-6vzmj started at 2023-01-02 12:56:26 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container tigera-operator ready: true, restart count 0 Jan 2 13:11:05.402: INFO: calico-typha-6c74b4b57c-bjmlz started at 2023-01-02 12:56:33 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container calico-typha ready: true, restart count 0 Jan 2 13:11:05.402: INFO: coredns-56f4c55bf9-zj22k started at 2023-01-02 12:57:01 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container coredns ready: true, restart count 0 Jan 2 13:11:05.402: INFO: coredns-56f4c55bf9-kpxkv started at 2023-01-02 12:57:01 +0000 UTC (0+1 container statuses recorded) Jan 2 13:11:05.402: INFO: Container coredns ready: true, restart count 0 Jan 2 13:11:05.402: INFO: csi-azuredisk-controller-7875f5db98-vvk5h started at 2023-01-02 12:57:53 +0000 UTC (0+6 container statuses recorded) Jan 2 13:11:05.402: INFO: Container azuredisk ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Container csi-attacher ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Container csi-provisioner ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Container csi-resizer ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Container csi-snapshotter ready: true, restart count 0 Jan 2 13:11:05.402: INFO: Container liveness-probe ready: true, restart count 0 Jan 2 13:11:05.900: INFO: Latency metrics for node capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:06.061: INFO: Running kubectl logs on non-ready containers in kube-system Jan 2 13:11:06.443: INFO: Failed to get logs of pod kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj) Jan 2 13:11:06.443: INFO: Logs of kube-system/kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj:kube-apiserver on node capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:06.443: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-t8nagj-control-plane-c8pmj:kube-apiserver Jan 2 13:11:06.843: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj) Jan 2 13:11:06.843: INFO: Logs of kube-system/kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj:kube-controller-manager on node capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:06.843: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj:kube-controller-manager Jan 2 13:11:07.244: INFO: Failed to get logs of pod kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj) Jan 2 13:11:07.244: INFO: Logs of kube-system/kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj:kube-scheduler on node capz-conf-t8nagj-control-plane-c8pmj Jan 2 13:11:07.244: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj:kube-scheduler [FAILED] 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-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] kube-controller-manager-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] kube-scheduler-capz-conf-t8nagj-control-plane-c8pmj capz-conf-t8nagj-control-plane-c8pmj Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:249 @ 01/02/23 13:11:07.244 < Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/02/23 13:11:07.244 (10m7.511s)
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/02/23 13:11:07.289from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/02/23 13:11:07.289
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/02/23 13:11:07.288from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/02/23 13:11:07.288
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/02/23 13:11:07.289from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/02/23 13:11:07.289
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 [It] Conformance Tests conformance-tests
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [It] 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 [It] 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 [It] 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 [It] Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e [It] Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e [It] Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e [It] 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 [It] Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e [It] 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 [It] 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 [It] Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e [It] 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 [It] 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 [It] Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e [It] Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e [It] Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e [It] Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e [It] 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 [It] [K8s-Upgrade] Running the CSI migration tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with out-of-tree cloud provider
capz-e2e [It] [K8s-Upgrade] Running the CSI migration 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 [It] [K8s-Upgrade] Running the CSI migration 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