pull-kubernetes-e2e-capz-windows-containerd #1593477341437235200 Results

Test Failures

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'

test/e2e/e2e.go:249
k8s.io/kubernetes/test/e2e.setupSuite()
	test/e2e/e2e.go:249 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
	test/e2e/e2e.go:81 +0x8f
reflect.Value.call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0x75b6e72, 0x4}, {0xc0000b9f20, 0x0, 0x0?})
	/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0xc0000b9f20?, 0x0?, 0x0?})
	/usr/local/go/src/reflect/value.go:368 +0xbc
				[SynchronizedBeforeSuite] TOP-LEVEL
  test/e2e/e2e.go:77
Nov 18 06:18:12.738: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 18 06:18:12.741: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 18 06:18:13.239: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 18 06:18:13.656: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:13.656: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:13.656: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:13.656: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 18 06:18:13.656: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:13.656: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:13.656: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:13.656: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:13.656: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:13.656: INFO: 
Nov 18 06:18:16.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:16.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:16.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:16.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 18 06:18:16.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:16.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:16.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:16.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:16.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:16.066: INFO: 
Nov 18 06:18:18.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:18.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:18.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:18.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 18 06:18:18.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:18.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:18.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:18.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:18.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:18.062: INFO: 
Nov 18 06:18:20.059: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:20.059: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:20.059: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:20.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 18 06:18:20.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:20.059: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:20.059: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:20.059: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:20.059: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:20.059: INFO: 
Nov 18 06:18:22.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:22.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:22.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:22.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 18 06:18:22.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:22.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:22.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:22.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:22.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:22.065: INFO: 
Nov 18 06:18:24.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:24.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:24.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:24.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 18 06:18:24.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:24.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:24.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:24.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:24.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:24.063: INFO: 
Nov 18 06:18:26.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:26.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:26.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:26.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 18 06:18:26.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:26.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:26.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:26.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:26.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:26.060: INFO: 
Nov 18 06:18:28.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:28.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:28.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:28.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 18 06:18:28.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:28.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:28.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:28.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:28.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:28.060: INFO: 
Nov 18 06:18:30.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:30.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:30.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:30.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 18 06:18:30.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:30.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:30.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:30.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:30.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:30.066: INFO: 
Nov 18 06:18:32.073: INFO: The status of Pod calico-node-windows-p5j6m is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:32.073: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:32.073: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:32.073: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:32.073: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 18 06:18:32.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:32.073: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:32.073: INFO: calico-node-windows-p5j6m                                     capz-conf-qtb4d                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:41 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:31 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:31 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:12 +0000 UTC  }]
Nov 18 06:18:32.073: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:32.073: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:32.073: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:32.073: INFO: 
Nov 18 06:18:34.069: INFO: The status of Pod calico-node-windows-p5j6m is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:34.069: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:34.069: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:34.069: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:34.069: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 18 06:18:34.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:34.069: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:34.069: INFO: calico-node-windows-p5j6m                                     capz-conf-qtb4d                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:41 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:31 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:31 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:12 +0000 UTC  }]
Nov 18 06:18:34.069: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:34.069: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:34.069: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:34.069: INFO: 
Nov 18 06:18:36.064: INFO: The status of Pod calico-node-windows-p5j6m is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:36.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:36.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:36.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:36.065: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 18 06:18:36.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:36.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:36.065: INFO: calico-node-windows-p5j6m                                     capz-conf-qtb4d                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:41 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:31 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:31 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:12 +0000 UTC  }]
Nov 18 06:18:36.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:36.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:36.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:36.065: INFO: 
Nov 18 06:18:38.064: INFO: The status of Pod calico-node-windows-p5j6m is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:38.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:38.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:38.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:38.065: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 18 06:18:38.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:38.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:38.065: INFO: calico-node-windows-p5j6m                                     capz-conf-qtb4d                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:41 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:31 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:31 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:12 +0000 UTC  }]
Nov 18 06:18:38.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:38.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:38.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:38.065: INFO: 
Nov 18 06:18:40.070: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:40.070: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:40.070: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:40.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 18 06:18:40.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:40.071: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:40.071: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:40.071: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:40.071: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:40.071: INFO: 
Nov 18 06:18:42.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:42.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:42.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:42.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 18 06:18:42.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:42.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:42.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:42.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:42.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:42.067: INFO: 
Nov 18 06:18:44.254: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:44.254: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:44.254: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:44.254: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (31 seconds elapsed)
Nov 18 06:18:44.254: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:44.254: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:44.254: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:44.254: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:44.254: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:44.254: INFO: 
Nov 18 06:18:46.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:46.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:46.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:46.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 18 06:18:46.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:46.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:46.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:46.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:46.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:46.067: INFO: 
Nov 18 06:18:48.071: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:48.071: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:48.071: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:48.071: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 18 06:18:48.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:48.071: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:48.071: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:48.071: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:48.071: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:48.071: INFO: 
Nov 18 06:18:50.069: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:50.069: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:50.069: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:50.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 18 06:18:50.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:50.069: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:50.069: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:50.069: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:50.069: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:50.069: INFO: 
Nov 18 06:18:52.076: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:52.076: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:52.076: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:52.076: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 18 06:18:52.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:52.076: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:52.076: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:52.076: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:52.076: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:52.076: INFO: 
Nov 18 06:18:54.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:54.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:54.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:54.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 18 06:18:54.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:54.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:54.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:54.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:54.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:54.067: INFO: 
Nov 18 06:18:56.070: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:56.070: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:56.070: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:56.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 18 06:18:56.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:56.070: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:56.070: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:56.070: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:56.070: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:56.070: INFO: 
Nov 18 06:18:58.074: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:58.074: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:58.074: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:18:58.074: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 18 06:18:58.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:18:58.074: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:18:58.074: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:58.074: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:58.074: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:18:58.074: INFO: 
Nov 18 06:19:00.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:00.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:00.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:00.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 18 06:19:00.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:00.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:00.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:00.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:00.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:00.067: INFO: 
Nov 18 06:19:02.069: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:02.069: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:02.069: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:02.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 18 06:19:02.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:02.069: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:02.069: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:02.069: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:02.069: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:02.069: INFO: 
Nov 18 06:19:04.073: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:04.073: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:04.073: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:04.073: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 18 06:19:04.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:04.073: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:04.073: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:04.073: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:04.073: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:04.073: INFO: 
Nov 18 06:19:06.069: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:06.069: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:06.069: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:06.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 18 06:19:06.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:06.069: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:06.069: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:06.069: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:06.069: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:06.069: INFO: 
Nov 18 06:19:08.070: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:08.070: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:08.070: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:08.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 18 06:19:08.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:08.070: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:08.070: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:08.070: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:08.070: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:08.070: INFO: 
Nov 18 06:19:10.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:10.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:10.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:10.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 18 06:19:10.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:10.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:10.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:10.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:10.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:10.067: INFO: 
Nov 18 06:19:12.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:12.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:12.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:12.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 18 06:19:12.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:12.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:12.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:12.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:12.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:12.066: INFO: 
Nov 18 06:19:14.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:14.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:14.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:14.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 18 06:19:14.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:14.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:14.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:14.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:14.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:14.065: INFO: 
Nov 18 06:19:16.068: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:16.068: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:16.068: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:16.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 18 06:19:16.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:16.068: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:16.068: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:16.068: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:16.068: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:16.068: INFO: 
Nov 18 06:19:18.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:18.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:18.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:18.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 18 06:19:18.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:18.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:18.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:18.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:18.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:18.064: INFO: 
Nov 18 06:19:20.071: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:20.071: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:20.071: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:20.071: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 18 06:19:20.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:20.071: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:20.071: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:20.071: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:20.071: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:20.071: INFO: 
Nov 18 06:19:22.068: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:22.068: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:22.068: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:22.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 18 06:19:22.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:22.068: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:22.068: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:22.068: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:22.068: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:22.068: INFO: 
Nov 18 06:19:24.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:24.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:24.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:24.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 18 06:19:24.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:24.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:24.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:24.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:24.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:24.066: INFO: 
Nov 18 06:19:26.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:26.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:26.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:26.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 18 06:19:26.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:26.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:26.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:26.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:26.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:26.066: INFO: 
Nov 18 06:19:28.071: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:28.071: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:28.071: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:28.071: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 18 06:19:28.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:28.071: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:28.071: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:28.071: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:28.071: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:28.071: INFO: 
Nov 18 06:19:30.071: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:30.071: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:30.071: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:30.071: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 18 06:19:30.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:30.071: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:30.071: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:30.071: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:30.071: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:30.071: INFO: 
Nov 18 06:19:32.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:32.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:32.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:32.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 18 06:19:32.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:32.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:32.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:32.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:32.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:32.065: INFO: 
Nov 18 06:19:34.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:34.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:34.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:34.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 18 06:19:34.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:34.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:34.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:34.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:34.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:34.064: INFO: 
Nov 18 06:19:36.069: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:36.069: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:36.069: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:36.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 18 06:19:36.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:36.069: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:36.069: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:36.069: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:36.069: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:36.069: INFO: 
Nov 18 06:19:38.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:38.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:38.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:38.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 18 06:19:38.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:38.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:38.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:38.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:38.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:38.065: INFO: 
Nov 18 06:19:40.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:40.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:40.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:40.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 18 06:19:40.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:40.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:40.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:40.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:40.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:40.067: INFO: 
Nov 18 06:19:42.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:42.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:42.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:42.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 18 06:19:42.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:42.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:42.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:42.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:42.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:42.065: INFO: 
Nov 18 06:19:44.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:44.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:44.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:44.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 18 06:19:44.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:44.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:44.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:44.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:44.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:44.066: INFO: 
Nov 18 06:19:46.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:46.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:46.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:46.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 18 06:19:46.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:46.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:46.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:46.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:46.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:46.067: INFO: 
Nov 18 06:19:48.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:48.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:48.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:48.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 18 06:19:48.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:48.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:48.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:48.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:48.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:48.065: INFO: 
Nov 18 06:19:50.068: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:50.068: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:50.068: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:50.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 18 06:19:50.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:50.068: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:50.068: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:50.068: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:50.068: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:50.068: INFO: 
Nov 18 06:19:52.070: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:52.070: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:52.070: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:52.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 18 06:19:52.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:52.070: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:52.070: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:52.070: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:52.070: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:52.070: INFO: 
Nov 18 06:19:54.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:54.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:54.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:54.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 18 06:19:54.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:54.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:54.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:54.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:54.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:54.065: INFO: 
Nov 18 06:19:56.069: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:56.069: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:56.069: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:56.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 18 06:19:56.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:56.069: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:56.069: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:56.069: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:56.069: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:56.069: INFO: 
Nov 18 06:19:58.073: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:58.073: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:58.073: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:19:58.073: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 18 06:19:58.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:19:58.073: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:19:58.073: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:58.073: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:58.073: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:19:58.073: INFO: 
Nov 18 06:20:00.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:00.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:00.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:00.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 18 06:20:00.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:00.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:00.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:00.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:00.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:00.063: INFO: 
Nov 18 06:20:02.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:02.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:02.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:02.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 18 06:20:02.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:02.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:02.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:02.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:02.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:02.066: INFO: 
Nov 18 06:20:04.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:04.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:04.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:04.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 18 06:20:04.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:04.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:04.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:04.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:04.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:04.061: INFO: 
Nov 18 06:20:06.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:06.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:06.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:06.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 18 06:20:06.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:06.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:06.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:06.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:06.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:06.061: INFO: 
Nov 18 06:20:08.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:08.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:08.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:08.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 18 06:20:08.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:08.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:08.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:08.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:08.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:08.062: INFO: 
Nov 18 06:20:10.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:10.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:10.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:10.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 18 06:20:10.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:10.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:10.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:10.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:10.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:10.061: INFO: 
Nov 18 06:20:12.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:12.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:12.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:12.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 18 06:20:12.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:12.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:12.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:12.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:12.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:12.062: INFO: 
Nov 18 06:20:14.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:14.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:14.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:14.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 18 06:20:14.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:14.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:14.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:14.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:14.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:14.064: INFO: 
Nov 18 06:20:16.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:16.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:16.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:16.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 18 06:20:16.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:16.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:16.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:16.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:16.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:16.061: INFO: 
Nov 18 06:20:18.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:18.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:18.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:18.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 18 06:20:18.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:18.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:18.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:18.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:18.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:18.064: INFO: 
Nov 18 06:20:20.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:20.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:20.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:20.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 18 06:20:20.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:20.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:20.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:20.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:20.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:20.062: INFO: 
Nov 18 06:20:22.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:22.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:22.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:22.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 18 06:20:22.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:22.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:22.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:22.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:22.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:22.061: INFO: 
Nov 18 06:20:24.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:24.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:24.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:24.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 18 06:20:24.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:24.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:24.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:24.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:24.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:24.061: INFO: 
Nov 18 06:20:26.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:26.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:26.065: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:26.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 18 06:20:26.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:26.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:26.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:26.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:26.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:26.065: INFO: 
Nov 18 06:20:28.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:28.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:28.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:28.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 18 06:20:28.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:28.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:28.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:28.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:28.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:28.062: INFO: 
Nov 18 06:20:30.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:30.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:30.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:30.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 18 06:20:30.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:30.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:30.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:30.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:30.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:30.062: INFO: 
Nov 18 06:20:32.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:32.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:32.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:32.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 18 06:20:32.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:32.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:32.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:32.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:32.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:32.062: INFO: 
Nov 18 06:20:34.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:34.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:34.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:34.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 18 06:20:34.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:34.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:34.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:34.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:34.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:34.062: INFO: 
Nov 18 06:20:36.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:36.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:36.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:36.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 18 06:20:36.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:36.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:36.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:36.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:36.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:36.062: INFO: 
Nov 18 06:20:38.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:38.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:38.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:38.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 18 06:20:38.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:38.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:38.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:38.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:38.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:38.062: INFO: 
Nov 18 06:20:40.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:40.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:40.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:40.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 18 06:20:40.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:40.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:40.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:40.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:40.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:40.061: INFO: 
Nov 18 06:20:42.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:42.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:42.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:42.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 18 06:20:42.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:42.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:42.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:42.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:42.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:42.064: INFO: 
Nov 18 06:20:44.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:44.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:44.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:44.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 18 06:20:44.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:44.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:44.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:44.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:44.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:44.064: INFO: 
Nov 18 06:20:46.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:46.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:46.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:46.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 18 06:20:46.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:46.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:46.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:46.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:46.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:46.063: INFO: 
Nov 18 06:20:48.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:48.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:48.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:48.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 18 06:20:48.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:48.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:48.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:48.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:48.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:48.064: INFO: 
Nov 18 06:20:50.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:50.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:50.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:50.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 18 06:20:50.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:50.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:50.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:50.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:50.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:50.064: INFO: 
Nov 18 06:20:52.070: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:52.070: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:52.070: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:52.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 18 06:20:52.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:52.070: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:52.070: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:52.070: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:52.070: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:52.070: INFO: 
Nov 18 06:20:54.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:54.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:54.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:54.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 18 06:20:54.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:54.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:54.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:54.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:54.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:54.061: INFO: 
Nov 18 06:20:56.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:56.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:56.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:56.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 18 06:20:56.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:56.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:56.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:56.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:56.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:56.062: INFO: 
Nov 18 06:20:58.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:58.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:58.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:20:58.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 18 06:20:58.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:20:58.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:20:58.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:58.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:58.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:20:58.061: INFO: 
Nov 18 06:21:00.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:00.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:00.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:00.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 18 06:21:00.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:00.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:00.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:00.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:00.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:00.062: INFO: 
Nov 18 06:21:02.065: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:02.065: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:02.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:02.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 18 06:21:02.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:02.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:02.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:02.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:02.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:02.066: INFO: 
Nov 18 06:21:04.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:04.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:04.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:04.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 18 06:21:04.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:04.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:04.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:04.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:04.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:04.062: INFO: 
Nov 18 06:21:06.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:06.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:06.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:06.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 18 06:21:06.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:06.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:06.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:06.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:06.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:06.060: INFO: 
Nov 18 06:21:08.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:08.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:08.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:08.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 18 06:21:08.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:08.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:08.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:08.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:08.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:08.062: INFO: 
Nov 18 06:21:10.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:10.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:10.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:10.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 18 06:21:10.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:10.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:10.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:10.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:10.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:10.063: INFO: 
Nov 18 06:21:12.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:12.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:12.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:12.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 18 06:21:12.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:12.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:12.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:12.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:12.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:12.062: INFO: 
Nov 18 06:21:14.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:14.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:14.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:14.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 18 06:21:14.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:14.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:14.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:14.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:14.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:14.061: INFO: 
Nov 18 06:21:16.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:16.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:16.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:16.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 18 06:21:16.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:16.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:16.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:16.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:16.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:16.064: INFO: 
Nov 18 06:21:18.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:18.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:18.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:18.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 18 06:21:18.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:18.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:18.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:18.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:18.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:18.064: INFO: 
Nov 18 06:21:20.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:20.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:20.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:20.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 18 06:21:20.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:20.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:20.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:20.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:20.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:20.066: INFO: 
Nov 18 06:21:22.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:22.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:22.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:22.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 18 06:21:22.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:22.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:22.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:22.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:22.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:22.062: INFO: 
Nov 18 06:21:24.057: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:24.057: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:24.057: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:24.057: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 18 06:21:24.057: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:24.057: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:24.057: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:24.057: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:24.057: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:24.057: INFO: 
Nov 18 06:21:26.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:26.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:26.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:26.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 18 06:21:26.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:26.065: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:26.065: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:26.065: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:26.065: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:26.065: INFO: 
Nov 18 06:21:28.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:28.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:28.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:28.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 18 06:21:28.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:28.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:28.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:28.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:28.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:28.062: INFO: 
Nov 18 06:21:30.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:30.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:30.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:30.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 18 06:21:30.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:30.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:30.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:30.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:30.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:30.062: INFO: 
Nov 18 06:21:32.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:32.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:32.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:32.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 18 06:21:32.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:32.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:32.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:32.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:32.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:32.064: INFO: 
Nov 18 06:21:34.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:34.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:34.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:34.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 18 06:21:34.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:34.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:34.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:34.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:34.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:34.061: INFO: 
Nov 18 06:21:36.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:36.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:36.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:36.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 18 06:21:36.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:36.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:36.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:36.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:36.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:36.062: INFO: 
Nov 18 06:21:38.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:38.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:38.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:38.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 18 06:21:38.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:38.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:38.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:38.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:38.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:38.062: INFO: 
Nov 18 06:21:40.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:40.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:40.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:40.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 18 06:21:40.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:40.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:40.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:40.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:40.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:40.064: INFO: 
Nov 18 06:21:42.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:42.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:42.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:42.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 18 06:21:42.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:42.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:42.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:42.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:42.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:42.063: INFO: 
Nov 18 06:21:44.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:44.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:44.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:44.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 18 06:21:44.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:44.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:44.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:44.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:44.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:44.063: INFO: 
Nov 18 06:21:46.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:46.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:46.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:46.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 18 06:21:46.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:46.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:46.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:46.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:46.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:46.061: INFO: 
Nov 18 06:21:48.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:48.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:48.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:48.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 18 06:21:48.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:48.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:48.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:48.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:48.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:48.061: INFO: 
Nov 18 06:21:50.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:50.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:50.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:50.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 18 06:21:50.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:50.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:50.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:50.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:50.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:50.063: INFO: 
Nov 18 06:21:52.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:52.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:52.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:52.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 18 06:21:52.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:52.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:52.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:52.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:52.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:52.062: INFO: 
Nov 18 06:21:54.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:54.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:54.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:54.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 18 06:21:54.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:54.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:54.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:54.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:54.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:54.063: INFO: 
Nov 18 06:21:56.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:56.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:56.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:56.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 18 06:21:56.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:56.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:56.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:56.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:56.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:56.064: INFO: 
Nov 18 06:21:58.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:58.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:58.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:21:58.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 18 06:21:58.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:21:58.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:21:58.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:58.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:58.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:21:58.067: INFO: 
Nov 18 06:22:00.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:00.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:00.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:00.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 18 06:22:00.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:00.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:00.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:00.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:00.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:00.062: INFO: 
Nov 18 06:22:02.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:02.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:02.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:02.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 18 06:22:02.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:02.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:02.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:02.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:02.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:02.061: INFO: 
Nov 18 06:22:04.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:04.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:04.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:04.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 18 06:22:04.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:04.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:04.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:04.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:04.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:04.061: INFO: 
Nov 18 06:22:06.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:06.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:06.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:06.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 18 06:22:06.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:06.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:06.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:06.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:06.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:06.063: INFO: 
Nov 18 06:22:08.249: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:08.249: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:08.249: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:08.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (235 seconds elapsed)
Nov 18 06:22:08.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:08.249: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:08.249: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:08.249: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:08.249: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:08.249: INFO: 
Nov 18 06:22:10.077: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:10.077: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:10.077: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:10.077: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 18 06:22:10.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:10.077: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:10.077: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:10.077: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:10.077: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:10.077: INFO: 
Nov 18 06:22:12.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:12.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:12.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:12.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 18 06:22:12.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:12.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:12.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:12.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:12.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:12.062: INFO: 
Nov 18 06:22:14.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:14.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:14.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:14.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 18 06:22:14.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:14.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:14.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:14.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:14.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:14.061: INFO: 
Nov 18 06:22:16.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:16.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:16.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:16.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 18 06:22:16.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:16.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:16.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:16.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:16.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:16.062: INFO: 
Nov 18 06:22:18.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:18.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:18.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:18.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 18 06:22:18.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:18.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:18.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:18.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:18.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:18.061: INFO: 
Nov 18 06:22:20.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:20.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:20.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:20.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 18 06:22:20.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:20.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:20.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:20.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:20.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:20.066: INFO: 
Nov 18 06:22:22.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:22.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:22.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:22.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 18 06:22:22.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:22.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:22.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:22.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:22.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:22.064: INFO: 
Nov 18 06:22:24.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:24.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:24.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:24.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 18 06:22:24.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:24.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:24.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:24.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:24.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:24.062: INFO: 
Nov 18 06:22:26.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:26.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:26.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:26.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 18 06:22:26.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:26.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:26.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:26.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:26.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:26.061: INFO: 
Nov 18 06:22:28.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:28.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:28.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:28.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 18 06:22:28.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:28.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:28.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:28.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:28.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:28.062: INFO: 
Nov 18 06:22:30.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:30.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:30.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:30.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 18 06:22:30.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:30.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:30.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:30.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:30.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:30.061: INFO: 
Nov 18 06:22:32.068: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:32.068: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:32.069: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:32.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 18 06:22:32.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:32.069: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:32.069: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:32.069: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:32.069: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:32.069: INFO: 
Nov 18 06:22:34.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:34.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:34.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:34.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 18 06:22:34.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:34.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:34.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:34.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:34.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:34.063: INFO: 
Nov 18 06:22:36.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:36.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:36.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:36.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 18 06:22:36.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:36.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:36.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:36.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:36.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:36.062: INFO: 
Nov 18 06:22:38.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:38.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:38.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:38.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 18 06:22:38.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:38.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:38.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:38.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:38.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:38.062: INFO: 
Nov 18 06:22:40.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:40.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:40.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:40.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 18 06:22:40.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:40.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:40.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:40.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:40.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:40.064: INFO: 
Nov 18 06:22:42.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:42.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:42.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:42.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 18 06:22:42.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:42.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:42.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:42.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:42.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:42.063: INFO: 
Nov 18 06:22:44.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:44.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:44.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:44.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 18 06:22:44.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:44.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:44.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:44.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:44.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:44.061: INFO: 
Nov 18 06:22:46.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:46.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:46.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:46.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 18 06:22:46.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:46.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:46.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:46.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:46.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:46.063: INFO: 
Nov 18 06:22:48.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:48.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:48.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:48.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 18 06:22:48.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:48.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:48.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:48.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:48.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:48.062: INFO: 
Nov 18 06:22:50.068: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:50.068: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:50.068: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:50.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 18 06:22:50.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:50.068: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:50.068: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:50.068: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:50.068: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:50.068: INFO: 
Nov 18 06:22:52.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:52.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:52.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:52.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 18 06:22:52.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:52.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:52.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:52.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:52.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:52.063: INFO: 
Nov 18 06:22:54.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:54.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:54.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:54.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 18 06:22:54.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:54.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:54.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:54.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:54.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:54.060: INFO: 
Nov 18 06:22:56.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:56.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:56.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:56.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 18 06:22:56.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:56.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:56.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:56.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:56.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:56.061: INFO: 
Nov 18 06:22:58.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:58.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:58.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:22:58.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 18 06:22:58.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:22:58.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:22:58.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:58.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:58.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:22:58.063: INFO: 
Nov 18 06:23:00.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:00.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:00.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:00.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 18 06:23:00.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:00.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:00.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:00.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:00.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:00.061: INFO: 
Nov 18 06:23:02.072: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:02.072: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:02.072: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:02.072: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 18 06:23:02.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:02.072: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:02.072: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:02.072: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:02.072: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:02.072: INFO: 
Nov 18 06:23:04.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:04.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:04.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:04.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 18 06:23:04.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:04.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:04.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:04.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:04.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:04.062: INFO: 
Nov 18 06:23:06.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:06.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:06.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:06.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 18 06:23:06.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:06.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:06.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:06.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:06.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:06.063: INFO: 
Nov 18 06:23:08.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:08.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:08.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:08.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 18 06:23:08.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:08.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:08.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:08.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:08.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:08.066: INFO: 
Nov 18 06:23:10.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:10.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:10.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:10.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 18 06:23:10.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:10.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:10.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:10.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:10.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:10.063: INFO: 
Nov 18 06:23:12.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:12.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:12.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:12.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 18 06:23:12.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:12.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:12.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:12.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:12.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:12.062: INFO: 
Nov 18 06:23:14.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:14.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:14.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:14.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 18 06:23:14.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:14.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:14.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:14.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:14.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:14.063: INFO: 
Nov 18 06:23:16.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:16.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:16.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:16.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 18 06:23:16.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:16.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:16.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:16.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:16.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:16.060: INFO: 
Nov 18 06:23:18.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:18.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:18.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:18.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 18 06:23:18.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:18.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:18.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:18.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:18.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:18.064: INFO: 
Nov 18 06:23:20.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:20.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:20.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:20.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 18 06:23:20.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:20.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:20.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:20.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:20.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:20.063: INFO: 
Nov 18 06:23:22.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:22.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:22.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:22.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 18 06:23:22.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:22.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:22.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:22.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:22.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:22.061: INFO: 
Nov 18 06:23:24.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:24.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:24.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:24.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 18 06:23:24.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:24.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:24.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:24.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:24.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:24.061: INFO: 
Nov 18 06:23:26.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:26.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:26.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:26.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 18 06:23:26.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:26.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:26.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:26.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:26.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:26.063: INFO: 
Nov 18 06:23:28.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:28.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:28.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:28.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 18 06:23:28.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:28.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:28.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:28.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:28.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:28.062: INFO: 
Nov 18 06:23:30.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:30.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:30.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:30.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 18 06:23:30.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:30.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:30.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:30.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:30.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:30.061: INFO: 
Nov 18 06:23:32.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:32.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:32.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:32.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 18 06:23:32.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:32.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:32.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:32.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:32.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:32.063: INFO: 
Nov 18 06:23:34.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:34.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:34.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:34.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 18 06:23:34.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:34.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:34.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:34.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:34.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:34.062: INFO: 
Nov 18 06:23:36.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:36.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:36.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:36.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 18 06:23:36.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:36.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:36.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:36.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:36.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:36.063: INFO: 
Nov 18 06:23:38.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:38.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:38.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:38.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 18 06:23:38.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:38.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:38.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:38.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:38.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:38.064: INFO: 
Nov 18 06:23:40.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:40.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:40.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:40.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 18 06:23:40.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:40.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:40.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:40.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:40.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:40.060: INFO: 
Nov 18 06:23:42.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:42.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:42.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:42.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 18 06:23:42.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:42.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:42.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:42.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:42.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:42.062: INFO: 
Nov 18 06:23:44.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:44.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:44.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:44.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 18 06:23:44.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:44.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:44.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:44.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:44.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:44.063: INFO: 
Nov 18 06:23:46.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:46.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:46.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:46.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 18 06:23:46.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:46.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:46.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:46.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:46.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:46.063: INFO: 
Nov 18 06:23:48.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:48.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:48.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:48.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 18 06:23:48.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:48.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:48.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:48.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:48.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:48.062: INFO: 
Nov 18 06:23:50.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:50.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:50.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:50.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 18 06:23:50.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:50.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:50.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:50.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:50.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:50.061: INFO: 
Nov 18 06:23:52.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:52.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:52.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:52.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 18 06:23:52.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:52.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:52.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:52.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:52.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:52.063: INFO: 
Nov 18 06:23:54.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:54.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:54.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:54.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 18 06:23:54.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:54.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:54.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:54.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:54.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:54.061: INFO: 
Nov 18 06:23:56.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:56.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:56.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:56.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 18 06:23:56.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:56.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:56.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:56.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:56.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:56.062: INFO: 
Nov 18 06:23:58.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:58.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:58.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:23:58.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 18 06:23:58.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:23:58.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:23:58.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:58.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:58.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:23:58.061: INFO: 
Nov 18 06:24:00.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:00.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:00.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:00.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 18 06:24:00.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:00.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:00.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:00.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:00.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:00.061: INFO: 
Nov 18 06:24:02.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:02.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:02.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:02.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 18 06:24:02.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:02.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:02.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:02.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:02.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:02.063: INFO: 
Nov 18 06:24:04.068: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:04.068: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:04.068: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:04.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 18 06:24:04.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:04.068: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:04.068: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:04.068: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:04.068: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:04.068: INFO: 
Nov 18 06:24:06.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:06.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:06.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:06.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 18 06:24:06.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:06.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:06.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:06.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:06.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:06.062: INFO: 
Nov 18 06:24:08.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:08.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:08.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:08.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 18 06:24:08.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:08.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:08.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:08.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:08.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:08.060: INFO: 
Nov 18 06:24:10.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:10.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:10.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:10.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 18 06:24:10.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:10.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:10.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:10.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:10.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:10.064: INFO: 
Nov 18 06:24:12.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:12.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:12.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:12.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 18 06:24:12.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:12.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:12.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:12.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:12.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:12.061: INFO: 
Nov 18 06:24:14.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:14.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:14.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:14.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 18 06:24:14.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:14.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:14.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:14.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:14.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:14.060: INFO: 
Nov 18 06:24:16.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:16.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:16.068: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:16.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 18 06:24:16.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:16.068: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:16.068: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:16.068: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:16.068: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:16.068: INFO: 
Nov 18 06:24:18.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:18.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:18.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:18.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 18 06:24:18.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:18.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:18.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:18.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:18.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:18.062: INFO: 
Nov 18 06:24:20.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:20.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:20.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:20.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 18 06:24:20.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:20.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:20.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:20.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:20.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:20.061: INFO: 
Nov 18 06:24:22.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:22.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:22.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:22.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 18 06:24:22.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:22.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:22.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:22.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:22.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:22.060: INFO: 
Nov 18 06:24:24.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:24.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:24.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:24.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 18 06:24:24.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:24.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:24.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:24.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:24.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:24.061: INFO: 
Nov 18 06:24:26.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:26.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:26.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:26.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 18 06:24:26.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:26.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:26.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:26.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:26.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:26.061: INFO: 
Nov 18 06:24:28.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:28.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:28.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:28.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 18 06:24:28.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:28.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:28.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:28.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:28.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:28.062: INFO: 
Nov 18 06:24:30.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:30.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:30.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:30.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 18 06:24:30.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:30.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:30.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:30.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:30.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:30.061: INFO: 
Nov 18 06:24:32.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:32.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:32.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:32.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 18 06:24:32.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:32.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:32.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:32.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:32.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:32.061: INFO: 
Nov 18 06:24:34.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:34.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:34.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:34.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 18 06:24:34.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:34.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:34.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:34.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:34.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:34.061: INFO: 
Nov 18 06:24:36.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:36.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:36.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:36.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 18 06:24:36.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:36.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:36.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:36.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:36.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:36.061: INFO: 
Nov 18 06:24:38.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:38.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:38.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:38.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 18 06:24:38.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:38.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:38.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:38.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:38.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:38.061: INFO: 
Nov 18 06:24:40.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:40.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:40.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:40.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 18 06:24:40.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:40.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:40.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:40.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:40.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:40.061: INFO: 
Nov 18 06:24:42.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:42.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:42.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:42.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 18 06:24:42.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:42.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:42.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:42.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:42.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:42.067: INFO: 
Nov 18 06:24:44.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:44.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:44.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:44.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 18 06:24:44.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:44.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:44.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:44.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:44.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:44.061: INFO: 
Nov 18 06:24:46.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:46.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:46.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:46.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 18 06:24:46.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:46.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:46.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:46.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:46.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:46.061: INFO: 
Nov 18 06:24:48.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:48.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:48.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:48.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 18 06:24:48.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:48.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:48.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:48.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:48.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:48.062: INFO: 
Nov 18 06:24:50.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:50.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:50.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:50.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 18 06:24:50.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:50.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:50.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:50.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:50.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:50.062: INFO: 
Nov 18 06:24:52.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:52.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:52.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:52.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 18 06:24:52.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:52.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:52.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:52.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:52.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:52.061: INFO: 
Nov 18 06:24:54.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:54.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:54.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:54.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 18 06:24:54.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:54.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:54.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:54.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:54.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:54.062: INFO: 
Nov 18 06:24:56.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:56.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:56.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:56.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 18 06:24:56.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:56.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:56.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:56.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:56.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:56.061: INFO: 
Nov 18 06:24:58.081: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:58.081: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:58.081: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:24:58.081: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 18 06:24:58.081: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:24:58.081: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:24:58.081: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:58.081: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:58.081: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:24:58.081: INFO: 
Nov 18 06:25:00.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:00.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:00.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:00.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 18 06:25:00.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:00.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:00.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:00.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:00.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:00.063: INFO: 
Nov 18 06:25:02.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:02.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:02.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:02.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 18 06:25:02.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:02.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:02.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:02.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:02.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:02.062: INFO: 
Nov 18 06:25:04.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:04.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:04.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:04.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 18 06:25:04.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:04.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:04.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:04.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:04.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:04.063: INFO: 
Nov 18 06:25:06.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:06.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:06.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:06.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 18 06:25:06.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:06.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:06.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:06.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:06.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:06.061: INFO: 
Nov 18 06:25:08.073: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:08.073: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:08.073: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:08.073: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 18 06:25:08.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:08.073: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:08.073: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:08.073: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:08.073: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:08.073: INFO: 
Nov 18 06:25:10.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:10.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:10.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:10.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 18 06:25:10.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:10.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:10.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:10.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:10.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:10.062: INFO: 
Nov 18 06:25:12.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:12.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:12.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:12.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 18 06:25:12.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:12.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:12.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:12.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:12.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:12.063: INFO: 
Nov 18 06:25:14.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:14.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:14.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:14.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 18 06:25:14.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:14.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:14.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:14.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:14.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:14.063: INFO: 
Nov 18 06:25:16.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:16.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:16.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:16.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 18 06:25:16.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:16.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:16.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:16.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:16.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:16.062: INFO: 
Nov 18 06:25:18.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:18.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:18.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:18.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 18 06:25:18.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:18.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:18.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:18.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:18.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:18.062: INFO: 
Nov 18 06:25:20.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:20.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:20.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:20.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 18 06:25:20.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:20.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:20.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:20.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:20.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:20.063: INFO: 
Nov 18 06:25:22.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:22.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:22.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:22.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 18 06:25:22.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:22.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:22.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:22.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:22.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:22.062: INFO: 
Nov 18 06:25:24.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:24.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:24.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:24.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 18 06:25:24.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:24.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:24.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:24.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:24.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:24.066: INFO: 
Nov 18 06:25:26.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:26.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:26.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:26.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 18 06:25:26.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:26.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:26.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:26.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:26.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:26.062: INFO: 
Nov 18 06:25:28.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:28.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:28.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:28.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 18 06:25:28.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:28.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:28.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:28.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:28.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:28.064: INFO: 
Nov 18 06:25:30.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:30.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:30.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:30.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 18 06:25:30.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:30.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:30.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:30.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:30.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:30.062: INFO: 
Nov 18 06:25:32.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:32.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:32.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:32.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 18 06:25:32.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:32.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:32.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:32.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:32.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:32.060: INFO: 
Nov 18 06:25:34.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:34.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:34.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:34.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 18 06:25:34.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:34.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:34.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:34.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:34.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:34.063: INFO: 
Nov 18 06:25:36.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:36.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:36.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:36.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 18 06:25:36.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:36.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:36.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:36.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:36.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:36.063: INFO: 
Nov 18 06:25:38.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:38.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:38.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:38.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 18 06:25:38.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:38.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:38.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:38.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:38.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:38.063: INFO: 
Nov 18 06:25:40.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:40.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:40.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:40.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 18 06:25:40.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:40.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:40.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:40.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:40.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:40.063: INFO: 
Nov 18 06:25:42.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:42.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:42.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:42.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 18 06:25:42.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:42.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:42.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:42.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:42.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:42.061: INFO: 
Nov 18 06:25:44.249: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:44.249: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:44.249: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:44.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (451 seconds elapsed)
Nov 18 06:25:44.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:44.249: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:44.249: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:44.249: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:44.249: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:44.249: INFO: 
Nov 18 06:25:46.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:46.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:46.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:46.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 18 06:25:46.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:46.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:46.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:46.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:46.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:46.062: INFO: 
Nov 18 06:25:48.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:48.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:48.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:48.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 18 06:25:48.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:48.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:48.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:48.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:48.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:48.061: INFO: 
Nov 18 06:25:50.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:50.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:50.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:50.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 18 06:25:50.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:50.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:50.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:50.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:50.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:50.062: INFO: 
Nov 18 06:25:52.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:52.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:52.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:52.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 18 06:25:52.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:52.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:52.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:52.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:52.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:52.063: INFO: 
Nov 18 06:25:54.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:54.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:54.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:54.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 18 06:25:54.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:54.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:54.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:54.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:54.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:54.062: INFO: 
Nov 18 06:25:56.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:56.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:56.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:56.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 18 06:25:56.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:56.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:56.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:56.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:56.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:56.066: INFO: 
Nov 18 06:25:58.068: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:58.068: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:58.068: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:25:58.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 18 06:25:58.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:25:58.068: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:25:58.068: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:58.068: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:58.068: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:25:58.068: INFO: 
Nov 18 06:26:00.074: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:00.074: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:00.074: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:00.074: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 18 06:26:00.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:00.074: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:00.074: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:00.074: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:00.074: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:00.074: INFO: 
Nov 18 06:26:02.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:02.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:02.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:02.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 18 06:26:02.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:02.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:02.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:02.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:02.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:02.062: INFO: 
Nov 18 06:26:04.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:04.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:04.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:04.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 18 06:26:04.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:04.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:04.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:04.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:04.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:04.061: INFO: 
Nov 18 06:26:06.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:06.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:06.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:06.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 18 06:26:06.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:06.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:06.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:06.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:06.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:06.062: INFO: 
Nov 18 06:26:08.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:08.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:08.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:08.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 18 06:26:08.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:08.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:08.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:08.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:08.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:08.062: INFO: 
Nov 18 06:26:10.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:10.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:10.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:10.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 18 06:26:10.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:10.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:10.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:10.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:10.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:10.066: INFO: 
Nov 18 06:26:12.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:12.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:12.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:12.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 18 06:26:12.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:12.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:12.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:12.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:12.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:12.061: INFO: 
Nov 18 06:26:14.249: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:14.249: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:14.249: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:14.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (481 seconds elapsed)
Nov 18 06:26:14.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:14.249: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:14.249: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:14.249: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:14.249: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:14.249: INFO: 
Nov 18 06:26:16.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:16.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:16.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:16.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 18 06:26:16.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:16.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:16.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:16.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:16.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:16.061: INFO: 
Nov 18 06:26:18.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:18.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:18.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:18.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 18 06:26:18.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:18.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:18.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:18.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:18.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:18.062: INFO: 
Nov 18 06:26:20.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:20.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:20.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:20.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 18 06:26:20.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:20.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:20.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:20.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:20.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:20.062: INFO: 
Nov 18 06:26:22.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:22.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:22.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:22.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 18 06:26:22.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:22.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:22.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:22.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:22.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:22.063: INFO: 
Nov 18 06:26:24.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:24.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:24.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:24.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 18 06:26:24.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:24.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:24.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:24.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:24.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:24.062: INFO: 
Nov 18 06:26:26.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:26.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:26.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:26.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 18 06:26:26.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:26.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:26.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:26.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:26.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:26.062: INFO: 
Nov 18 06:26:28.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:28.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:28.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:28.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 18 06:26:28.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:28.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:28.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:28.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:28.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:28.061: INFO: 
Nov 18 06:26:30.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:30.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:30.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:30.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 18 06:26:30.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:30.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:30.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:30.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:30.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:30.064: INFO: 
Nov 18 06:26:32.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:32.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:32.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:32.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 18 06:26:32.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:32.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:32.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:32.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:32.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:32.061: INFO: 
Nov 18 06:26:34.084: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:34.084: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:34.084: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:34.084: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 18 06:26:34.084: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:34.084: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:34.084: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:34.084: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:34.084: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:34.084: INFO: 
Nov 18 06:26:36.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:36.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:36.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:36.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 18 06:26:36.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:36.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:36.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:36.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:36.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:36.062: INFO: 
Nov 18 06:26:38.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:38.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:38.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:38.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 18 06:26:38.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:38.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:38.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:38.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:38.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:38.064: INFO: 
Nov 18 06:26:40.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:40.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:40.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:40.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 18 06:26:40.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:40.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:40.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:40.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:40.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:40.061: INFO: 
Nov 18 06:26:42.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:42.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:42.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:42.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 18 06:26:42.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:42.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:42.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:42.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:42.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:42.062: INFO: 
Nov 18 06:26:44.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:44.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:44.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:44.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 18 06:26:44.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:44.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:44.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:44.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:44.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:44.062: INFO: 
Nov 18 06:26:46.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:46.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:46.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:46.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 18 06:26:46.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:46.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:46.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:46.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:46.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:46.063: INFO: 
Nov 18 06:26:48.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:48.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:48.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:48.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 18 06:26:48.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:48.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:48.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:48.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:48.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:48.062: INFO: 
Nov 18 06:26:50.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:50.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:50.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:50.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 18 06:26:50.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:50.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:50.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:50.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:50.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:50.063: INFO: 
Nov 18 06:26:52.072: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:52.072: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:52.072: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:52.072: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 18 06:26:52.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:52.072: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:52.072: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:52.072: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:52.072: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:52.072: INFO: 
Nov 18 06:26:54.099: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:54.099: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:54.099: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:54.099: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 18 06:26:54.099: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:54.099: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:54.099: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:54.099: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:54.099: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:54.099: INFO: 
Nov 18 06:26:56.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:56.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:56.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:56.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 18 06:26:56.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:56.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:56.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:56.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:56.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:56.062: INFO: 
Nov 18 06:26:58.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:58.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:58.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:26:58.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 18 06:26:58.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:26:58.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:26:58.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:58.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:58.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:26:58.062: INFO: 
Nov 18 06:27:00.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:00.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:00.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:00.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 18 06:27:00.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:00.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:00.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:00.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:00.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:00.064: INFO: 
Nov 18 06:27:02.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:02.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:02.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:02.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 18 06:27:02.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:02.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:02.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:02.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:02.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:02.062: INFO: 
Nov 18 06:27:04.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:04.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:04.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:04.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 18 06:27:04.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:04.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:04.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:04.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:04.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:04.062: INFO: 
Nov 18 06:27:06.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:06.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:06.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:06.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 18 06:27:06.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:06.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:06.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:06.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:06.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:06.063: INFO: 
Nov 18 06:27:08.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:08.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:08.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:08.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 18 06:27:08.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:08.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:08.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:08.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:08.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:08.062: INFO: 
Nov 18 06:27:10.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:10.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:10.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:10.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 18 06:27:10.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:10.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:10.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:10.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:10.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:10.067: INFO: 
Nov 18 06:27:12.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:12.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:12.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:12.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 18 06:27:12.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:12.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:12.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:12.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:12.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:12.063: INFO: 
Nov 18 06:27:14.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:14.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:14.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:14.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 18 06:27:14.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:14.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:14.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:14.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:14.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:14.063: INFO: 
Nov 18 06:27:16.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:16.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:16.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:16.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 18 06:27:16.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:16.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:16.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:16.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:16.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:16.064: INFO: 
Nov 18 06:27:18.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:18.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:18.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:18.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 18 06:27:18.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:18.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:18.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:18.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:18.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:18.063: INFO: 
Nov 18 06:27:20.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:20.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:20.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:20.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 18 06:27:20.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:20.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:20.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:20.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:20.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:20.062: INFO: 
Nov 18 06:27:22.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:22.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:22.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:22.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 18 06:27:22.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:22.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:22.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:22.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:22.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:22.061: INFO: 
Nov 18 06:27:24.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:24.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:24.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:24.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 18 06:27:24.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:24.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:24.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:24.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:24.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:24.062: INFO: 
Nov 18 06:27:26.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:26.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:26.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:26.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 18 06:27:26.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:26.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:26.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:26.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:26.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:26.063: INFO: 
Nov 18 06:27:28.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:28.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:28.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:28.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 18 06:27:28.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:28.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:28.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:28.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:28.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:28.063: INFO: 
Nov 18 06:27:30.060: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:30.060: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:30.060: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:30.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 18 06:27:30.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:30.060: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:30.060: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:30.060: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:30.060: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:30.060: INFO: 
Nov 18 06:27:32.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:32.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:32.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:32.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 18 06:27:32.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:32.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:32.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:32.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:32.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:32.063: INFO: 
Nov 18 06:27:34.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:34.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:34.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:34.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 18 06:27:34.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:34.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:34.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:34.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:34.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:34.063: INFO: 
Nov 18 06:27:36.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:36.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:36.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:36.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 18 06:27:36.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:36.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:36.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:36.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:36.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:36.064: INFO: 
Nov 18 06:27:38.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:38.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:38.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:38.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 18 06:27:38.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:38.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:38.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:38.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:38.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:38.062: INFO: 
Nov 18 06:27:40.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:40.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:40.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:40.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 18 06:27:40.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:40.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:40.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:40.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:40.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:40.061: INFO: 
Nov 18 06:27:42.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:42.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:42.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:42.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 18 06:27:42.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:42.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:42.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:42.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:42.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:42.061: INFO: 
Nov 18 06:27:44.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:44.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:44.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:44.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 18 06:27:44.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:44.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:44.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:44.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:44.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:44.062: INFO: 
Nov 18 06:27:46.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:46.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:46.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:46.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 18 06:27:46.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:46.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:46.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:46.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:46.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:46.064: INFO: 
Nov 18 06:27:48.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:48.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:48.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:48.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 18 06:27:48.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:48.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:48.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:48.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:48.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:48.063: INFO: 
Nov 18 06:27:50.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:50.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:50.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:50.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 18 06:27:50.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:50.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:50.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:50.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:50.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:50.063: INFO: 
Nov 18 06:27:52.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:52.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:52.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:52.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 18 06:27:52.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:52.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:52.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:52.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:52.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:52.063: INFO: 
Nov 18 06:27:54.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:54.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:54.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:54.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 18 06:27:54.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:54.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:54.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:54.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:54.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:54.062: INFO: 
Nov 18 06:27:56.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:56.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:56.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:56.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 18 06:27:56.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:56.061: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:56.061: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:56.061: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:56.061: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:56.061: INFO: 
Nov 18 06:27:58.062: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:58.062: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:58.062: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:27:58.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 18 06:27:58.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:27:58.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:27:58.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:58.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:58.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:27:58.062: INFO: 
Nov 18 06:28:00.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:00.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:00.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:00.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 18 06:28:00.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:00.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:00.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:00.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:00.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:00.063: INFO: 
Nov 18 06:28:02.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:02.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:02.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:02.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 18 06:28:02.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:02.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:02.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:02.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:02.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:02.064: INFO: 
Nov 18 06:28:04.064: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:04.064: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:04.064: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:04.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 18 06:28:04.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:04.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:04.064: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:04.064: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:04.064: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:04.064: INFO: 
Nov 18 06:28:06.061: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:06.061: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:06.061: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:06.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 18 06:28:06.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:06.062: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:06.062: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:06.062: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:06.062: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:06.062: INFO: 
Nov 18 06:28:08.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:08.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:08.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:08.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 18 06:28:08.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:08.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:08.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:08.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:08.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:08.067: INFO: 
Nov 18 06:28:10.067: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:10.067: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:10.067: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:10.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 18 06:28:10.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:10.067: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:10.067: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:10.067: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:10.067: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:10.067: INFO: 
Nov 18 06:28:12.066: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:12.066: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:12.066: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:12.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 18 06:28:12.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:12.066: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:12.066: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:12.066: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:12.066: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:12.066: INFO: 
Nov 18 06:28:14.063: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:14.063: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:14.063: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:14.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 18 06:28:14.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:14.063: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:14.063: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.063: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.063: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.063: INFO: 
Nov 18 06:28:14.469: INFO: The status of Pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:14.469: INFO: The status of Pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:14.469: INFO: The status of Pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 06:28:14.469: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (601 seconds elapsed)
Nov 18 06:28:14.469: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 06:28:14.469: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:14.469: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.469: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.469: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.469: INFO: 
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/18/22 06:28:14.469�[0m
�[1mSTEP:�[0m Found 130 events. �[38;5;243m11/18/22 06:28:14.615�[0m
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:13:56 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-53k332-control-plane-zkfrt_cb95ac96-c64b-4529-9237-c13d80a94984 became leader
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:13:59 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-53k332-control-plane-zkfrt_c2f4b460-c320-44a8-b26a-b3c37568b09c became leader
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:10 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:10 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-fxx4m
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:10 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-h7n5p
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:10 +0000 UTC - event for coredns-787d4945fb-fxx4m: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:10 +0000 UTC - event for coredns-787d4945fb-h7n5p: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:10 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-8njd9
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:10 +0000 UTC - event for kube-proxy-8njd9: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-8njd9 to capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:11 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-8njd9
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:14 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-jtdxv
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:14 +0000 UTC - event for kube-proxy-jtdxv: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-jtdxv to capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:15 +0000 UTC - event for kube-proxy-jtdxv: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_fbd3976770c82f"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:20 +0000 UTC - event for kube-proxy-jtdxv: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_fbd3976770c82f" in 4.758942065s (4.758959366s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:20 +0000 UTC - event for kube-proxy-jtdxv: {kubelet capz-conf-53k332-control-plane-zkfrt} Started: Started container kube-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:20 +0000 UTC - event for kube-proxy-jtdxv: {kubelet capz-conf-53k332-control-plane-zkfrt} Created: Created container kube-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:26 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:26 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-lq5sv
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:26 +0000 UTC - event for metrics-server-c9574f845-lq5sv: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:28 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:28 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-4jwqm
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:28 +0000 UTC - event for calico-kube-controllers-657b584867-4jwqm: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:28 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-x2xg9
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:29 +0000 UTC - event for calico-node-x2xg9: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-x2xg9 to capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:29 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:37 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Started: Started container upgrade-ipam
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:37 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Created: Created container upgrade-ipam
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:37 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.888740175s (7.888755375s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:41 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Created: Created container install-cni
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:41 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Started: Started container install-cni
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:41 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:43 +0000 UTC - event for calico-kube-controllers-657b584867-4jwqm: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-4jwqm to capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:43 +0000 UTC - event for coredns-787d4945fb-fxx4m: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-fxx4m to capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:43 +0000 UTC - event for coredns-787d4945fb-h7n5p: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-h7n5p to capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:43 +0000 UTC - event for metrics-server-c9574f845-lq5sv: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-lq5sv to capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:44 +0000 UTC - event for calico-kube-controllers-657b584867-4jwqm: {kubelet capz-conf-53k332-control-plane-zkfrt} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "53cdebdd0222bb3d9f94c9bee9108a5c3870650d9bc7f71e258d482b3e4a934f": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:44 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:44 +0000 UTC - event for coredns-787d4945fb-fxx4m: {kubelet capz-conf-53k332-control-plane-zkfrt} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d024b4cee2dc4c1288c8b1b0f83d64358e09fc3368903f8cc5c940f912765dda": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:44 +0000 UTC - event for coredns-787d4945fb-h7n5p: {kubelet capz-conf-53k332-control-plane-zkfrt} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0e684db80672484df73e78203ddfa311826fc818cf9d19178f78aa7045be9a86": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:44 +0000 UTC - event for metrics-server-c9574f845-lq5sv: {kubelet capz-conf-53k332-control-plane-zkfrt} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "9f1ce04790b9b49b66de6f6483199361b9efbc8df769a64bb1f1d59b51ccd126": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:51 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.819890202s (7.819896802s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:52 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Created: Created container calico-node
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:52 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Started: Started container calico-node
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:53 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused

Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:54 +0000 UTC - event for calico-node-x2xg9: {kubelet capz-conf-53k332-control-plane-zkfrt} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503

Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:56 +0000 UTC - event for calico-kube-controllers-657b584867-4jwqm: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:57 +0000 UTC - event for coredns-787d4945fb-h7n5p: {kubelet capz-conf-53k332-control-plane-zkfrt} Started: Started container coredns
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:57 +0000 UTC - event for coredns-787d4945fb-h7n5p: {kubelet capz-conf-53k332-control-plane-zkfrt} Created: Created container coredns
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:57 +0000 UTC - event for coredns-787d4945fb-h7n5p: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:57 +0000 UTC - event for metrics-server-c9574f845-lq5sv: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:14:58 +0000 UTC - event for coredns-787d4945fb-h7n5p: {kubelet capz-conf-53k332-control-plane-zkfrt} Unhealthy: Readiness probe failed: Get "http://192.168.134.66:8181/ready": dial tcp 192.168.134.66:8181: connect: connection refused
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:00 +0000 UTC - event for coredns-787d4945fb-fxx4m: {kubelet capz-conf-53k332-control-plane-zkfrt} Created: Created container coredns
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:00 +0000 UTC - event for coredns-787d4945fb-fxx4m: {kubelet capz-conf-53k332-control-plane-zkfrt} Started: Started container coredns
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:00 +0000 UTC - event for coredns-787d4945fb-fxx4m: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:02 +0000 UTC - event for calico-kube-controllers-657b584867-4jwqm: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 6.259260969s (6.259313869s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:02 +0000 UTC - event for calico-kube-controllers-657b584867-4jwqm: {kubelet capz-conf-53k332-control-plane-zkfrt} Started: Started container calico-kube-controllers
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:02 +0000 UTC - event for calico-kube-controllers-657b584867-4jwqm: {kubelet capz-conf-53k332-control-plane-zkfrt} Created: Created container calico-kube-controllers
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:04 +0000 UTC - event for calico-kube-controllers-657b584867-4jwqm: {kubelet capz-conf-53k332-control-plane-zkfrt} Unhealthy: Readiness probe failed: Failed to read status file /status/status.json: unexpected end of JSON input

Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:06 +0000 UTC - event for metrics-server-c9574f845-lq5sv: {kubelet capz-conf-53k332-control-plane-zkfrt} Created: Created container metrics-server
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:06 +0000 UTC - event for metrics-server-c9574f845-lq5sv: {kubelet capz-conf-53k332-control-plane-zkfrt} Started: Started container metrics-server
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:15:06 +0000 UTC - event for metrics-server-c9574f845-lq5sv: {kubelet capz-conf-53k332-control-plane-zkfrt} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.677051525s (8.798214817s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:51 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-qggsb
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:51 +0000 UTC - event for calico-node-windows-qggsb: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-qggsb to capz-conf-l9sp8
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:51 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-px49p
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:51 +0000 UTC - event for containerd-logger-px49p: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-px49p to capz-conf-l9sp8
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:51 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-f8sts
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:51 +0000 UTC - event for kube-proxy-windows-f8sts: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-f8sts to capz-conf-l9sp8
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:53 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} FailedMount: MountVolume.SetUp failed for volume "calico-config-windows" : failed to sync configmap cache: timed out waiting for the condition
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:53 +0000 UTC - event for containerd-logger-px49p: {kubelet capz-conf-l9sp8} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:16:53 +0000 UTC - event for kube-proxy-windows-f8sts: {kubelet capz-conf-l9sp8} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:08 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:08 +0000 UTC - event for containerd-logger-px49p: {kubelet capz-conf-l9sp8} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:08 +0000 UTC - event for kube-proxy-windows-f8sts: {kubelet capz-conf-l9sp8} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess" already present on machine
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:08 +0000 UTC - event for kube-proxy-windows-f8sts: {kubelet capz-conf-l9sp8} Created: Created container kube-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:08 +0000 UTC - event for kube-proxy-windows-f8sts: {kubelet capz-conf-l9sp8} Started: Started container kube-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:12 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-p5j6m
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:12 +0000 UTC - event for calico-node-windows-p5j6m: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-p5j6m to capz-conf-qtb4d
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:12 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-b5j6l
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:12 +0000 UTC - event for containerd-logger-b5j6l: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-b5j6l to capz-conf-qtb4d
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:12 +0000 UTC - event for containerd-logger-px49p: {kubelet capz-conf-l9sp8} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.3106903s (4.3106903s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:12 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-8b9zj
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:12 +0000 UTC - event for kube-proxy-windows-8b9zj: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-8b9zj to capz-conf-qtb4d
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:14 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:14 +0000 UTC - event for kube-proxy-windows-8b9zj: {kubelet capz-conf-qtb4d} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:19 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Created: Created container install-cni
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:19 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 6.2207728s (10.494974s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:19 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Started: Started container install-cni
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:19 +0000 UTC - event for containerd-logger-px49p: {kubelet capz-conf-l9sp8} Started: Started container containerd-logger
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:19 +0000 UTC - event for containerd-logger-px49p: {kubelet capz-conf-l9sp8} Created: Created container containerd-logger
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:21 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-kbxmn
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:21 +0000 UTC - event for csi-proxy-kbxmn: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-kbxmn to capz-conf-l9sp8
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:21 +0000 UTC - event for csi-proxy-kbxmn: {kubelet capz-conf-l9sp8} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:24 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:31 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:31 +0000 UTC - event for containerd-logger-b5j6l: {kubelet capz-conf-qtb4d} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:31 +0000 UTC - event for kube-proxy-windows-8b9zj: {kubelet capz-conf-qtb4d} Created: Created container kube-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:31 +0000 UTC - event for kube-proxy-windows-8b9zj: {kubelet capz-conf-qtb4d} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess" already present on machine
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:31 +0000 UTC - event for kube-proxy-windows-8b9zj: {kubelet capz-conf-qtb4d} Started: Started container kube-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:35 +0000 UTC - event for csi-proxy-kbxmn: {kubelet capz-conf-l9sp8} Started: Started container csi-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:35 +0000 UTC - event for csi-proxy-kbxmn: {kubelet capz-conf-l9sp8} Created: Created container csi-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:35 +0000 UTC - event for csi-proxy-kbxmn: {kubelet capz-conf-l9sp8} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 13.2808882s (13.2808882s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:36 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Started: Started container install-cni
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:36 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Created: Created container install-cni
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:36 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.1493798s (5.1493798s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:38 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.8089299s (14.0091082s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:38 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Created: Created container calico-node-startup
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:38 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-tffx7
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:38 +0000 UTC - event for csi-proxy-tffx7: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-tffx7 to capz-conf-qtb4d
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:39 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Started: Started container calico-node-startup
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:39 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:39 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 765.5129ms (765.5129ms including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:39 +0000 UTC - event for csi-proxy-tffx7: {kubelet capz-conf-qtb4d} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:41 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:41 +0000 UTC - event for containerd-logger-b5j6l: {kubelet capz-conf-qtb4d} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 5.6439275s (10.7763085s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:45 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Created: Created container calico-node-felix
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:45 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Started: Started container calico-node-felix
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:48 +0000 UTC - event for containerd-logger-b5j6l: {kubelet capz-conf-qtb4d} Started: Started container containerd-logger
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:48 +0000 UTC - event for containerd-logger-b5j6l: {kubelet capz-conf-qtb4d} Created: Created container containerd-logger
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:58 +0000 UTC - event for csi-proxy-tffx7: {kubelet capz-conf-qtb4d} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 16.9097435s (19.7774434s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:58 +0000 UTC - event for csi-proxy-tffx7: {kubelet capz-conf-qtb4d} Created: Created container csi-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:17:59 +0000 UTC - event for csi-proxy-tffx7: {kubelet capz-conf-qtb4d} Started: Started container csi-proxy
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:02 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.1160097s (21.4203252s including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:03 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Started: Started container calico-node-startup
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:03 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:03 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Created: Created container calico-node-startup
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:04 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 831.7475ms (831.7475ms including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:07 +0000 UTC - event for calico-node-windows-qggsb: {kubelet capz-conf-l9sp8} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 813.8893ms (813.8893ms including waiting)
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:09 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Created: Created container calico-node-felix
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:10 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Started: Started container calico-node-felix
Nov 18 06:28:14.615: INFO: At 2022-11-18 06:18:31 +0000 UTC - event for calico-node-windows-p5j6m: {kubelet capz-conf-qtb4d} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 781.5914ms (781.5914ms including waiting)
Nov 18 06:28:14.778: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 18 06:28:14.778: INFO: calico-kube-controllers-657b584867-4jwqm                      capz-conf-53k332-control-plane-zkfrt  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:43 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:15:05 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:15:05 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:43 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: calico-node-windows-p5j6m                                     capz-conf-qtb4d                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:41 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:38 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:38 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:12 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: calico-node-windows-qggsb                                     capz-conf-l9sp8                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:24 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:12 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:18:12 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:16:51 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: calico-node-x2xg9                                             capz-conf-53k332-control-plane-zkfrt  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:44 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:59 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:59 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:28 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: containerd-logger-b5j6l                                       capz-conf-qtb4d                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:13 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:49 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:49 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:12 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: containerd-logger-px49p                                       capz-conf-l9sp8                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:16:52 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:19 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:19 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:16:51 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: coredns-787d4945fb-fxx4m                                      capz-conf-53k332-control-plane-zkfrt  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:43 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:15:01 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:15:01 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:43 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: coredns-787d4945fb-h7n5p                                      capz-conf-53k332-control-plane-zkfrt  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:43 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:15:00 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:15:00 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:43 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: csi-proxy-kbxmn                                               capz-conf-l9sp8                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:21 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:35 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:35 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:21 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: csi-proxy-tffx7                                               capz-conf-qtb4d                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:38 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:59 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:59 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:38 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: etcd-capz-conf-53k332-control-plane-zkfrt                     capz-conf-53k332-control-plane-zkfrt  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:11 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:13 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:13 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:11 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.778: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt  capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.778: INFO: kube-proxy-jtdxv                                              capz-conf-53k332-control-plane-zkfrt  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:14 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:20 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:20 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:14 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: kube-proxy-windows-8b9zj                                      capz-conf-qtb4d                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:13 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:32 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:32 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:12 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: kube-proxy-windows-f8sts                                      capz-conf-l9sp8                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:16:52 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:09 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:17:09 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:16:51 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt           capz-conf-53k332-control-plane-zkfrt  Pending         []
Nov 18 06:28:14.778: INFO: metrics-server-c9574f845-lq5sv                                capz-conf-53k332-control-plane-zkfrt  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:43 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:15:34 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:15:34 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 06:14:43 +0000 UTC  }]
Nov 18 06:28:14.778: INFO: 
Nov 18 06:28:15.922: INFO: 
Logging node info for node capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:16.049: INFO: Node Info: &Node{ObjectMeta:{capz-conf-53k332-control-plane-zkfrt    65512b71-1ece-40ac-b27d-77de97ccdb6d 1775 0 2022-11-18 06:14:08 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:westeurope failure-domain.beta.kubernetes.io/zone:westeurope-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-53k332-control-plane-zkfrt kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:westeurope topology.kubernetes.io/zone:westeurope-3] map[cluster.x-k8s.io/cluster-name:capz-conf-53k332 cluster.x-k8s.io/cluster-namespace:capz-conf-53k332 cluster.x-k8s.io/machine:capz-conf-53k332-control-plane-mbplq cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-53k332-control-plane kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.0.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.134.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-18 06:14:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-18 06:14: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":{}}}} } {manager Update v1 2022-11-18 06:14:23 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2022-11-18 06:14:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-18 06:14:52 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2022-11-18 06:25:22 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-53k332/providers/Microsoft.Compute/virtualMachines/capz-conf-53k332-control-plane-zkfrt,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: {{8344723456 0} {<nil>}  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: {{8239865856 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2022-11-18 06:14:52 +0000 UTC,LastTransitionTime:2022-11-18 06:14:52 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-18 06:25:22 +0000 UTC,LastTransitionTime:2022-11-18 06:14:08 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 06:25:22 +0000 UTC,LastTransitionTime:2022-11-18 06:14:08 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 06:25:22 +0000 UTC,LastTransitionTime:2022-11-18 06:14:08 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 06:25:22 +0000 UTC,LastTransitionTime:2022-11-18 06:14:43 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-53k332-control-plane-zkfrt,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:c7335e3a90c34d0a95455bbcd4743d68,SystemUUID:22360e9e-f123-c64c-b01e-ba59b64ca5be,BootID:17f00380-d2d9-49e0-ba0a-8d903c48713d,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.30+fbd3976770c82f,KubeProxyVersion:v1.27.0-alpha.0.30+fbd3976770c82f,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:b83c1d70989e1fe87583607bf5aee1ee34e52773d4755b95f5cf5a451962f3a4 registry.k8s.io/etcd:3.5.5-0],SizeBytes:102417044,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:6f72b851544986cb0921b53ea655ec04c36131248f16d4ad110cb3ca0c369dc1 registry.k8s.io/etcd:3.5.4-0],SizeBytes:102157811,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:78bc199299f966b0694dc4044501aee2d7ebd6862b2b0a00bca3ee8d3813c82f docker.io/calico/kube-controllers:v3.23.0],SizeBytes:56343954,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:d21364e0c633a2e2e59c3839983222a0cbd1a20b5f65447dc135d776a3fee704 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:35317342,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:4188262a351f156e8027ff81693d771c35b34b668cbd61e59c4a4490dd5c08f3 registry.k8s.io/kube-apiserver:v1.25.3],SizeBytes:34238163,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:4cba827b4565c9d11a9a8648070fa8c3e89f0b9eb88ac1c0a24b5d5a96eda2c1 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:32243894,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:d3a06262256f3e7578d5f77df137a8cdf58f9f498f35b5b56d116e8a7e31dc91 registry.k8s.io/kube-controller-manager:v1.25.3],SizeBytes:31261869,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:74af4dd1f4b40265afc2c24fa21b10d22984f08736e8036c685974aeee2ac2cf gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:21534369,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:3e28658c9fd10358a4da39594346bff855e5bea14e538977fc62cab7cff7e7b4 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_fbd3976770c82f],SizeBytes:21532658,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:6bf25f038543e1f433cb7f2bdda445ed348c7b9279935ebc2ae4f432308ed82f registry.k8s.io/kube-proxy:v1.25.3],SizeBytes:20265805,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:1a77cd3899f75eb90f4ebdb50e81a5a89fbe7984292b185f1168913520813c74 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:17482420,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 18 06:28:16.050: INFO: 
Logging kubelet events for node capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:16.160: INFO: 
Logging pods the kubelet thinks is on node capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:16.393: INFO: kube-controller-manager-capz-conf-53k332-control-plane-zkfrt started at <nil> (0+0 container statuses recorded)
Nov 18 06:28:16.393: INFO: etcd-capz-conf-53k332-control-plane-zkfrt started at 2022-11-18 06:14:11 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:16.393: INFO: 	Container etcd ready: true, restart count 0
Nov 18 06:28:16.393: INFO: metrics-server-c9574f845-lq5sv started at 2022-11-18 06:14:43 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:16.393: INFO: 	Container metrics-server ready: true, restart count 0
Nov 18 06:28:16.393: INFO: calico-kube-controllers-657b584867-4jwqm started at 2022-11-18 06:14:43 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:16.393: INFO: 	Container calico-kube-controllers ready: true, restart count 0
Nov 18 06:28:16.393: INFO: coredns-787d4945fb-h7n5p started at 2022-11-18 06:14:43 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:16.393: INFO: 	Container coredns ready: true, restart count 0
Nov 18 06:28:16.393: INFO: kube-apiserver-capz-conf-53k332-control-plane-zkfrt started at <nil> (0+0 container statuses recorded)
Nov 18 06:28:16.393: INFO: kube-proxy-jtdxv started at 2022-11-18 06:14:14 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:16.393: INFO: 	Container kube-proxy ready: true, restart count 0
Nov 18 06:28:16.393: INFO: calico-node-x2xg9 started at 2022-11-18 06:14:29 +0000 UTC (2+1 container statuses recorded)
Nov 18 06:28:16.393: INFO: 	Init container upgrade-ipam ready: true, restart count 0
Nov 18 06:28:16.393: INFO: 	Init container install-cni ready: true, restart count 0
Nov 18 06:28:16.393: INFO: 	Container calico-node ready: true, restart count 0
Nov 18 06:28:16.393: INFO: coredns-787d4945fb-fxx4m started at 2022-11-18 06:14:43 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:16.393: INFO: 	Container coredns ready: true, restart count 0
Nov 18 06:28:16.393: INFO: kube-scheduler-capz-conf-53k332-control-plane-zkfrt started at <nil> (0+0 container statuses recorded)
Nov 18 06:28:16.800: INFO: 
Latency metrics for node capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:16.800: INFO: 
Logging node info for node capz-conf-l9sp8
Nov 18 06:28:16.913: INFO: Node Info: &Node{ObjectMeta:{capz-conf-l9sp8    5eab4010-520a-4b4a-969d-ad64c488484a 2018 0 2022-11-18 06:16:51 +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:westeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-l9sp8 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:westeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-53k332 cluster.x-k8s.io/cluster-namespace:capz-conf-53k332 cluster.x-k8s.io/machine:capz-conf-53k332-md-win-748cc4c8f7-2hldm cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-53k332-md-win-748cc4c8f7 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.108.65 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:44:1a:02 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-18 06:16:51 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-18 06:16:51 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2022-11-18 06:17:21 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-18 06:17:47 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-18 06:18:03 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-18 06:28:06 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-53k332/providers/Microsoft.Compute/virtualMachines/capz-conf-l9sp8,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{136912564224 0} {<nil>} 133703676Ki BinarySI},memory: {{17179398144 0} {<nil>} 16776756Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{123221307598 0} {<nil>} 123221307598 DecimalSI},memory: {{17074540544 0} {<nil>} 16674356Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-18 06:28:06 +0000 UTC,LastTransitionTime:2022-11-18 06:16:51 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 06:28:06 +0000 UTC,LastTransitionTime:2022-11-18 06:16:51 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 06:28:06 +0000 UTC,LastTransitionTime:2022-11-18 06:16:51 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 06:28:06 +0000 UTC,LastTransitionTime:2022-11-18 06:17:21 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-l9sp8,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-l9sp8,SystemUUID:786280EA-EC7D-4D69-8FAF-5B0C0561124F,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.30+fbd3976770c82f-dirty,KubeProxyVersion:v1.27.0-alpha.0.30+fbd3976770c82f-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 18 06:28:16.913: INFO: 
Logging kubelet events for node capz-conf-l9sp8
Nov 18 06:28:17.024: INFO: 
Logging pods the kubelet thinks is on node capz-conf-l9sp8
Nov 18 06:28:17.155: INFO: containerd-logger-px49p started at 2022-11-18 06:16:52 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:17.155: INFO: 	Container containerd-logger ready: true, restart count 0
Nov 18 06:28:17.155: INFO: kube-proxy-windows-f8sts started at 2022-11-18 06:16:52 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:17.155: INFO: 	Container kube-proxy ready: true, restart count 0
Nov 18 06:28:17.155: INFO: calico-node-windows-qggsb started at 2022-11-18 06:16:52 +0000 UTC (1+2 container statuses recorded)
Nov 18 06:28:17.155: INFO: 	Init container install-cni ready: true, restart count 0
Nov 18 06:28:17.155: INFO: 	Container calico-node-felix ready: true, restart count 1
Nov 18 06:28:17.155: INFO: 	Container calico-node-startup ready: true, restart count 0
Nov 18 06:28:17.155: INFO: csi-proxy-kbxmn started at 2022-11-18 06:17:21 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:17.155: INFO: 	Container csi-proxy ready: true, restart count 0
Nov 18 06:28:17.561: INFO: 
Latency metrics for node capz-conf-l9sp8
Nov 18 06:28:17.561: INFO: 
Logging node info for node capz-conf-qtb4d
Nov 18 06:28:17.674: INFO: Node Info: &Node{ObjectMeta:{capz-conf-qtb4d    27e90ec5-7b0e-4309-95d0-c9665297d006 1590 0 2022-11-18 06:17:12 +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:westeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-qtb4d kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:westeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-53k332 cluster.x-k8s.io/cluster-namespace:capz-conf-53k332 cluster.x-k8s.io/machine:capz-conf-53k332-md-win-748cc4c8f7-k27xh cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-53k332-md-win-748cc4c8f7 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.46.65 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:bc:3f:15 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-18 06:17:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-18 06:17:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2022-11-18 06:17:38 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-18 06:18:01 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-18 06:18:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-18 06:23:19 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-53k332/providers/Microsoft.Compute/virtualMachines/capz-conf-qtb4d,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{136912564224 0} {<nil>} 133703676Ki BinarySI},memory: {{17179398144 0} {<nil>} 16776756Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{123221307598 0} {<nil>} 123221307598 DecimalSI},memory: {{17074540544 0} {<nil>} 16674356Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-18 06:23:19 +0000 UTC,LastTransitionTime:2022-11-18 06:17:12 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 06:23:19 +0000 UTC,LastTransitionTime:2022-11-18 06:17:12 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 06:23:19 +0000 UTC,LastTransitionTime:2022-11-18 06:17:12 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 06:23:19 +0000 UTC,LastTransitionTime:2022-11-18 06:17:38 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-qtb4d,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-qtb4d,SystemUUID:AD6FE40B-613C-457A-ABF6-248D4E7DFDCA,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.30+fbd3976770c82f-dirty,KubeProxyVersion:v1.27.0-alpha.0.30+fbd3976770c82f-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 18 06:28:17.674: INFO: 
Logging kubelet events for node capz-conf-qtb4d
Nov 18 06:28:17.788: INFO: 
Logging pods the kubelet thinks is on node capz-conf-qtb4d
Nov 18 06:28:17.918: INFO: containerd-logger-b5j6l started at 2022-11-18 06:17:13 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:17.918: INFO: 	Container containerd-logger ready: true, restart count 0
Nov 18 06:28:17.918: INFO: kube-proxy-windows-8b9zj started at 2022-11-18 06:17:13 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:17.918: INFO: 	Container kube-proxy ready: true, restart count 0
Nov 18 06:28:17.918: INFO: calico-node-windows-p5j6m started at 2022-11-18 06:17:13 +0000 UTC (1+2 container statuses recorded)
Nov 18 06:28:17.918: INFO: 	Init container install-cni ready: true, restart count 0
Nov 18 06:28:17.918: INFO: 	Container calico-node-felix ready: true, restart count 1
Nov 18 06:28:17.918: INFO: 	Container calico-node-startup ready: true, restart count 0
Nov 18 06:28:17.918: INFO: csi-proxy-tffx7 started at 2022-11-18 06:17:38 +0000 UTC (0+1 container statuses recorded)
Nov 18 06:28:17.918: INFO: 	Container csi-proxy ready: true, restart count 0
Nov 18 06:28:18.341: INFO: 
Latency metrics for node capz-conf-qtb4d
Nov 18 06:28:18.480: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 18 06:28:18.818: INFO: Failed to get logs of pod kube-apiserver-capz-conf-53k332-control-plane-zkfrt, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-53k332-control-plane-zkfrt)
Nov 18 06:28:18.818: INFO: Logs of kube-system/kube-apiserver-capz-conf-53k332-control-plane-zkfrt:kube-apiserver on node capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:18.818: INFO:  : STARTLOG

ENDLOG for container kube-system:kube-apiserver-capz-conf-53k332-control-plane-zkfrt:kube-apiserver
Nov 18 06:28:19.217: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-53k332-control-plane-zkfrt, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-53k332-control-plane-zkfrt)
Nov 18 06:28:19.218: INFO: Logs of kube-system/kube-controller-manager-capz-conf-53k332-control-plane-zkfrt:kube-controller-manager on node capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:19.218: INFO:  : STARTLOG

ENDLOG for container kube-system:kube-controller-manager-capz-conf-53k332-control-plane-zkfrt:kube-controller-manager
Nov 18 06:28:19.617: INFO: Failed to get logs of pod kube-scheduler-capz-conf-53k332-control-plane-zkfrt, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-53k332-control-plane-zkfrt)
Nov 18 06:28:19.617: INFO: Logs of kube-system/kube-scheduler-capz-conf-53k332-control-plane-zkfrt:kube-scheduler on node capz-conf-53k332-control-plane-zkfrt
Nov 18 06:28:19.617: INFO:  : STARTLOG

ENDLOG for container kube-system:kube-scheduler-capz-conf-53k332-control-plane-zkfrt:kube-scheduler
Nov 18 06:28:19.618: FAIL: Error waiting for all pods to be running and ready: 3 / 18 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s
POD                                                          NODE                                 PHASE   GRACE CONDITIONS
kube-apiserver-capz-conf-53k332-control-plane-zkfrt          capz-conf-53k332-control-plane-zkfrt Pending       []
kube-controller-manager-capz-conf-53k332-control-plane-zkfrt capz-conf-53k332-control-plane-zkfrt Pending       []
kube-scheduler-capz-conf-53k332-control-plane-zkfrt          capz-conf-53k332-control-plane-zkfrt Pending       []


Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite()
	test/e2e/e2e.go:249 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
	test/e2e/e2e.go:81 +0x8f
reflect.Value.call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0x75b6e72, 0x4}, {0xc0000b9f20, 0x0, 0x0?})
	/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0xc0000b9f20?, 0x0?, 0x0?})
	/usr/local/go/src/reflect/value.go:368 +0xbc

				Click to see stdout/stderrfrom junit.kubetest.01.xml

Filter through log files | View test history on testgrid

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'

test/e2e/e2e.go:77

				from junit.kubetest.01.xml

Filter through log files | View test history on testgrid

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'

test/e2e/e2e.go:77

				from junit.kubetest.01.xml

Filter through log files | View test history on testgrid

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'

test/e2e/e2e.go:77

				from junit.kubetest.01.xml

Filter through log files | View test history on testgrid

PR	princepereira: Windows Kube-Proxy implementation of ProxyTerminatingEndpoints feature
Result	SUCCESS
Tests	4 failed / 6 succeeded
Started	2022-11-18 05:35
Elapsed	1h6m
Revision	a48cd77756e800a5f0abb35bc5b1c06637822bae
Refs	113776

PR #113776 pull-kubernetes-e2e-capz-windows-containerd #1593477341437235200

Test Failures

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

Passed

Skipped