pull-kubernetes-e2e-capz-windows-containerd #1595036308873416704 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}, {0xc0000b8f20, 0x0, 0x0?})
	/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0xc0000b8f20?, 0x0?, 0x0?})
	/usr/local/go/src/reflect/value.go:368 +0xbc
				[SynchronizedBeforeSuite] TOP-LEVEL
  test/e2e/e2e.go:77
Nov 22 13:34:32.533: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 22 13:34:32.536: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 22 13:34:32.738: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 22 13:34:32.913: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:32.913: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:32.913: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:32.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 22 13:34:32.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:32.913: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:32.913: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:32.913: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:32.913: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:32.913: INFO: 
Nov 22 13:34:35.044: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:35.044: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:35.044: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:35.044: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 22 13:34:35.044: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:35.044: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:35.044: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:35.044: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:35.044: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:35.044: INFO: 
Nov 22 13:34:37.043: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:37.043: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:37.043: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:37.043: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 22 13:34:37.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:37.043: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:37.043: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:37.043: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:37.043: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:37.043: INFO: 
Nov 22 13:34:39.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:39.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:39.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:39.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 22 13:34:39.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:39.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:39.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:39.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:39.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:39.041: INFO: 
Nov 22 13:34:41.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:41.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:41.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:41.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 22 13:34:41.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:41.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:41.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:41.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:41.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:41.040: INFO: 
Nov 22 13:34:43.039: INFO: The status of Pod calico-node-windows-vwdqr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:43.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:43.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:43.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:43.039: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 22 13:34:43.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:43.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:43.039: INFO: calico-node-windows-vwdqr                                     capz-conf-pf2j7                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:56 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:42 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:42 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:27 +0000 UTC  }]
Nov 22 13:34:43.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:43.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:43.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:43.039: INFO: 
Nov 22 13:34:45.052: INFO: The status of Pod calico-node-windows-vwdqr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:45.052: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:45.052: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:45.052: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:45.052: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 22 13:34:45.052: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:45.052: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:45.052: INFO: calico-node-windows-vwdqr                                     capz-conf-pf2j7                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:56 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:42 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:42 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:27 +0000 UTC  }]
Nov 22 13:34:45.052: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:45.052: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:45.052: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:45.052: INFO: 
Nov 22 13:34:47.040: INFO: The status of Pod calico-node-windows-vwdqr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:47.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:47.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:47.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:47.040: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 22 13:34:47.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:47.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:47.040: INFO: calico-node-windows-vwdqr                                     capz-conf-pf2j7                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:56 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:42 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:42 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:27 +0000 UTC  }]
Nov 22 13:34:47.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:47.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:47.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:47.040: INFO: 
Nov 22 13:34:49.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:49.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:49.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:49.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 22 13:34:49.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:49.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:49.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:49.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:49.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:49.037: INFO: 
Nov 22 13:34:51.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:51.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:51.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:51.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 22 13:34:51.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:51.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:51.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:51.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:51.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:51.034: INFO: 
Nov 22 13:34:53.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:53.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:53.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:53.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 22 13:34:53.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:53.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:53.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:53.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:53.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:53.034: INFO: 
Nov 22 13:34:55.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:55.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:55.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:55.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 22 13:34:55.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:55.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:55.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:55.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:55.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:55.035: INFO: 
Nov 22 13:34:57.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:57.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:57.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:57.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 22 13:34:57.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:57.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:57.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:57.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:57.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:57.036: INFO: 
Nov 22 13:34:59.042: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:59.042: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:59.042: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:34:59.042: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 22 13:34:59.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:34:59.042: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:34:59.042: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:59.042: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:59.042: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:34:59.042: INFO: 
Nov 22 13:35:01.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:01.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:01.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:01.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 22 13:35:01.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:01.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:01.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:01.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:01.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:01.034: INFO: 
Nov 22 13:35:03.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:03.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:03.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:03.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 22 13:35:03.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:03.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:03.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:03.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:03.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:03.037: INFO: 
Nov 22 13:35:05.047: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:05.047: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:05.047: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:05.047: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 22 13:35:05.047: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:05.047: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:05.047: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:05.047: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:05.047: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:05.047: INFO: 
Nov 22 13:35:07.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:07.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:07.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:07.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 22 13:35:07.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:07.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:07.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:07.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:07.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:07.035: INFO: 
Nov 22 13:35:09.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:09.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:09.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:09.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 22 13:35:09.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:09.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:09.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:09.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:09.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:09.036: INFO: 
Nov 22 13:35:11.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:11.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:11.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:11.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 22 13:35:11.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:11.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:11.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:11.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:11.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:11.034: INFO: 
Nov 22 13:35:13.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:13.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:13.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:13.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 22 13:35:13.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:13.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:13.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:13.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:13.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:13.034: INFO: 
Nov 22 13:35:15.064: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:15.064: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:15.064: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:15.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 22 13:35:15.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:15.064: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:15.064: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:15.064: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:15.064: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:15.064: INFO: 
Nov 22 13:35:17.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:17.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:17.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:17.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 22 13:35:17.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:17.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:17.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:17.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:17.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:17.033: INFO: 
Nov 22 13:35:19.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:19.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:19.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:19.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 22 13:35:19.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:19.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:19.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:19.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:19.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:19.035: INFO: 
Nov 22 13:35:21.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:21.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:21.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:21.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 22 13:35:21.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:21.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:21.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:21.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:21.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:21.035: INFO: 
Nov 22 13:35:23.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:23.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:23.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:23.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 22 13:35:23.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:23.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:23.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:23.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:23.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:23.034: INFO: 
Nov 22 13:35:25.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:25.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:25.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:25.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 22 13:35:25.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:25.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:25.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:25.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:25.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:25.037: INFO: 
Nov 22 13:35:27.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:27.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:27.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:27.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 22 13:35:27.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:27.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:27.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:27.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:27.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:27.037: INFO: 
Nov 22 13:35:29.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:29.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:29.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:29.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 22 13:35:29.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:29.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:29.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:29.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:29.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:29.033: INFO: 
Nov 22 13:35:31.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:31.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:31.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:31.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 22 13:35:31.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:31.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:31.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:31.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:31.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:31.033: INFO: 
Nov 22 13:35:33.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:33.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:33.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:33.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 22 13:35:33.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:33.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:33.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:33.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:33.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:33.034: INFO: 
Nov 22 13:35:35.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:35.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:35.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:35.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 22 13:35:35.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:35.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:35.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:35.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:35.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:35.036: INFO: 
Nov 22 13:35:37.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:37.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:37.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:37.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 22 13:35:37.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:37.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:37.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:37.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:37.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:37.036: INFO: 
Nov 22 13:35:39.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:39.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:39.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:39.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 22 13:35:39.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:39.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:39.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:39.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:39.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:39.034: INFO: 
Nov 22 13:35:41.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:41.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:41.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:41.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 22 13:35:41.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:41.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:41.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:41.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:41.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:41.034: INFO: 
Nov 22 13:35:43.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:43.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:43.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:43.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 22 13:35:43.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:43.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:43.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:43.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:43.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:43.033: INFO: 
Nov 22 13:35:45.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:45.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:45.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:45.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 22 13:35:45.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:45.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:45.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:45.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:45.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:45.041: INFO: 
Nov 22 13:35:47.046: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:47.046: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:47.046: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:47.046: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 22 13:35:47.046: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:47.046: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:47.046: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:47.046: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:47.046: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:47.046: INFO: 
Nov 22 13:35:49.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:49.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:49.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:49.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 22 13:35:49.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:49.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:49.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:49.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:49.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:49.033: INFO: 
Nov 22 13:35:51.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:51.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:51.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:51.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 22 13:35:51.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:51.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:51.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:51.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:51.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:51.033: INFO: 
Nov 22 13:35:53.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:53.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:53.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:53.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 22 13:35:53.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:53.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:53.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:53.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:53.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:53.035: INFO: 
Nov 22 13:35:55.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:55.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:55.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:55.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 22 13:35:55.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:55.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:55.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:55.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:55.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:55.038: INFO: 
Nov 22 13:35:57.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:57.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:57.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:57.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 22 13:35:57.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:57.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:57.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:57.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:57.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:57.034: INFO: 
Nov 22 13:35:59.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:59.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:59.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:35:59.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 22 13:35:59.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:35:59.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:35:59.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:59.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:59.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:35:59.035: INFO: 
Nov 22 13:36:01.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:01.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:01.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:01.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 22 13:36:01.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:01.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:01.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:01.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:01.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:01.035: INFO: 
Nov 22 13:36:03.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:03.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:03.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:03.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 22 13:36:03.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:03.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:03.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:03.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:03.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:03.035: INFO: 
Nov 22 13:36:05.042: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:05.042: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:05.042: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:05.042: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 22 13:36:05.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:05.042: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:05.042: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:05.042: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:05.042: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:05.042: INFO: 
Nov 22 13:36:07.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:07.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:07.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:07.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 22 13:36:07.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:07.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:07.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:07.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:07.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:07.034: INFO: 
Nov 22 13:36:09.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:09.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:09.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:09.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 22 13:36:09.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:09.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:09.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:09.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:09.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:09.034: INFO: 
Nov 22 13:36:11.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:11.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:11.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:11.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 22 13:36:11.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:11.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:11.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:11.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:11.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:11.040: INFO: 
Nov 22 13:36:13.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:13.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:13.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:13.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 22 13:36:13.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:13.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:13.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:13.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:13.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:13.033: INFO: 
Nov 22 13:36:15.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:15.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:15.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:15.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 22 13:36:15.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:15.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:15.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:15.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:15.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:15.039: INFO: 
Nov 22 13:36:17.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:17.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:17.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:17.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 22 13:36:17.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:17.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:17.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:17.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:17.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:17.037: INFO: 
Nov 22 13:36:19.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:19.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:19.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:19.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 22 13:36:19.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:19.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:19.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:19.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:19.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:19.041: INFO: 
Nov 22 13:36:21.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:21.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:21.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:21.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 22 13:36:21.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:21.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:21.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:21.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:21.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:21.033: INFO: 
Nov 22 13:36:23.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:23.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:23.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:23.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 22 13:36:23.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:23.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:23.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:23.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:23.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:23.034: INFO: 
Nov 22 13:36:25.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:25.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:25.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:25.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 22 13:36:25.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:25.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:25.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:25.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:25.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:25.037: INFO: 
Nov 22 13:36:27.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:27.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:27.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:27.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 22 13:36:27.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:27.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:27.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:27.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:27.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:27.035: INFO: 
Nov 22 13:36:29.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:29.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:29.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:29.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 22 13:36:29.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:29.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:29.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:29.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:29.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:29.034: INFO: 
Nov 22 13:36:31.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:31.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:31.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:31.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 22 13:36:31.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:31.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:31.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:31.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:31.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:31.034: INFO: 
Nov 22 13:36:33.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:33.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:33.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:33.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 22 13:36:33.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:33.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:33.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:33.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:33.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:33.033: INFO: 
Nov 22 13:36:35.043: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:35.043: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:35.043: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:35.043: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 22 13:36:35.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:35.043: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:35.043: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:35.043: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:35.043: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:35.043: INFO: 
Nov 22 13:36:37.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:37.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:37.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:37.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 22 13:36:37.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:37.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:37.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:37.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:37.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:37.036: INFO: 
Nov 22 13:36:39.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:39.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:39.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:39.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 22 13:36:39.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:39.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:39.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:39.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:39.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:39.033: INFO: 
Nov 22 13:36:41.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:41.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:41.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:41.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 22 13:36:41.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:41.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:41.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:41.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:41.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:41.033: INFO: 
Nov 22 13:36:43.032: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:43.032: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:43.032: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:43.032: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 22 13:36:43.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:43.032: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:43.032: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:43.032: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:43.032: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:43.032: INFO: 
Nov 22 13:36:45.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:45.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:45.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:45.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 22 13:36:45.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:45.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:45.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:45.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:45.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:45.039: INFO: 
Nov 22 13:36:47.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:47.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:47.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:47.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 22 13:36:47.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:47.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:47.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:47.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:47.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:47.034: INFO: 
Nov 22 13:36:49.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:49.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:49.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:49.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 22 13:36:49.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:49.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:49.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:49.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:49.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:49.034: INFO: 
Nov 22 13:36:51.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:51.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:51.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:51.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 22 13:36:51.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:51.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:51.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:51.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:51.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:51.034: INFO: 
Nov 22 13:36:53.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:53.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:53.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:53.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 22 13:36:53.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:53.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:53.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:53.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:53.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:53.034: INFO: 
Nov 22 13:36:55.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:55.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:55.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:55.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 22 13:36:55.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:55.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:55.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:55.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:55.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:55.036: INFO: 
Nov 22 13:36:57.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:57.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:57.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:57.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 22 13:36:57.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:57.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:57.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:57.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:57.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:57.033: INFO: 
Nov 22 13:36:59.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:59.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:59.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:36:59.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 22 13:36:59.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:36:59.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:36:59.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:59.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:59.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:36:59.036: INFO: 
Nov 22 13:37:01.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:01.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:01.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:01.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 22 13:37:01.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:01.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:01.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:01.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:01.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:01.037: INFO: 
Nov 22 13:37:03.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:03.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:03.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:03.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 22 13:37:03.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:03.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:03.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:03.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:03.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:03.036: INFO: 
Nov 22 13:37:05.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:05.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:05.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:05.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 22 13:37:05.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:05.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:05.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:05.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:05.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:05.040: INFO: 
Nov 22 13:37:07.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:07.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:07.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:07.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 22 13:37:07.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:07.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:07.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:07.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:07.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:07.036: INFO: 
Nov 22 13:37:09.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:09.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:09.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:09.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 22 13:37:09.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:09.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:09.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:09.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:09.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:09.035: INFO: 
Nov 22 13:37:11.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:11.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:11.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:11.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 22 13:37:11.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:11.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:11.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:11.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:11.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:11.036: INFO: 
Nov 22 13:37:13.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:13.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:13.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:13.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 22 13:37:13.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:13.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:13.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:13.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:13.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:13.036: INFO: 
Nov 22 13:37:15.049: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:15.049: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:15.049: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:15.049: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 22 13:37:15.049: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:15.049: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:15.049: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:15.049: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:15.049: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:15.049: INFO: 
Nov 22 13:37:17.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:17.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:17.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:17.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 22 13:37:17.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:17.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:17.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:17.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:17.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:17.034: INFO: 
Nov 22 13:37:19.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:19.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:19.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:19.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 22 13:37:19.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:19.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:19.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:19.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:19.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:19.034: INFO: 
Nov 22 13:37:21.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:21.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:21.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:21.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 22 13:37:21.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:21.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:21.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:21.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:21.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:21.034: INFO: 
Nov 22 13:37:23.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:23.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:23.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:23.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 22 13:37:23.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:23.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:23.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:23.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:23.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:23.034: INFO: 
Nov 22 13:37:25.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:25.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:25.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:25.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 22 13:37:25.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:25.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:25.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:25.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:25.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:25.035: INFO: 
Nov 22 13:37:27.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:27.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:27.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:27.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 22 13:37:27.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:27.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:27.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:27.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:27.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:27.041: INFO: 
Nov 22 13:37:29.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:29.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:29.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:29.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 22 13:37:29.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:29.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:29.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:29.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:29.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:29.035: INFO: 
Nov 22 13:37:31.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:31.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:31.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:31.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 22 13:37:31.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:31.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:31.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:31.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:31.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:31.033: INFO: 
Nov 22 13:37:33.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:33.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:33.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:33.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 22 13:37:33.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:33.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:33.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:33.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:33.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:33.036: INFO: 
Nov 22 13:37:35.046: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:35.046: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:35.046: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:35.046: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 22 13:37:35.046: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:35.046: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:35.046: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:35.046: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:35.046: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:35.046: INFO: 
Nov 22 13:37:37.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:37.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:37.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:37.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 22 13:37:37.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:37.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:37.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:37.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:37.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:37.037: INFO: 
Nov 22 13:37:39.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:39.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:39.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:39.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 22 13:37:39.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:39.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:39.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:39.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:39.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:39.036: INFO: 
Nov 22 13:37:41.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:41.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:41.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:41.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 22 13:37:41.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:41.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:41.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:41.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:41.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:41.033: INFO: 
Nov 22 13:37:43.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:43.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:43.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:43.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 22 13:37:43.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:43.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:43.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:43.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:43.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:43.033: INFO: 
Nov 22 13:37:45.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:45.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:45.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:45.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 22 13:37:45.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:45.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:45.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:45.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:45.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:45.039: INFO: 
Nov 22 13:37:47.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:47.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:47.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:47.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 22 13:37:47.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:47.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:47.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:47.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:47.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:47.034: INFO: 
Nov 22 13:37:49.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:49.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:49.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:49.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 22 13:37:49.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:49.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:49.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:49.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:49.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:49.034: INFO: 
Nov 22 13:37:51.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:51.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:51.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:51.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 22 13:37:51.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:51.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:51.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:51.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:51.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:51.034: INFO: 
Nov 22 13:37:53.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:53.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:53.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:53.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 22 13:37:53.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:53.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:53.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:53.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:53.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:53.038: INFO: 
Nov 22 13:37:55.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:55.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:55.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:55.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 22 13:37:55.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:55.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:55.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:55.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:55.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:55.035: INFO: 
Nov 22 13:37:57.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:57.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:57.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:57.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 22 13:37:57.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:57.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:57.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:57.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:57.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:57.036: INFO: 
Nov 22 13:37:59.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:59.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:59.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:37:59.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 22 13:37:59.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:37:59.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:37:59.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:59.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:59.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:37:59.034: INFO: 
Nov 22 13:38:01.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:01.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:01.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:01.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 22 13:38:01.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:01.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:01.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:01.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:01.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:01.036: INFO: 
Nov 22 13:38:03.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:03.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:03.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:03.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 22 13:38:03.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:03.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:03.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:03.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:03.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:03.039: INFO: 
Nov 22 13:38:05.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:05.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:05.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:05.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 22 13:38:05.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:05.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:05.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:05.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:05.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:05.041: INFO: 
Nov 22 13:38:07.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:07.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:07.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:07.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 22 13:38:07.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:07.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:07.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:07.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:07.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:07.037: INFO: 
Nov 22 13:38:09.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:09.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:09.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:09.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 22 13:38:09.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:09.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:09.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:09.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:09.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:09.034: INFO: 
Nov 22 13:38:11.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:11.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:11.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:11.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 22 13:38:11.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:11.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:11.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:11.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:11.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:11.036: INFO: 
Nov 22 13:38:13.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:13.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:13.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:13.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 22 13:38:13.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:13.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:13.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:13.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:13.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:13.036: INFO: 
Nov 22 13:38:15.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:15.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:15.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:15.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 22 13:38:15.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:15.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:15.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:15.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:15.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:15.035: INFO: 
Nov 22 13:38:17.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:17.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:17.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:17.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 22 13:38:17.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:17.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:17.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:17.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:17.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:17.036: INFO: 
Nov 22 13:38:19.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:19.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:19.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:19.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 22 13:38:19.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:19.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:19.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:19.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:19.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:19.037: INFO: 
Nov 22 13:38:21.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:21.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:21.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:21.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 22 13:38:21.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:21.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:21.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:21.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:21.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:21.034: INFO: 
Nov 22 13:38:23.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:23.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:23.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:23.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 22 13:38:23.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:23.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:23.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:23.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:23.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:23.036: INFO: 
Nov 22 13:38:25.059: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:25.059: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:25.059: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:25.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 22 13:38:25.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:25.059: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:25.059: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:25.059: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:25.059: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:25.059: INFO: 
Nov 22 13:38:27.043: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:27.043: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:27.043: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:27.043: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 22 13:38:27.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:27.043: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:27.043: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:27.043: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:27.043: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:27.043: INFO: 
Nov 22 13:38:29.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:29.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:29.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:29.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 22 13:38:29.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:29.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:29.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:29.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:29.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:29.038: INFO: 
Nov 22 13:38:31.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:31.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:31.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:31.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 22 13:38:31.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:31.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:31.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:31.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:31.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:31.036: INFO: 
Nov 22 13:38:33.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:33.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:33.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:33.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 22 13:38:33.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:33.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:33.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:33.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:33.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:33.034: INFO: 
Nov 22 13:38:35.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:35.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:35.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:35.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 22 13:38:35.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:35.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:35.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:35.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:35.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:35.041: INFO: 
Nov 22 13:38:37.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:37.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:37.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:37.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 22 13:38:37.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:37.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:37.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:37.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:37.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:37.038: INFO: 
Nov 22 13:38:39.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:39.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:39.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:39.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 22 13:38:39.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:39.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:39.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:39.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:39.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:39.034: INFO: 
Nov 22 13:38:41.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:41.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:41.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:41.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 22 13:38:41.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:41.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:41.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:41.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:41.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:41.034: INFO: 
Nov 22 13:38:43.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:43.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:43.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:43.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 22 13:38:43.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:43.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:43.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:43.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:43.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:43.034: INFO: 
Nov 22 13:38:45.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:45.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:45.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:45.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 22 13:38:45.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:45.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:45.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:45.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:45.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:45.040: INFO: 
Nov 22 13:38:47.046: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:47.046: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:47.046: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:47.046: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 22 13:38:47.046: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:47.046: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:47.046: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:47.046: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:47.046: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:47.046: INFO: 
Nov 22 13:38:49.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:49.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:49.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:49.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 22 13:38:49.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:49.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:49.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:49.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:49.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:49.034: INFO: 
Nov 22 13:38:51.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:51.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:51.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:51.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 22 13:38:51.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:51.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:51.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:51.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:51.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:51.034: INFO: 
Nov 22 13:38:53.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:53.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:53.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:53.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 22 13:38:53.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:53.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:53.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:53.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:53.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:53.036: INFO: 
Nov 22 13:38:55.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:55.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:55.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:55.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 22 13:38:55.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:55.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:55.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:55.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:55.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:55.039: INFO: 
Nov 22 13:38:57.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:57.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:57.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:57.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 22 13:38:57.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:57.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:57.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:57.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:57.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:57.033: INFO: 
Nov 22 13:38:59.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:59.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:59.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:38:59.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 22 13:38:59.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:38:59.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:38:59.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:59.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:59.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:38:59.035: INFO: 
Nov 22 13:39:01.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:01.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:01.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:01.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 22 13:39:01.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:01.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:01.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:01.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:01.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:01.035: INFO: 
Nov 22 13:39:03.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:03.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:03.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:03.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 22 13:39:03.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:03.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:03.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:03.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:03.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:03.035: INFO: 
Nov 22 13:39:05.042: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:05.042: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:05.042: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:05.042: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 22 13:39:05.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:05.042: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:05.042: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:05.042: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:05.042: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:05.042: INFO: 
Nov 22 13:39:07.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:07.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:07.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:07.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 22 13:39:07.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:07.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:07.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:07.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:07.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:07.036: INFO: 
Nov 22 13:39:09.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:09.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:09.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:09.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 22 13:39:09.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:09.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:09.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:09.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:09.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:09.033: INFO: 
Nov 22 13:39:11.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:11.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:11.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:11.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 22 13:39:11.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:11.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:11.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:11.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:11.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:11.035: INFO: 
Nov 22 13:39:13.143: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:13.143: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:13.143: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:13.143: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 22 13:39:13.143: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:13.143: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:13.143: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:13.143: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:13.143: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:13.143: INFO: 
Nov 22 13:39:15.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:15.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:15.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:15.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 22 13:39:15.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:15.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:15.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:15.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:15.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:15.039: INFO: 
Nov 22 13:39:17.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:17.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:17.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:17.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 22 13:39:17.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:17.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:17.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:17.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:17.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:17.034: INFO: 
Nov 22 13:39:19.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:19.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:19.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:19.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 22 13:39:19.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:19.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:19.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:19.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:19.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:19.035: INFO: 
Nov 22 13:39:21.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:21.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:21.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:21.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 22 13:39:21.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:21.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:21.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:21.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:21.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:21.036: INFO: 
Nov 22 13:39:23.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:23.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:23.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:23.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 22 13:39:23.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:23.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:23.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:23.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:23.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:23.034: INFO: 
Nov 22 13:39:25.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:25.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:25.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:25.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 22 13:39:25.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:25.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:25.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:25.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:25.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:25.038: INFO: 
Nov 22 13:39:27.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:27.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:27.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:27.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 22 13:39:27.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:27.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:27.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:27.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:27.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:27.037: INFO: 
Nov 22 13:39:29.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:29.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:29.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:29.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 22 13:39:29.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:29.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:29.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:29.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:29.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:29.035: INFO: 
Nov 22 13:39:31.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:31.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:31.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:31.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 22 13:39:31.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:31.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:31.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:31.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:31.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:31.035: INFO: 
Nov 22 13:39:33.148: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:33.148: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:33.148: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:33.148: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 22 13:39:33.148: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:33.148: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:33.148: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:33.148: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:33.148: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:33.148: INFO: 
Nov 22 13:39:35.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:35.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:35.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:35.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 22 13:39:35.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:35.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:35.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:35.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:35.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:35.040: INFO: 
Nov 22 13:39:37.042: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:37.042: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:37.042: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:37.042: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 22 13:39:37.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:37.042: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:37.042: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:37.042: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:37.042: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:37.042: INFO: 
Nov 22 13:39:39.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:39.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:39.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:39.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 22 13:39:39.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:39.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:39.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:39.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:39.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:39.034: INFO: 
Nov 22 13:39:41.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:41.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:41.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:41.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 22 13:39:41.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:41.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:41.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:41.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:41.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:41.035: INFO: 
Nov 22 13:39:43.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:43.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:43.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:43.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 22 13:39:43.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:43.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:43.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:43.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:43.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:43.035: INFO: 
Nov 22 13:39:45.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:45.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:45.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:45.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 22 13:39:45.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:45.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:45.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:45.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:45.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:45.041: INFO: 
Nov 22 13:39:47.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:47.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:47.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:47.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 22 13:39:47.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:47.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:47.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:47.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:47.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:47.035: INFO: 
Nov 22 13:39:49.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:49.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:49.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:49.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 22 13:39:49.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:49.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:49.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:49.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:49.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:49.034: INFO: 
Nov 22 13:39:51.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:51.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:51.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:51.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 22 13:39:51.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:51.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:51.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:51.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:51.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:51.036: INFO: 
Nov 22 13:39:53.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:53.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:53.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:53.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 22 13:39:53.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:53.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:53.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:53.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:53.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:53.034: INFO: 
Nov 22 13:39:55.149: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:55.149: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:55.149: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:55.149: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 22 13:39:55.149: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:55.149: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:55.149: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:55.149: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:55.149: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:55.149: INFO: 
Nov 22 13:39:57.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:57.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:57.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:57.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 22 13:39:57.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:57.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:57.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:57.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:57.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:57.035: INFO: 
Nov 22 13:39:59.044: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:59.044: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:59.044: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:39:59.044: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 22 13:39:59.044: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:39:59.044: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:39:59.044: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:59.044: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:59.044: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:39:59.044: INFO: 
Nov 22 13:40:01.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:01.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:01.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:01.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 22 13:40:01.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:01.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:01.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:01.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:01.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:01.034: INFO: 
Nov 22 13:40:03.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:03.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:03.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:03.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 22 13:40:03.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:03.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:03.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:03.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:03.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:03.036: INFO: 
Nov 22 13:40:05.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:05.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:05.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:05.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 22 13:40:05.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:05.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:05.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:05.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:05.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:05.036: INFO: 
Nov 22 13:40:07.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:07.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:07.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:07.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 22 13:40:07.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:07.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:07.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:07.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:07.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:07.038: INFO: 
Nov 22 13:40:09.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:09.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:09.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:09.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 22 13:40:09.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:09.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:09.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:09.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:09.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:09.034: INFO: 
Nov 22 13:40:11.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:11.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:11.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:11.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 22 13:40:11.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:11.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:11.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:11.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:11.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:11.035: INFO: 
Nov 22 13:40:13.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:13.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:13.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:13.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 22 13:40:13.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:13.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:13.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:13.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:13.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:13.034: INFO: 
Nov 22 13:40:15.048: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:15.048: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:15.048: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:15.048: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 22 13:40:15.048: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:15.048: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:15.048: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:15.048: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:15.048: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:15.048: INFO: 
Nov 22 13:40:17.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:17.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:17.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:17.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 22 13:40:17.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:17.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:17.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:17.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:17.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:17.037: INFO: 
Nov 22 13:40:19.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:19.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:19.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:19.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 22 13:40:19.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:19.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:19.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:19.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:19.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:19.034: INFO: 
Nov 22 13:40:21.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:21.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:21.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:21.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 22 13:40:21.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:21.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:21.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:21.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:21.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:21.035: INFO: 
Nov 22 13:40:23.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:23.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:23.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:23.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 22 13:40:23.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:23.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:23.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:23.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:23.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:23.036: INFO: 
Nov 22 13:40:25.047: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:25.047: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:25.047: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:25.047: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 22 13:40:25.047: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:25.047: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:25.047: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:25.047: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:25.047: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:25.047: INFO: 
Nov 22 13:40:27.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:27.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:27.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:27.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 22 13:40:27.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:27.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:27.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:27.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:27.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:27.035: INFO: 
Nov 22 13:40:29.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:29.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:29.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:29.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 22 13:40:29.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:29.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:29.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:29.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:29.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:29.034: INFO: 
Nov 22 13:40:31.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:31.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:31.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:31.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 22 13:40:31.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:31.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:31.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:31.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:31.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:31.038: INFO: 
Nov 22 13:40:33.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:33.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:33.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:33.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 22 13:40:33.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:33.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:33.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:33.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:33.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:33.035: INFO: 
Nov 22 13:40:35.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:35.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:35.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:35.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 22 13:40:35.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:35.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:35.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:35.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:35.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:35.040: INFO: 
Nov 22 13:40:37.043: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:37.043: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:37.043: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:37.043: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 22 13:40:37.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:37.043: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:37.043: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:37.043: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:37.043: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:37.043: INFO: 
Nov 22 13:40:39.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:39.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:39.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:39.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 22 13:40:39.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:39.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:39.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:39.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:39.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:39.035: INFO: 
Nov 22 13:40:41.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:41.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:41.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:41.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 22 13:40:41.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:41.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:41.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:41.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:41.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:41.035: INFO: 
Nov 22 13:40:43.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:43.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:43.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:43.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 22 13:40:43.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:43.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:43.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:43.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:43.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:43.036: INFO: 
Nov 22 13:40:45.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:45.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:45.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:45.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 22 13:40:45.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:45.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:45.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:45.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:45.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:45.035: INFO: 
Nov 22 13:40:47.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:47.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:47.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:47.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 22 13:40:47.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:47.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:47.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:47.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:47.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:47.035: INFO: 
Nov 22 13:40:49.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:49.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:49.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:49.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 22 13:40:49.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:49.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:49.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:49.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:49.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:49.034: INFO: 
Nov 22 13:40:51.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:51.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:51.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:51.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 22 13:40:51.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:51.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:51.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:51.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:51.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:51.037: INFO: 
Nov 22 13:40:53.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:53.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:53.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:53.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 22 13:40:53.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:53.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:53.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:53.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:53.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:53.034: INFO: 
Nov 22 13:40:55.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:55.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:55.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:55.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 22 13:40:55.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:55.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:55.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:55.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:55.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:55.035: INFO: 
Nov 22 13:40:57.045: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:57.045: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:57.045: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:57.045: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 22 13:40:57.045: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:57.045: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:57.045: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:57.045: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:57.045: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:57.045: INFO: 
Nov 22 13:40:59.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:59.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:59.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:40:59.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 22 13:40:59.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:40:59.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:40:59.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:59.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:59.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:40:59.037: INFO: 
Nov 22 13:41:01.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:01.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:01.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:01.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 22 13:41:01.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:01.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:01.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:01.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:01.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:01.034: INFO: 
Nov 22 13:41:03.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:03.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:03.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:03.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 22 13:41:03.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:03.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:03.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:03.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:03.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:03.035: INFO: 
Nov 22 13:41:05.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:05.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:05.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:05.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 22 13:41:05.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:05.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:05.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:05.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:05.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:05.036: INFO: 
Nov 22 13:41:07.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:07.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:07.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:07.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 22 13:41:07.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:07.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:07.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:07.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:07.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:07.035: INFO: 
Nov 22 13:41:09.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:09.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:09.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:09.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 22 13:41:09.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:09.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:09.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:09.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:09.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:09.036: INFO: 
Nov 22 13:41:11.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:11.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:11.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:11.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 22 13:41:11.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:11.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:11.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:11.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:11.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:11.034: INFO: 
Nov 22 13:41:13.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:13.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:13.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:13.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 22 13:41:13.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:13.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:13.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:13.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:13.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:13.035: INFO: 
Nov 22 13:41:15.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:15.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:15.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:15.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 22 13:41:15.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:15.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:15.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:15.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:15.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:15.037: INFO: 
Nov 22 13:41:17.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:17.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:17.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:17.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 22 13:41:17.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:17.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:17.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:17.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:17.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:17.038: INFO: 
Nov 22 13:41:19.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:19.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:19.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:19.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 22 13:41:19.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:19.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:19.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:19.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:19.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:19.034: INFO: 
Nov 22 13:41:21.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:21.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:21.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:21.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 22 13:41:21.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:21.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:21.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:21.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:21.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:21.039: INFO: 
Nov 22 13:41:23.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:23.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:23.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:23.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 22 13:41:23.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:23.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:23.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:23.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:23.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:23.035: INFO: 
Nov 22 13:41:25.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:25.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:25.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:25.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 22 13:41:25.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:25.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:25.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:25.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:25.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:25.036: INFO: 
Nov 22 13:41:27.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:27.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:27.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:27.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 22 13:41:27.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:27.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:27.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:27.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:27.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:27.034: INFO: 
Nov 22 13:41:29.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:29.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:29.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:29.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 22 13:41:29.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:29.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:29.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:29.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:29.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:29.035: INFO: 
Nov 22 13:41:31.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:31.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:31.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:31.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 22 13:41:31.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:31.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:31.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:31.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:31.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:31.034: INFO: 
Nov 22 13:41:33.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:33.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:33.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:33.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 22 13:41:33.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:33.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:33.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:33.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:33.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:33.034: INFO: 
Nov 22 13:41:35.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:35.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:35.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:35.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 22 13:41:35.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:35.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:35.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:35.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:35.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:35.036: INFO: 
Nov 22 13:41:37.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:37.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:37.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:37.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 22 13:41:37.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:37.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:37.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:37.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:37.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:37.037: INFO: 
Nov 22 13:41:39.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:39.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:39.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:39.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 22 13:41:39.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:39.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:39.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:39.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:39.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:39.035: INFO: 
Nov 22 13:41:41.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:41.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:41.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:41.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 22 13:41:41.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:41.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:41.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:41.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:41.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:41.036: INFO: 
Nov 22 13:41:43.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:43.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:43.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:43.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 22 13:41:43.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:43.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:43.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:43.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:43.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:43.035: INFO: 
Nov 22 13:41:45.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:45.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:45.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:45.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 22 13:41:45.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:45.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:45.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:45.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:45.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:45.036: INFO: 
Nov 22 13:41:47.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:47.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:47.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:47.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 22 13:41:47.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:47.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:47.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:47.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:47.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:47.035: INFO: 
Nov 22 13:41:49.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:49.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:49.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:49.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 22 13:41:49.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:49.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:49.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:49.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:49.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:49.035: INFO: 
Nov 22 13:41:51.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:51.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:51.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:51.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 22 13:41:51.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:51.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:51.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:51.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:51.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:51.034: INFO: 
Nov 22 13:41:53.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:53.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:53.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:53.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 22 13:41:53.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:53.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:53.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:53.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:53.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:53.034: INFO: 
Nov 22 13:41:55.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:55.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:55.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:55.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 22 13:41:55.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:55.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:55.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:55.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:55.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:55.041: INFO: 
Nov 22 13:41:57.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:57.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:57.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:57.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 22 13:41:57.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:57.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:57.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:57.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:57.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:57.035: INFO: 
Nov 22 13:41:59.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:59.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:59.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:41:59.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 22 13:41:59.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:41:59.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:41:59.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:59.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:59.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:41:59.033: INFO: 
Nov 22 13:42:01.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:01.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:01.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:01.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 22 13:42:01.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:01.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:01.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:01.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:01.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:01.034: INFO: 
Nov 22 13:42:03.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:03.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:03.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:03.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 22 13:42:03.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:03.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:03.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:03.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:03.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:03.034: INFO: 
Nov 22 13:42:05.043: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:05.043: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:05.043: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:05.043: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 22 13:42:05.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:05.043: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:05.043: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:05.043: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:05.043: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:05.043: INFO: 
Nov 22 13:42:07.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:07.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:07.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:07.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 22 13:42:07.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:07.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:07.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:07.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:07.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:07.036: INFO: 
Nov 22 13:42:09.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:09.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:09.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:09.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 22 13:42:09.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:09.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:09.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:09.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:09.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:09.034: INFO: 
Nov 22 13:42:11.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:11.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:11.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:11.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 22 13:42:11.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:11.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:11.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:11.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:11.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:11.036: INFO: 
Nov 22 13:42:13.148: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:13.148: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:13.148: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:13.148: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 22 13:42:13.148: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:13.148: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:13.148: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:13.148: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:13.148: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:13.148: INFO: 
Nov 22 13:42:15.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:15.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:15.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:15.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 22 13:42:15.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:15.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:15.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:15.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:15.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:15.040: INFO: 
Nov 22 13:42:17.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:17.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:17.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:17.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 22 13:42:17.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:17.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:17.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:17.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:17.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:17.036: INFO: 
Nov 22 13:42:19.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:19.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:19.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:19.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 22 13:42:19.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:19.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:19.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:19.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:19.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:19.035: INFO: 
Nov 22 13:42:21.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:21.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:21.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:21.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 22 13:42:21.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:21.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:21.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:21.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:21.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:21.034: INFO: 
Nov 22 13:42:23.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:23.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:23.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:23.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 22 13:42:23.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:23.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:23.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:23.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:23.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:23.035: INFO: 
Nov 22 13:42:25.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:25.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:25.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:25.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 22 13:42:25.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:25.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:25.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:25.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:25.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:25.038: INFO: 
Nov 22 13:42:27.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:27.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:27.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:27.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 22 13:42:27.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:27.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:27.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:27.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:27.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:27.036: INFO: 
Nov 22 13:42:29.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:29.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:29.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:29.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 22 13:42:29.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:29.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:29.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:29.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:29.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:29.034: INFO: 
Nov 22 13:42:31.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:31.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:31.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:31.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 22 13:42:31.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:31.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:31.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:31.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:31.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:31.033: INFO: 
Nov 22 13:42:33.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:33.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:33.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:33.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 22 13:42:33.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:33.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:33.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:33.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:33.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:33.038: INFO: 
Nov 22 13:42:35.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:35.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:35.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:35.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 22 13:42:35.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:35.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:35.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:35.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:35.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:35.036: INFO: 
Nov 22 13:42:37.042: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:37.042: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:37.042: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:37.042: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 22 13:42:37.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:37.042: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:37.042: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:37.042: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:37.042: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:37.042: INFO: 
Nov 22 13:42:39.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:39.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:39.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:39.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 22 13:42:39.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:39.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:39.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:39.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:39.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:39.036: INFO: 
Nov 22 13:42:41.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:41.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:41.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:41.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 22 13:42:41.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:41.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:41.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:41.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:41.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:41.034: INFO: 
Nov 22 13:42:43.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:43.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:43.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:43.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 22 13:42:43.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:43.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:43.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:43.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:43.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:43.036: INFO: 
Nov 22 13:42:45.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:45.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:45.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:45.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 22 13:42:45.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:45.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:45.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:45.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:45.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:45.040: INFO: 
Nov 22 13:42:47.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:47.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:47.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:47.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 22 13:42:47.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:47.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:47.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:47.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:47.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:47.034: INFO: 
Nov 22 13:42:49.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:49.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:49.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:49.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 22 13:42:49.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:49.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:49.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:49.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:49.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:49.036: INFO: 
Nov 22 13:42:51.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:51.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:51.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:51.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 22 13:42:51.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:51.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:51.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:51.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:51.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:51.039: INFO: 
Nov 22 13:42:53.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:53.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:53.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:53.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 22 13:42:53.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:53.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:53.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:53.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:53.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:53.034: INFO: 
Nov 22 13:42:55.043: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:55.043: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:55.043: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:55.043: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 22 13:42:55.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:55.043: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:55.043: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:55.043: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:55.043: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:55.043: INFO: 
Nov 22 13:42:57.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:57.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:57.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:57.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 22 13:42:57.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:57.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:57.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:57.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:57.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:57.035: INFO: 
Nov 22 13:42:59.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:59.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:59.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:42:59.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 22 13:42:59.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:42:59.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:42:59.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:59.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:59.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:42:59.034: INFO: 
Nov 22 13:43:01.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:01.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:01.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:01.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 22 13:43:01.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:01.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:01.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:01.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:01.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:01.036: INFO: 
Nov 22 13:43:03.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:03.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:03.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:03.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 22 13:43:03.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:03.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:03.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:03.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:03.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:03.034: INFO: 
Nov 22 13:43:05.039: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:05.039: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:05.039: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:05.039: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 22 13:43:05.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:05.039: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:05.039: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:05.039: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:05.039: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:05.039: INFO: 
Nov 22 13:43:07.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:07.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:07.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:07.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 22 13:43:07.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:07.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:07.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:07.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:07.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:07.035: INFO: 
Nov 22 13:43:09.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:09.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:09.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:09.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 22 13:43:09.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:09.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:09.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:09.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:09.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:09.038: INFO: 
Nov 22 13:43:11.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:11.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:11.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:11.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 22 13:43:11.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:11.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:11.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:11.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:11.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:11.034: INFO: 
Nov 22 13:43:13.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:13.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:13.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:13.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 22 13:43:13.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:13.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:13.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:13.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:13.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:13.034: INFO: 
Nov 22 13:43:15.042: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:15.042: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:15.042: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:15.042: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 22 13:43:15.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:15.042: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:15.042: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:15.042: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:15.042: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:15.042: INFO: 
Nov 22 13:43:17.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:17.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:17.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:17.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 22 13:43:17.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:17.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:17.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:17.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:17.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:17.035: INFO: 
Nov 22 13:43:19.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:19.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:19.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:19.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 22 13:43:19.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:19.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:19.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:19.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:19.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:19.036: INFO: 
Nov 22 13:43:21.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:21.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:21.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:21.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 22 13:43:21.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:21.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:21.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:21.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:21.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:21.036: INFO: 
Nov 22 13:43:23.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:23.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:23.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:23.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 22 13:43:23.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:23.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:23.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:23.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:23.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:23.035: INFO: 
Nov 22 13:43:25.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:25.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:25.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:25.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 22 13:43:25.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:25.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:25.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:25.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:25.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:25.041: INFO: 
Nov 22 13:43:27.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:27.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:27.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:27.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 22 13:43:27.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:27.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:27.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:27.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:27.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:27.034: INFO: 
Nov 22 13:43:29.033: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:29.033: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:29.033: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:29.033: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 22 13:43:29.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:29.033: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:29.033: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:29.033: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:29.033: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:29.033: INFO: 
Nov 22 13:43:31.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:31.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:31.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:31.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 22 13:43:31.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:31.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:31.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:31.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:31.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:31.035: INFO: 
Nov 22 13:43:33.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:33.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:33.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:33.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 22 13:43:33.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:33.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:33.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:33.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:33.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:33.035: INFO: 
Nov 22 13:43:35.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:35.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:35.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:35.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 22 13:43:35.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:35.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:35.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:35.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:35.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:35.038: INFO: 
Nov 22 13:43:37.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:37.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:37.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:37.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 22 13:43:37.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:37.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:37.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:37.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:37.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:37.038: INFO: 
Nov 22 13:43:39.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:39.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:39.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:39.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 22 13:43:39.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:39.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:39.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:39.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:39.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:39.034: INFO: 
Nov 22 13:43:41.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:41.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:41.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:41.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 22 13:43:41.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:41.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:41.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:41.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:41.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:41.034: INFO: 
Nov 22 13:43:43.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:43.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:43.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:43.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 22 13:43:43.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:43.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:43.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:43.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:43.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:43.038: INFO: 
Nov 22 13:43:45.046: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:45.046: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:45.046: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:45.046: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 22 13:43:45.046: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:45.046: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:45.046: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:45.046: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:45.046: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:45.046: INFO: 
Nov 22 13:43:47.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:47.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:47.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:47.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 22 13:43:47.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:47.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:47.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:47.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:47.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:47.035: INFO: 
Nov 22 13:43:49.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:49.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:49.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:49.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 22 13:43:49.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:49.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:49.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:49.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:49.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:49.037: INFO: 
Nov 22 13:43:51.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:51.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:51.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:51.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 22 13:43:51.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:51.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:51.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:51.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:51.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:51.035: INFO: 
Nov 22 13:43:53.042: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:53.042: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:53.042: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:53.042: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 22 13:43:53.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:53.042: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:53.042: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:53.042: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:53.042: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:53.042: INFO: 
Nov 22 13:43:55.043: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:55.043: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:55.043: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:55.043: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 22 13:43:55.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:55.043: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:55.043: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:55.043: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:55.043: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:55.043: INFO: 
Nov 22 13:43:57.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:57.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:57.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:57.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 22 13:43:57.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:57.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:57.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:57.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:57.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:57.035: INFO: 
Nov 22 13:43:59.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:59.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:59.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:43:59.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 22 13:43:59.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:43:59.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:43:59.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:59.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:59.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:43:59.036: INFO: 
Nov 22 13:44:01.040: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:01.040: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:01.040: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:01.040: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 22 13:44:01.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:01.040: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:01.040: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:01.040: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:01.040: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:01.040: INFO: 
Nov 22 13:44:03.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:03.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:03.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:03.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 22 13:44:03.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:03.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:03.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:03.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:03.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:03.034: INFO: 
Nov 22 13:44:05.050: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:05.050: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:05.050: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:05.050: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 22 13:44:05.050: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:05.050: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:05.050: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:05.050: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:05.050: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:05.050: INFO: 
Nov 22 13:44:07.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:07.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:07.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:07.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 22 13:44:07.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:07.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:07.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:07.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:07.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:07.035: INFO: 
Nov 22 13:44:09.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:09.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:09.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:09.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 22 13:44:09.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:09.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:09.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:09.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:09.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:09.034: INFO: 
Nov 22 13:44:11.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:11.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:11.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:11.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 22 13:44:11.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:11.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:11.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:11.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:11.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:11.034: INFO: 
Nov 22 13:44:13.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:13.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:13.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:13.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 22 13:44:13.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:13.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:13.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:13.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:13.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:13.034: INFO: 
Nov 22 13:44:15.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:15.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:15.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:15.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 22 13:44:15.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:15.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:15.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:15.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:15.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:15.037: INFO: 
Nov 22 13:44:17.038: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:17.038: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:17.038: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:17.038: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 22 13:44:17.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:17.038: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:17.038: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:17.038: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:17.038: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:17.038: INFO: 
Nov 22 13:44:19.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:19.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:19.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:19.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 22 13:44:19.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:19.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:19.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:19.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:19.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:19.035: INFO: 
Nov 22 13:44:21.041: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:21.041: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:21.041: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:21.041: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 22 13:44:21.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:21.041: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:21.041: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:21.041: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:21.041: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:21.041: INFO: 
Nov 22 13:44:23.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:23.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:23.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:23.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 22 13:44:23.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:23.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:23.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:23.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:23.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:23.034: INFO: 
Nov 22 13:44:25.044: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:25.044: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:25.044: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:25.044: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 22 13:44:25.044: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:25.044: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:25.044: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:25.044: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:25.044: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:25.044: INFO: 
Nov 22 13:44:27.036: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:27.036: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:27.036: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:27.036: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 22 13:44:27.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:27.036: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:27.036: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:27.036: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:27.036: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:27.036: INFO: 
Nov 22 13:44:29.037: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:29.037: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:29.037: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:29.037: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 22 13:44:29.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:29.037: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:29.037: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:29.037: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:29.037: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:29.037: INFO: 
Nov 22 13:44:31.034: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:31.034: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:31.034: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:31.034: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 22 13:44:31.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:31.034: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:31.034: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:31.034: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:31.034: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:31.034: INFO: 
Nov 22 13:44:33.035: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:33.035: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:33.035: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:33.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 22 13:44:33.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:33.035: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:33.035: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.035: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.035: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.035: INFO: 
Nov 22 13:44:33.159: INFO: The status of Pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:33.159: INFO: The status of Pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:33.159: INFO: The status of Pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 22 13:44:33.159: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 22 13:44:33.159: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 22 13:44:33.159: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:33.159: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.159: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.159: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.159: INFO: 
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/22/22 13:44:33.159�[0m
�[1mSTEP:�[0m Found 126 events. �[38;5;243m11/22/22 13:44:33.207�[0m
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:27 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-yq6h0h-control-plane-cqtht_b9af207f-9381-40b6-96b4-97daf949e48f became leader
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:27 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-yq6h0h-control-plane-cqtht_50ddbde5-9048-42a8-bca8-030eb3441ae1 became leader
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:36 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:36 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-f56th
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:36 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-rx6kz
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:36 +0000 UTC - event for coredns-787d4945fb-f56th: {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 22 13:44:33.207: INFO: At 2022-11-22 13:29:36 +0000 UTC - event for coredns-787d4945fb-rx6kz: {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 22 13:44:33.207: INFO: At 2022-11-22 13:29:36 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-f6lj5
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:36 +0000 UTC - event for kube-proxy-f6lj5: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-f6lj5 to capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:37 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-f6lj5
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:39 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-vfpst
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:39 +0000 UTC - event for kube-proxy-vfpst: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-vfpst to capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:41 +0000 UTC - event for kube-proxy-vfpst: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.34_b4a25fd6fa82a4"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:42 +0000 UTC - event for kube-proxy-vfpst: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.34_b4a25fd6fa82a4" in 1.375856573s (1.376446882s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:42 +0000 UTC - event for kube-proxy-vfpst: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Created: Created container kube-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:43 +0000 UTC - event for kube-proxy-vfpst: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Started: Started container kube-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:49 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:49 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-c75hc
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:49 +0000 UTC - event for metrics-server-c9574f845-c75hc: {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 22 13:44:33.207: INFO: At 2022-11-22 13:29:50 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:50 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-hqmwj
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:50 +0000 UTC - event for calico-kube-controllers-657b584867-hqmwj: {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 22 13:44:33.207: INFO: At 2022-11-22 13:29:50 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-bh44p
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:50 +0000 UTC - event for calico-node-bh44p: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-bh44p to capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:51 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:57 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Started: Started container upgrade-ipam
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:57 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Created: Created container upgrade-ipam
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:29:57 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 5.82420103s (5.82421883s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:01 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:01 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Created: Created container install-cni
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:01 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Started: Started container install-cni
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:04 +0000 UTC - event for calico-kube-controllers-657b584867-hqmwj: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-hqmwj to capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:04 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:04 +0000 UTC - event for coredns-787d4945fb-f56th: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-f56th to capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:04 +0000 UTC - event for coredns-787d4945fb-rx6kz: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-rx6kz to capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:04 +0000 UTC - event for metrics-server-c9574f845-c75hc: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-c75hc to capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:05 +0000 UTC - event for calico-kube-controllers-657b584867-hqmwj: {kubelet capz-conf-yq6h0h-control-plane-cqtht} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "55910915a1f65f4fcd5555356483f3f15a0d1129efa349b167a697773a7da9ee": 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 22 13:44:33.207: INFO: At 2022-11-22 13:30:05 +0000 UTC - event for coredns-787d4945fb-f56th: {kubelet capz-conf-yq6h0h-control-plane-cqtht} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "7f8fe02a77c455cd45d527f936be3aef1d81b174d11c0464b393db724cee142a": 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 22 13:44:33.207: INFO: At 2022-11-22 13:30:05 +0000 UTC - event for coredns-787d4945fb-rx6kz: {kubelet capz-conf-yq6h0h-control-plane-cqtht} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "419edec49d8667459feb09fad4d6435ce22e79143fe529acc7c80465ee8fa4e8": 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 22 13:44:33.207: INFO: At 2022-11-22 13:30:05 +0000 UTC - event for metrics-server-c9574f845-c75hc: {kubelet capz-conf-yq6h0h-control-plane-cqtht} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "758901e20ccd623682fc4b959ed9dcdc13a9add9b19e5a7bbfd786ac7c6a52ba": 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 22 13:44:33.207: INFO: At 2022-11-22 13:30:11 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} 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 22 13:44:33.207: INFO: At 2022-11-22 13:30:11 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 6.411071909s (6.411084309s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:11 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Created: Created container calico-node
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:11 +0000 UTC - event for calico-node-bh44p: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Started: Started container calico-node
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:17 +0000 UTC - event for calico-kube-controllers-657b584867-hqmwj: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:17 +0000 UTC - event for coredns-787d4945fb-f56th: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:17 +0000 UTC - event for coredns-787d4945fb-f56th: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Created: Created container coredns
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:17 +0000 UTC - event for coredns-787d4945fb-f56th: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Started: Started container coredns
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:18 +0000 UTC - event for coredns-787d4945fb-f56th: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Unhealthy: Readiness probe failed: Get "http://192.168.27.130:8181/ready": dial tcp 192.168.27.130:8181: connect: connection refused
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:18 +0000 UTC - event for coredns-787d4945fb-rx6kz: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:19 +0000 UTC - event for coredns-787d4945fb-rx6kz: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Created: Created container coredns
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:19 +0000 UTC - event for coredns-787d4945fb-rx6kz: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Started: Started container coredns
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:19 +0000 UTC - event for coredns-787d4945fb-rx6kz: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Unhealthy: Readiness probe failed: Get "http://192.168.27.131:8181/ready": dial tcp 192.168.27.131:8181: connect: connection refused
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:19 +0000 UTC - event for metrics-server-c9574f845-c75hc: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:22 +0000 UTC - event for calico-kube-controllers-657b584867-hqmwj: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.207213435s (5.207328336s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:22 +0000 UTC - event for calico-kube-controllers-657b584867-hqmwj: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Created: Created container calico-kube-controllers
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:23 +0000 UTC - event for calico-kube-controllers-657b584867-hqmwj: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Started: Started container calico-kube-controllers
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:26 +0000 UTC - event for metrics-server-c9574f845-c75hc: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Started: Started container metrics-server
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:26 +0000 UTC - event for metrics-server-c9574f845-c75hc: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Created: Created container metrics-server
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:30:26 +0000 UTC - event for metrics-server-c9574f845-c75hc: {kubelet capz-conf-yq6h0h-control-plane-cqtht} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.59816775s (6.853465295s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:07 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-fx4hg
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:07 +0000 UTC - event for calico-node-windows-fx4hg: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-fx4hg to capz-conf-xh56n
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:07 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-vrt84
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:07 +0000 UTC - event for containerd-logger-vrt84: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-vrt84 to capz-conf-xh56n
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:07 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-wj77r
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:07 +0000 UTC - event for kube-proxy-windows-wj77r: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-wj77r to capz-conf-xh56n
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:24 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:24 +0000 UTC - event for containerd-logger-vrt84: {kubelet capz-conf-xh56n} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:24 +0000 UTC - event for kube-proxy-windows-wj77r: {kubelet capz-conf-xh56n} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.32_57eb5d631ccd61-calico-hostprocess" already present on machine
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:24 +0000 UTC - event for kube-proxy-windows-wj77r: {kubelet capz-conf-xh56n} Created: Created container kube-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:24 +0000 UTC - event for kube-proxy-windows-wj77r: {kubelet capz-conf-xh56n} Started: Started container kube-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-vwdqr
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Created: Created container install-cni
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 3.5111377s (3.5112046s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Started: Started container install-cni
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for calico-node-windows-vwdqr: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-vwdqr to capz-conf-pf2j7
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-flxpq
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for containerd-logger-flxpq: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-flxpq to capz-conf-pf2j7
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-7s4nc
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:27 +0000 UTC - event for kube-proxy-windows-7s4nc: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-7s4nc to capz-conf-pf2j7
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:29 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:29 +0000 UTC - event for kube-proxy-windows-7s4nc: {kubelet capz-conf-pf2j7} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:30 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-b6fk5
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:30 +0000 UTC - event for csi-proxy-b6fk5: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-b6fk5 to capz-conf-xh56n
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:31 +0000 UTC - event for containerd-logger-vrt84: {kubelet capz-conf-xh56n} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.4879827s (6.9934906s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:31 +0000 UTC - event for csi-proxy-b6fk5: {kubelet capz-conf-xh56n} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:33 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:38 +0000 UTC - event for containerd-logger-vrt84: {kubelet capz-conf-xh56n} Created: Created container containerd-logger
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:39 +0000 UTC - event for containerd-logger-vrt84: {kubelet capz-conf-xh56n} Started: Started container containerd-logger
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:44 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:44 +0000 UTC - event for containerd-logger-flxpq: {kubelet capz-conf-pf2j7} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:44 +0000 UTC - event for kube-proxy-windows-7s4nc: {kubelet capz-conf-pf2j7} Started: Started container kube-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:44 +0000 UTC - event for kube-proxy-windows-7s4nc: {kubelet capz-conf-pf2j7} Created: Created container kube-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:44 +0000 UTC - event for kube-proxy-windows-7s4nc: {kubelet capz-conf-pf2j7} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.32_57eb5d631ccd61-calico-hostprocess" already present on machine
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:47 +0000 UTC - event for containerd-logger-flxpq: {kubelet capz-conf-pf2j7} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.2734381s (3.2734381s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:50 +0000 UTC - event for csi-proxy-b6fk5: {kubelet capz-conf-xh56n} Started: Started container csi-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:50 +0000 UTC - event for csi-proxy-b6fk5: {kubelet capz-conf-xh56n} Created: Created container csi-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:50 +0000 UTC - event for csi-proxy-b6fk5: {kubelet capz-conf-xh56n} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 18.7489196s (18.7489196s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:51 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 4.0878382s (7.2730145s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:51 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Created: Created container install-cni
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:52 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 2.6887464s (19.4468183s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:52 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Created: Created container calico-node-startup
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:52 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Started: Started container install-cni
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:53 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:53 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Started: Started container calico-node-startup
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:53 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 272.1713ms (272.1713ms including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:54 +0000 UTC - event for containerd-logger-flxpq: {kubelet capz-conf-pf2j7} Started: Started container containerd-logger
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:54 +0000 UTC - event for containerd-logger-flxpq: {kubelet capz-conf-pf2j7} Created: Created container containerd-logger
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:54 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-jgcsl
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:54 +0000 UTC - event for csi-proxy-jgcsl: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-jgcsl to capz-conf-pf2j7
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:55 +0000 UTC - event for csi-proxy-jgcsl: {kubelet capz-conf-pf2j7} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:56 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:59 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Created: Created container calico-node-felix
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:33:59 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Started: Started container calico-node-felix
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:09 +0000 UTC - event for csi-proxy-jgcsl: {kubelet capz-conf-pf2j7} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 13.9343973s (13.9343973s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:09 +0000 UTC - event for csi-proxy-jgcsl: {kubelet capz-conf-pf2j7} Created: Created container csi-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:09 +0000 UTC - event for csi-proxy-jgcsl: {kubelet capz-conf-pf2j7} Started: Started container csi-proxy
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:11 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 2.4727335s (14.6534925s including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:11 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Created: Created container calico-node-startup
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:11 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Started: Started container calico-node-startup
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:11 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:12 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 316.6582ms (316.6582ms including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:17 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Created: Created container calico-node-felix
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:17 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Started: Started container calico-node-felix
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:25 +0000 UTC - event for calico-node-windows-fx4hg: {kubelet capz-conf-xh56n} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 262.0083ms (262.0083ms including waiting)
Nov 22 13:44:33.207: INFO: At 2022-11-22 13:34:42 +0000 UTC - event for calico-node-windows-vwdqr: {kubelet capz-conf-pf2j7} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 221.0938ms (221.0938ms including waiting)
Nov 22 13:44:33.257: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
Nov 22 13:44:33.257: INFO: calico-kube-controllers-657b584867-hqmwj                      capz-conf-yq6h0h-control-plane-cqtht  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:23 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:23 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: calico-node-bh44p                                             capz-conf-yq6h0h-control-plane-cqtht  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:12 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:12 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:50 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: calico-node-windows-fx4hg                                     capz-conf-xh56n                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:33 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:31 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:31 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:07 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: calico-node-windows-vwdqr                                     capz-conf-pf2j7                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:56 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:47 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:47 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:27 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: containerd-logger-flxpq                                       capz-conf-pf2j7                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:28 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:54 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:27 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: containerd-logger-vrt84                                       capz-conf-xh56n                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:07 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:39 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:39 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:07 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: coredns-787d4945fb-f56th                                      capz-conf-yq6h0h-control-plane-cqtht  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:24 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:24 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: coredns-787d4945fb-rx6kz                                      capz-conf-yq6h0h-control-plane-cqtht  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:20 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:20 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: csi-proxy-b6fk5                                               capz-conf-xh56n                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:30 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:50 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:50 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:30 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: csi-proxy-jgcsl                                               capz-conf-pf2j7                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:54 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:10 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:34:10 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:54 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: etcd-capz-conf-yq6h0h-control-plane-cqtht                     capz-conf-yq6h0h-control-plane-cqtht  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:38 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:48 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:48 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:38 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.257: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht  capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.257: INFO: kube-proxy-vfpst                                              capz-conf-yq6h0h-control-plane-cqtht  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:39 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:43 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:43 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:29:39 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: kube-proxy-windows-7s4nc                                      capz-conf-pf2j7                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:28 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:45 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:45 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:27 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: kube-proxy-windows-wj77r                                      capz-conf-xh56n                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:07 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:25 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:25 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:33:07 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht           capz-conf-yq6h0h-control-plane-cqtht  Pending         []
Nov 22 13:44:33.257: INFO: metrics-server-c9574f845-c75hc                                capz-conf-yq6h0h-control-plane-cqtht  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:54 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-22 13:30:04 +0000 UTC  }]
Nov 22 13:44:33.257: INFO: 
Nov 22 13:44:33.759: INFO: 
Logging node info for node capz-conf-pf2j7
Nov 22 13:44:33.948: INFO: Node Info: &Node{ObjectMeta:{capz-conf-pf2j7    2e3573c4-8451-49ee-b839-5b069fe8e379 1660 0 2022-11-22 13:33:27 +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:eastus failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-pf2j7 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:eastus topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-yq6h0h cluster.x-k8s.io/cluster-namespace:capz-conf-yq6h0h cluster.x-k8s.io/machine:capz-conf-yq6h0h-md-win-75fdf9d44b-bth59 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-yq6h0h-md-win-75fdf9d44b 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.33.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:41:eb:04 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-22 13:33:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-22 13:33:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-22 13:33:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-22 13:34:20 +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-22 13:34:39 +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-22 13:39:35 +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-yq6h0h/providers/Microsoft.Compute/virtualMachines/capz-conf-pf2j7,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-22 13:39:35 +0000 UTC,LastTransitionTime:2022-11-22 13:33:27 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-22 13:39:35 +0000 UTC,LastTransitionTime:2022-11-22 13:33:27 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-22 13:39:35 +0000 UTC,LastTransitionTime:2022-11-22 13:33:27 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-22 13:39:35 +0000 UTC,LastTransitionTime:2022-11-22 13:33:54 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-pf2j7,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-pf2j7,SystemUUID:91C1A0BC-87D1-4201-B061-595D38EF9BD6,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.34+b4a25fd6fa82a4-dirty,KubeProxyVersion:v1.27.0-alpha.0.34+b4a25fd6fa82a4-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.32_57eb5d631ccd61-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 22 13:44:33.949: INFO: 
Logging kubelet events for node capz-conf-pf2j7
Nov 22 13:44:34.146: INFO: 
Logging pods the kubelet thinks is on node capz-conf-pf2j7
Nov 22 13:44:34.363: INFO: kube-proxy-windows-7s4nc started at 2022-11-22 13:33:28 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:34.363: INFO: 	Container kube-proxy ready: true, restart count 0
Nov 22 13:44:34.363: INFO: calico-node-windows-vwdqr started at 2022-11-22 13:33:28 +0000 UTC (1+2 container statuses recorded)
Nov 22 13:44:34.363: INFO: 	Init container install-cni ready: true, restart count 0
Nov 22 13:44:34.363: INFO: 	Container calico-node-felix ready: true, restart count 1
Nov 22 13:44:34.363: INFO: 	Container calico-node-startup ready: true, restart count 0
Nov 22 13:44:34.363: INFO: containerd-logger-flxpq started at 2022-11-22 13:33:28 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:34.363: INFO: 	Container containerd-logger ready: true, restart count 0
Nov 22 13:44:34.363: INFO: csi-proxy-jgcsl started at 2022-11-22 13:33:54 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:34.363: INFO: 	Container csi-proxy ready: true, restart count 0
Nov 22 13:44:34.998: INFO: 
Latency metrics for node capz-conf-pf2j7
Nov 22 13:44:34.998: INFO: 
Logging node info for node capz-conf-xh56n
Nov 22 13:44:35.148: INFO: Node Info: &Node{ObjectMeta:{capz-conf-xh56n    58e5da4e-db06-418b-9d71-81a2df368807 2088 0 2022-11-22 13:33:07 +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:eastus failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-xh56n kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:eastus topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-yq6h0h cluster.x-k8s.io/cluster-namespace:capz-conf-yq6h0h cluster.x-k8s.io/machine:capz-conf-yq6h0h-md-win-75fdf9d44b-cj9cg cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-yq6h0h-md-win-75fdf9d44b 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.194.1 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:30:c4:a2 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-22 13:33:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-22 13:33:07 +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-22 13:33:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2022-11-22 13:34:22 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {manager Update v1 2022-11-22 13:34:22 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kubelet.exe Update v1 2022-11-22 13:44:21 +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-yq6h0h/providers/Microsoft.Compute/virtualMachines/capz-conf-xh56n,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-22 13:44:21 +0000 UTC,LastTransitionTime:2022-11-22 13:33:07 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-22 13:44:21 +0000 UTC,LastTransitionTime:2022-11-22 13:33:07 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-22 13:44:21 +0000 UTC,LastTransitionTime:2022-11-22 13:33:07 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-22 13:44:21 +0000 UTC,LastTransitionTime:2022-11-22 13:33:30 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-xh56n,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-xh56n,SystemUUID:8F3C591E-A07B-4AFF-85BB-87A0529694CC,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.34+b4a25fd6fa82a4-dirty,KubeProxyVersion:v1.27.0-alpha.0.34+b4a25fd6fa82a4-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.32_57eb5d631ccd61-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 22 13:44:35.148: INFO: 
Logging kubelet events for node capz-conf-xh56n
Nov 22 13:44:35.348: INFO: 
Logging pods the kubelet thinks is on node capz-conf-xh56n
Nov 22 13:44:35.565: INFO: containerd-logger-vrt84 started at 2022-11-22 13:33:07 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:35.565: INFO: 	Container containerd-logger ready: true, restart count 0
Nov 22 13:44:35.565: INFO: kube-proxy-windows-wj77r started at 2022-11-22 13:33:07 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:35.565: INFO: 	Container kube-proxy ready: true, restart count 0
Nov 22 13:44:35.565: INFO: calico-node-windows-fx4hg started at 2022-11-22 13:33:07 +0000 UTC (1+2 container statuses recorded)
Nov 22 13:44:35.565: INFO: 	Init container install-cni ready: true, restart count 0
Nov 22 13:44:35.565: INFO: 	Container calico-node-felix ready: true, restart count 1
Nov 22 13:44:35.565: INFO: 	Container calico-node-startup ready: true, restart count 0
Nov 22 13:44:35.565: INFO: csi-proxy-b6fk5 started at 2022-11-22 13:33:30 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:35.565: INFO: 	Container csi-proxy ready: true, restart count 0
Nov 22 13:44:36.207: INFO: 
Latency metrics for node capz-conf-xh56n
Nov 22 13:44:36.207: INFO: 
Logging node info for node capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:36.350: INFO: Node Info: &Node{ObjectMeta:{capz-conf-yq6h0h-control-plane-cqtht    0ed09e2f-f434-4b07-be9c-f9db2ea655d6 1774 0 2022-11-22 13:29:35 +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:eastus failure-domain.beta.kubernetes.io/zone:eastus-2 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-yq6h0h-control-plane-cqtht 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:eastus topology.kubernetes.io/zone:eastus-2] map[cluster.x-k8s.io/cluster-name:capz-conf-yq6h0h cluster.x-k8s.io/cluster-namespace:capz-conf-yq6h0h cluster.x-k8s.io/machine:capz-conf-yq6h0h-control-plane-hnz4q cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-yq6h0h-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.27.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-22 13:29:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/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-22 13:29:36 +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-22 13:29:48 +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-22 13:30:04 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-22 13:30:11 +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-22 13:40:51 +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-yq6h0h/providers/Microsoft.Compute/virtualMachines/capz-conf-yq6h0h-control-plane-cqtht,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-22 13:30:11 +0000 UTC,LastTransitionTime:2022-11-22 13:30:11 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-22 13:40:51 +0000 UTC,LastTransitionTime:2022-11-22 13:29:11 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-22 13:40:51 +0000 UTC,LastTransitionTime:2022-11-22 13:29:11 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-22 13:40:51 +0000 UTC,LastTransitionTime:2022-11-22 13:29:11 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-22 13:40:51 +0000 UTC,LastTransitionTime:2022-11-22 13:30:04 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-yq6h0h-control-plane-cqtht,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:54f6e3d3052b43c08354c202466add00,SystemUUID:122b27dd-857d-b146-b3ea-3e5d56cd59a3,BootID:cc8d0e46-2730-4c3d-9be7-92a90fc6b2d6,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.34+b4a25fd6fa82a4,KubeProxyVersion:v1.27.0-alpha.0.34+b4a25fd6fa82a4,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:7a3aaeb42057aafd4da4538a84c937ca23bfece791bdee9e9872bc7f674a2610 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.32_57eb5d631ccd61],SizeBytes:35317326,},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:d60e6280a01cbcecfa44852aea235bed2440618f7b74523b86339acca61b4da3 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.32_57eb5d631ccd61],SizeBytes:32243470,},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:0138748c7a93db3885f8f5f802e5a6e5dd420937da631a2b2835ba715dd12b6b gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.32_57eb5d631ccd61],SizeBytes:21534312,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:6d5e307982736de75f8cb41c2667f84305d1084b66ae93c05ce30e77a51b7ff6 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.34_b4a25fd6fa82a4],SizeBytes:21532478,},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:5aa3c32efaf72b0c70602c2437f09e71032a72f41e8bc0e47e36629acb2d18a2 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.32_57eb5d631ccd61],SizeBytes:17482399,},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 22 13:44:36.350: INFO: 
Logging kubelet events for node capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:36.547: INFO: 
Logging pods the kubelet thinks is on node capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:36.778: INFO: kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht started at <nil> (0+0 container statuses recorded)
Nov 22 13:44:36.778: INFO: kube-proxy-vfpst started at 2022-11-22 13:29:39 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:36.778: INFO: 	Container kube-proxy ready: true, restart count 0
Nov 22 13:44:36.778: INFO: calico-node-bh44p started at 2022-11-22 13:29:50 +0000 UTC (2+1 container statuses recorded)
Nov 22 13:44:36.778: INFO: 	Init container upgrade-ipam ready: true, restart count 0
Nov 22 13:44:36.778: INFO: 	Init container install-cni ready: true, restart count 0
Nov 22 13:44:36.778: INFO: 	Container calico-node ready: true, restart count 0
Nov 22 13:44:36.778: INFO: calico-kube-controllers-657b584867-hqmwj started at 2022-11-22 13:30:04 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:36.778: INFO: 	Container calico-kube-controllers ready: true, restart count 0
Nov 22 13:44:36.778: INFO: etcd-capz-conf-yq6h0h-control-plane-cqtht started at 2022-11-22 13:29:38 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:36.778: INFO: 	Container etcd ready: true, restart count 0
Nov 22 13:44:36.778: INFO: kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht started at <nil> (0+0 container statuses recorded)
Nov 22 13:44:36.778: INFO: coredns-787d4945fb-f56th started at 2022-11-22 13:30:04 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:36.778: INFO: 	Container coredns ready: true, restart count 0
Nov 22 13:44:36.778: INFO: coredns-787d4945fb-rx6kz started at 2022-11-22 13:30:04 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:36.778: INFO: 	Container coredns ready: true, restart count 0
Nov 22 13:44:36.778: INFO: metrics-server-c9574f845-c75hc started at 2022-11-22 13:30:04 +0000 UTC (0+1 container statuses recorded)
Nov 22 13:44:36.778: INFO: 	Container metrics-server ready: true, restart count 0
Nov 22 13:44:36.778: INFO: kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht started at <nil> (0+0 container statuses recorded)
Nov 22 13:44:37.396: INFO: 
Latency metrics for node capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:37.560: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 22 13:44:37.951: INFO: Failed to get logs of pod kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht)
Nov 22 13:44:37.951: INFO: Logs of kube-system/kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht:kube-apiserver on node capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:37.951: INFO:  : STARTLOG

ENDLOG for container kube-system:kube-apiserver-capz-conf-yq6h0h-control-plane-cqtht:kube-apiserver
Nov 22 13:44:38.347: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht)
Nov 22 13:44:38.347: INFO: Logs of kube-system/kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht:kube-controller-manager on node capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:38.347: INFO:  : STARTLOG

ENDLOG for container kube-system:kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht:kube-controller-manager
Nov 22 13:44:38.748: INFO: Failed to get logs of pod kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht)
Nov 22 13:44:38.748: INFO: Logs of kube-system/kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht:kube-scheduler on node capz-conf-yq6h0h-control-plane-cqtht
Nov 22 13:44:38.748: INFO:  : STARTLOG

ENDLOG for container kube-system:kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht:kube-scheduler
Nov 22 13:44:38.748: 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-yq6h0h-control-plane-cqtht          capz-conf-yq6h0h-control-plane-cqtht Pending       []
kube-controller-manager-capz-conf-yq6h0h-control-plane-cqtht capz-conf-yq6h0h-control-plane-cqtht Pending       []
kube-scheduler-capz-conf-yq6h0h-control-plane-cqtht          capz-conf-yq6h0h-control-plane-cqtht 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}, {0xc0000b8f20, 0x0, 0x0?})
	/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0xc0000b8f20?, 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	claudiubelu: Replaces path.Operation with filepath.Operation (part 2)
Result	SUCCESS
Tests	4 failed / 6 succeeded
Started	2022-11-22 12:50
Elapsed	1h7m
Revision	3efc6945f70785209d7bb5861ff0bd9cceb6e4c5
Refs	110863

PR #110863 pull-kubernetes-e2e-capz-windows-containerd #1595036308873416704

Test Failures

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

Kubernetes e2e suite [SynchronizedBeforeSuite] 10m6s

Passed

Skipped