PR #115040 pull-kubernetes-e2e-capz-conformance #1615085319911116800
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | mpatlasov: Stop reporting volume limits for migrated in-tree drivers in Node object |
| Result | SUCCESS |
| Tests | 25 failed / 30 succeeded |
| Started | |
| Elapsed | 59m58s |
| Revision | 47b72ed5591e8766ff4f4889c0fa4aa3b9b90711 |
| Refs |
115040 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.389from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.389
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.389from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.389
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.4from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.4
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.406from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.406
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.386from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.386
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] Error waiting for all pods to be running and ready: 3 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s POD NODE PHASE GRACE CONDITIONS kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/16/23 21:29:57.355from junit.kubetest.01.xml
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/16/23 21:19:49.71 Jan 16 21:19:49.710: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 16 21:19:49.717: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 16 21:19:49.941: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 16 21:19:50.121: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:50.121: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:50.121: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:50.121: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 16 21:19:50.121: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:19:50.121: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:19:50.121: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:50.121: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:50.121: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:50.121: INFO: Jan 16 21:19:52.267: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:52.267: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:52.267: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:52.267: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Jan 16 21:19:52.267: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:19:52.267: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:19:52.267: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:52.267: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:52.267: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:52.267: INFO: Jan 16 21:19:54.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:54.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:54.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:54.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Jan 16 21:19:54.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:19:54.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:19:54.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:54.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:54.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:54.245: INFO: Jan 16 21:19:56.280: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:56.280: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:56.280: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:56.280: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Jan 16 21:19:56.280: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:19:56.280: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:19:56.280: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:56.280: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:56.280: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:56.280: INFO: Jan 16 21:19:58.256: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:58.257: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:58.257: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:19:58.257: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Jan 16 21:19:58.260: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:19:58.260: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:19:58.260: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:58.260: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:58.260: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:19:58.260: INFO: Jan 16 21:20:00.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:00.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:00.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:00.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Jan 16 21:20:00.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:00.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:00.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:00.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:00.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:00.247: INFO: Jan 16 21:20:02.255: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:02.255: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:02.255: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:02.255: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Jan 16 21:20:02.255: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:02.255: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:02.255: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:02.255: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:02.255: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:02.255: INFO: Jan 16 21:20:04.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:04.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:04.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:04.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Jan 16 21:20:04.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:04.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:04.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:04.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:04.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:04.249: INFO: Jan 16 21:20:06.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:06.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:06.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:06.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Jan 16 21:20:06.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:06.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:06.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:06.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:06.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:06.249: INFO: Jan 16 21:20:08.258: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:08.258: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:08.258: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:08.258: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Jan 16 21:20:08.258: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:08.258: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:08.258: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:08.258: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:08.258: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:08.258: INFO: Jan 16 21:20:10.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:10.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:10.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:10.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Jan 16 21:20:10.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:10.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:10.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:10.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:10.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:10.245: INFO: Jan 16 21:20:12.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:12.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:12.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:12.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Jan 16 21:20:12.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:12.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:12.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:12.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:12.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:12.249: INFO: Jan 16 21:20:14.248: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:14.248: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:14.248: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:14.248: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Jan 16 21:20:14.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:14.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:14.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:14.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:14.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:14.248: INFO: Jan 16 21:20:16.385: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:16.385: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:16.385: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:16.385: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Jan 16 21:20:16.385: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:16.385: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:16.385: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:16.385: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:16.385: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:16.385: INFO: Jan 16 21:20:18.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:18.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:18.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:18.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Jan 16 21:20:18.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:18.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:18.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:18.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:18.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:18.247: INFO: Jan 16 21:20:20.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:20.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:20.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:20.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Jan 16 21:20:20.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:20.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:20.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:20.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:20.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:20.249: INFO: Jan 16 21:20:22.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:22.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:22.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:22.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Jan 16 21:20:22.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:22.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:22.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:22.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:22.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:22.243: INFO: Jan 16 21:20:24.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:24.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:24.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:24.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Jan 16 21:20:24.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:24.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:24.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:24.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:24.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:24.249: INFO: Jan 16 21:20:26.264: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:26.264: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:26.264: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:26.264: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Jan 16 21:20:26.264: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:26.264: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:26.264: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:26.264: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:26.264: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:26.264: INFO: Jan 16 21:20:28.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:28.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:28.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:28.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Jan 16 21:20:28.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:28.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:28.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:28.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:28.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:28.247: INFO: Jan 16 21:20:30.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:30.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:30.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:30.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Jan 16 21:20:30.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:30.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:30.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:30.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:30.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:30.244: INFO: Jan 16 21:20:32.252: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:32.252: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:32.252: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:32.252: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Jan 16 21:20:32.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:32.252: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:32.252: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:32.252: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:32.252: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:32.252: INFO: Jan 16 21:20:34.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:34.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:34.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:34.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Jan 16 21:20:34.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:34.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:34.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:34.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:34.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:34.246: INFO: Jan 16 21:20:36.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:36.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:36.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:36.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Jan 16 21:20:36.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:36.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:36.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:36.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:36.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:36.245: INFO: Jan 16 21:20:38.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:38.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:38.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:38.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Jan 16 21:20:38.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:38.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:38.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:38.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:38.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:38.244: INFO: Jan 16 21:20:40.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:40.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:40.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:40.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Jan 16 21:20:40.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:40.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:40.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:40.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:40.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:40.244: INFO: Jan 16 21:20:42.248: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:42.248: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:42.248: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:42.248: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Jan 16 21:20:42.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:42.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:42.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:42.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:42.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:42.248: INFO: Jan 16 21:20:44.248: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:44.248: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:44.248: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:44.248: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Jan 16 21:20:44.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:44.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:44.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:44.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:44.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:44.248: INFO: Jan 16 21:20:46.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:46.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:46.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:46.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Jan 16 21:20:46.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:46.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:46.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:46.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:46.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:46.242: INFO: Jan 16 21:20:48.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:48.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:48.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:48.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Jan 16 21:20:48.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:48.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:48.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:48.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:48.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:48.247: INFO: Jan 16 21:20:50.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:50.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:50.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:50.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Jan 16 21:20:50.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:50.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:50.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:50.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:50.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:50.249: INFO: Jan 16 21:20:52.253: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:52.253: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:52.253: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:52.253: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Jan 16 21:20:52.253: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:52.253: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:52.253: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:52.253: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:52.253: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:52.253: INFO: Jan 16 21:20:54.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:54.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:54.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:54.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Jan 16 21:20:54.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:54.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:54.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:54.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:54.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:54.246: INFO: Jan 16 21:20:56.272: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:56.272: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:56.272: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:56.272: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Jan 16 21:20:56.272: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:56.272: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:56.272: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:56.272: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:56.272: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:56.272: INFO: Jan 16 21:20:58.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:58.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:58.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:20:58.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Jan 16 21:20:58.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:20:58.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:20:58.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:58.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:58.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:20:58.244: INFO: Jan 16 21:21:00.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:00.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:00.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:00.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Jan 16 21:21:00.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:00.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:00.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:00.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:00.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:00.249: INFO: Jan 16 21:21:02.253: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:02.253: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:02.253: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:02.253: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Jan 16 21:21:02.253: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:02.253: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:02.253: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:02.253: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:02.253: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:02.253: INFO: Jan 16 21:21:04.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:04.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:04.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:04.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Jan 16 21:21:04.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:04.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:04.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:04.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:04.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:04.243: INFO: Jan 16 21:21:06.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:06.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:06.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:06.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Jan 16 21:21:06.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:06.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:06.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:06.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:06.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:06.244: INFO: Jan 16 21:21:08.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:08.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:08.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:08.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Jan 16 21:21:08.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:08.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:08.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:08.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:08.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:08.247: INFO: Jan 16 21:21:10.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:10.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:10.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:10.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Jan 16 21:21:10.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:10.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:10.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:10.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:10.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:10.249: INFO: Jan 16 21:21:12.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:12.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:12.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:12.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Jan 16 21:21:12.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:12.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:12.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:12.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:12.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:12.245: INFO: Jan 16 21:21:14.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:14.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:14.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:14.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Jan 16 21:21:14.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:14.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:14.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:14.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:14.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:14.246: INFO: Jan 16 21:21:16.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:16.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:16.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:16.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Jan 16 21:21:16.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:16.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:16.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:16.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:16.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:16.245: INFO: Jan 16 21:21:18.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:18.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:18.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:18.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Jan 16 21:21:18.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:18.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:18.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:18.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:18.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:18.243: INFO: Jan 16 21:21:20.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:20.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:20.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:20.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Jan 16 21:21:20.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:20.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:20.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:20.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:20.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:20.246: INFO: Jan 16 21:21:22.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:22.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:22.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:22.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Jan 16 21:21:22.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:22.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:22.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:22.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:22.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:22.245: INFO: Jan 16 21:21:24.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:24.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:24.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:24.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Jan 16 21:21:24.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:24.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:24.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:24.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:24.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:24.245: INFO: Jan 16 21:21:26.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:26.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:26.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:26.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Jan 16 21:21:26.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:26.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:26.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:26.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:26.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:26.242: INFO: Jan 16 21:21:28.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:28.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:28.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:28.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Jan 16 21:21:28.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:28.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:28.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:28.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:28.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:28.246: INFO: Jan 16 21:21:30.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:30.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:30.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:30.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Jan 16 21:21:30.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:30.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:30.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:30.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:30.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:30.246: INFO: Jan 16 21:21:32.251: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:32.252: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:32.252: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:32.252: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Jan 16 21:21:32.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:32.252: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:32.252: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:32.252: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:32.252: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:32.252: INFO: Jan 16 21:21:34.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:34.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:34.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:34.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Jan 16 21:21:34.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:34.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:34.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:34.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:34.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:34.246: INFO: Jan 16 21:21:36.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:36.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:36.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:36.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Jan 16 21:21:36.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:36.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:36.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:36.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:36.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:36.249: INFO: Jan 16 21:21:38.261: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:38.261: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:38.261: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:38.261: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Jan 16 21:21:38.261: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:38.261: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:38.261: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:38.261: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:38.261: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:38.261: INFO: Jan 16 21:21:40.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:40.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:40.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:40.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Jan 16 21:21:40.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:40.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:40.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:40.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:40.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:40.247: INFO: Jan 16 21:21:42.250: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:42.250: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:42.250: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:42.250: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Jan 16 21:21:42.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:42.250: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:42.250: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:42.250: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:42.250: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:42.250: INFO: Jan 16 21:21:44.250: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:44.250: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:44.250: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:44.250: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Jan 16 21:21:44.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:44.250: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:44.250: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:44.250: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:44.250: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:44.250: INFO: Jan 16 21:21:46.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:46.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:46.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:46.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Jan 16 21:21:46.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:46.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:46.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:46.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:46.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:46.247: INFO: Jan 16 21:21:48.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:48.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:48.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:48.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Jan 16 21:21:48.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:48.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:48.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:48.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:48.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:48.247: INFO: Jan 16 21:21:50.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:50.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:50.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:50.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Jan 16 21:21:50.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:50.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:50.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:50.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:50.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:50.243: INFO: Jan 16 21:21:52.264: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:52.264: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:52.264: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:52.264: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Jan 16 21:21:52.264: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:52.264: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:52.264: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:52.264: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:52.264: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:52.264: INFO: Jan 16 21:21:54.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:54.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:54.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:54.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Jan 16 21:21:54.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:54.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:54.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:54.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:54.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:54.244: INFO: Jan 16 21:21:56.252: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:56.252: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:56.252: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:56.252: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Jan 16 21:21:56.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:56.252: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:56.252: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:56.252: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:56.252: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:56.252: INFO: Jan 16 21:21:58.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:58.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:58.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:21:58.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Jan 16 21:21:58.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:21:58.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:21:58.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:58.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:58.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:21:58.245: INFO: Jan 16 21:22:00.256: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:00.256: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:00.256: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:00.256: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Jan 16 21:22:00.256: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:00.256: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:00.256: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:00.256: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:00.256: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:00.256: INFO: Jan 16 21:22:02.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:02.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:02.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:02.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Jan 16 21:22:02.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:02.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:02.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:02.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:02.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:02.249: INFO: Jan 16 21:22:04.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:04.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:04.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:04.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Jan 16 21:22:04.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:04.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:04.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:04.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:04.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:04.242: INFO: Jan 16 21:22:06.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:06.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:06.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:06.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Jan 16 21:22:06.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:06.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:06.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:06.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:06.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:06.246: INFO: Jan 16 21:22:08.254: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:08.254: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:08.254: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:08.254: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Jan 16 21:22:08.254: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:08.254: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:08.254: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:08.254: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:08.254: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:08.254: INFO: Jan 16 21:22:10.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:10.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:10.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:10.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Jan 16 21:22:10.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:10.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:10.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:10.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:10.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:10.247: INFO: Jan 16 21:22:12.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:12.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:12.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:12.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Jan 16 21:22:12.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:12.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:12.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:12.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:12.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:12.246: INFO: Jan 16 21:22:14.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:14.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:14.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:14.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Jan 16 21:22:14.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:14.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:14.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:14.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:14.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:14.247: INFO: Jan 16 21:22:16.252: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:16.252: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:16.252: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:16.252: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Jan 16 21:22:16.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:16.252: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:16.252: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:16.252: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:16.252: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:16.252: INFO: Jan 16 21:22:18.253: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:18.253: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:18.253: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:18.253: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Jan 16 21:22:18.253: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:18.253: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:18.253: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:18.253: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:18.253: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:18.253: INFO: Jan 16 21:22:20.260: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:20.260: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:20.260: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:20.260: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Jan 16 21:22:20.260: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:20.260: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:20.260: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:20.260: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:20.260: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:20.260: INFO: Jan 16 21:22:22.252: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:22.252: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:22.252: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:22.252: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Jan 16 21:22:22.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:22.252: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:22.252: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:22.252: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:22.252: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:22.252: INFO: Jan 16 21:22:24.254: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:24.254: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:24.254: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:24.254: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Jan 16 21:22:24.254: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:24.254: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:24.254: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:24.254: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:24.254: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:24.254: INFO: Jan 16 21:22:26.264: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:26.264: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:26.264: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:26.264: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Jan 16 21:22:26.264: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:26.264: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:26.264: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:26.264: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:26.264: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:26.264: INFO: Jan 16 21:22:28.248: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:28.248: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:28.248: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:28.248: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Jan 16 21:22:28.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:28.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:28.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:28.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:28.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:28.248: INFO: Jan 16 21:22:30.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:30.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:30.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:30.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Jan 16 21:22:30.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:30.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:30.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:30.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:30.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:30.245: INFO: Jan 16 21:22:32.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:32.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:32.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:32.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Jan 16 21:22:32.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:32.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:32.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:32.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:32.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:32.249: INFO: Jan 16 21:22:34.248: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:34.248: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:34.248: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:34.248: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Jan 16 21:22:34.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:34.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:34.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:34.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:34.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:34.248: INFO: Jan 16 21:22:36.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:36.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:36.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:36.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Jan 16 21:22:36.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:36.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:36.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:36.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:36.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:36.246: INFO: Jan 16 21:22:38.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:38.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:38.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:38.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Jan 16 21:22:38.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:38.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:38.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:38.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:38.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:38.244: INFO: Jan 16 21:22:40.250: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:40.250: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:40.250: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:40.250: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Jan 16 21:22:40.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:40.250: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:40.250: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:40.250: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:40.250: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:40.250: INFO: Jan 16 21:22:42.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:42.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:42.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:42.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Jan 16 21:22:42.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:42.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:42.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:42.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:42.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:42.245: INFO: Jan 16 21:22:44.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:44.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:44.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:44.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Jan 16 21:22:44.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:44.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:44.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:44.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:44.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:44.248: INFO: Jan 16 21:22:46.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:46.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:46.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:46.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Jan 16 21:22:46.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:46.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:46.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:46.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:46.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:46.245: INFO: Jan 16 21:22:48.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:48.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:48.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:48.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Jan 16 21:22:48.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:48.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:48.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:48.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:48.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:48.244: INFO: Jan 16 21:22:50.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:50.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:50.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:50.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Jan 16 21:22:50.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:50.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:50.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:50.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:50.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:50.247: INFO: Jan 16 21:22:52.248: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:52.248: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:52.248: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:52.248: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Jan 16 21:22:52.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:52.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:52.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:52.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:52.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:52.248: INFO: Jan 16 21:22:54.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:54.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:54.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:54.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Jan 16 21:22:54.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:54.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:54.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:54.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:54.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:54.246: INFO: Jan 16 21:22:56.264: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:56.264: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:56.264: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:56.264: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Jan 16 21:22:56.264: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:56.264: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:56.264: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:56.264: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:56.264: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:56.264: INFO: Jan 16 21:22:58.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:58.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:58.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:22:58.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Jan 16 21:22:58.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:22:58.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:22:58.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:58.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:58.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:22:58.249: INFO: Jan 16 21:23:00.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:00.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:00.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:00.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Jan 16 21:23:00.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:00.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:00.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:00.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:00.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:00.242: INFO: Jan 16 21:23:02.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:02.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:02.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:02.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Jan 16 21:23:02.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:02.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:02.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:02.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:02.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:02.246: INFO: Jan 16 21:23:04.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:04.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:04.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:04.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Jan 16 21:23:04.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:04.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:04.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:04.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:04.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:04.245: INFO: Jan 16 21:23:06.251: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:06.251: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:06.251: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:06.251: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Jan 16 21:23:06.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:06.251: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:06.251: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:06.251: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:06.251: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:06.251: INFO: Jan 16 21:23:08.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:08.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:08.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:08.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Jan 16 21:23:08.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:08.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:08.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:08.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:08.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:08.249: INFO: Jan 16 21:23:10.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:10.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:10.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:10.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Jan 16 21:23:10.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:10.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:10.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:10.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:10.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:10.247: INFO: Jan 16 21:23:12.255: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:12.255: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:12.255: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:12.255: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Jan 16 21:23:12.255: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:12.255: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:12.255: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:12.255: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:12.255: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:12.255: INFO: Jan 16 21:23:14.250: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:14.250: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:14.250: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:14.250: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Jan 16 21:23:14.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:14.250: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:14.250: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:14.250: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:14.250: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:14.250: INFO: Jan 16 21:23:16.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:16.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:16.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:16.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Jan 16 21:23:16.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:16.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:16.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:16.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:16.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:16.244: INFO: Jan 16 21:23:18.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:18.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:18.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:18.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Jan 16 21:23:18.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:18.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:18.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:18.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:18.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:18.245: INFO: Jan 16 21:23:20.255: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:20.255: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:20.255: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:20.255: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Jan 16 21:23:20.255: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:20.255: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:20.255: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:20.255: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:20.255: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:20.255: INFO: Jan 16 21:23:22.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:22.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:22.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:22.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Jan 16 21:23:22.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:22.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:22.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:22.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:22.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:22.244: INFO: Jan 16 21:23:24.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:24.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:24.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:24.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Jan 16 21:23:24.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:24.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:24.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:24.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:24.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:24.247: INFO: Jan 16 21:23:26.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:26.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:26.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:26.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Jan 16 21:23:26.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:26.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:26.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:26.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:26.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:26.247: INFO: Jan 16 21:23:28.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:28.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:28.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:28.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Jan 16 21:23:28.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:28.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:28.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:28.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:28.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:28.245: INFO: Jan 16 21:23:30.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:30.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:30.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:30.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Jan 16 21:23:30.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:30.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:30.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:30.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:30.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:30.242: INFO: Jan 16 21:23:32.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:32.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:32.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:32.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Jan 16 21:23:32.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:32.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:32.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:32.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:32.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:32.243: INFO: Jan 16 21:23:34.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:34.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:34.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:34.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Jan 16 21:23:34.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:34.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:34.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:34.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:34.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:34.244: INFO: Jan 16 21:23:36.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:36.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:36.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:36.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Jan 16 21:23:36.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:36.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:36.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:36.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:36.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:36.245: INFO: Jan 16 21:23:38.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:38.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:38.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:38.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Jan 16 21:23:38.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:38.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:38.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:38.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:38.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:38.245: INFO: Jan 16 21:23:40.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:40.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:40.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:40.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Jan 16 21:23:40.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:40.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:40.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:40.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:40.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:40.245: INFO: Jan 16 21:23:42.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:42.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:42.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:42.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Jan 16 21:23:42.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:42.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:42.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:42.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:42.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:42.243: INFO: Jan 16 21:23:44.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:44.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:44.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:44.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Jan 16 21:23:44.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:44.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:44.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:44.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:44.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:44.243: INFO: Jan 16 21:23:46.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:46.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:46.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:46.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Jan 16 21:23:46.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:46.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:46.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:46.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:46.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:46.244: INFO: Jan 16 21:23:48.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:48.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:48.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:48.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Jan 16 21:23:48.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:48.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:48.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:48.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:48.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:48.245: INFO: Jan 16 21:23:50.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:50.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:50.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:50.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Jan 16 21:23:50.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:50.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:50.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:50.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:50.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:50.249: INFO: Jan 16 21:23:52.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:52.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:52.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:52.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Jan 16 21:23:52.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:52.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:52.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:52.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:52.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:52.240: INFO: Jan 16 21:23:54.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:54.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:54.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:54.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Jan 16 21:23:54.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:54.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:54.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:54.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:54.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:54.239: INFO: Jan 16 21:23:56.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:56.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:56.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:56.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Jan 16 21:23:56.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:56.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:56.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:56.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:56.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:56.246: INFO: Jan 16 21:23:58.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:58.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:58.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:23:58.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Jan 16 21:23:58.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:23:58.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:23:58.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:58.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:58.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:23:58.242: INFO: Jan 16 21:24:00.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:00.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:00.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:00.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Jan 16 21:24:00.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:00.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:00.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:00.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:00.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:00.239: INFO: Jan 16 21:24:02.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:02.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:02.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:02.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Jan 16 21:24:02.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:02.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:02.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:02.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:02.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:02.239: INFO: Jan 16 21:24:04.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:04.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:04.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:04.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Jan 16 21:24:04.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:04.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:04.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:04.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:04.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:04.240: INFO: Jan 16 21:24:06.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:06.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:06.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:06.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Jan 16 21:24:06.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:06.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:06.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:06.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:06.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:06.239: INFO: Jan 16 21:24:08.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:08.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:08.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:08.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Jan 16 21:24:08.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:08.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:08.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:08.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:08.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:08.242: INFO: Jan 16 21:24:10.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:10.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:10.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:10.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Jan 16 21:24:10.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:10.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:10.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:10.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:10.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:10.241: INFO: Jan 16 21:24:12.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:12.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:12.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:12.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Jan 16 21:24:12.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:12.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:12.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:12.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:12.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:12.242: INFO: Jan 16 21:24:14.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:14.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:14.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:14.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Jan 16 21:24:14.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:14.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:14.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:14.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:14.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:14.238: INFO: Jan 16 21:24:16.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:16.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:16.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:16.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Jan 16 21:24:16.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:16.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:16.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:16.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:16.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:16.241: INFO: Jan 16 21:24:18.248: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:18.248: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:18.248: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:18.248: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Jan 16 21:24:18.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:18.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:18.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:18.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:18.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:18.248: INFO: Jan 16 21:24:20.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:20.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:20.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:20.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Jan 16 21:24:20.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:20.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:20.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:20.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:20.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:20.241: INFO: Jan 16 21:24:22.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:22.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:22.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:22.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Jan 16 21:24:22.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:22.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:22.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:22.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:22.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:22.241: INFO: Jan 16 21:24:24.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:24.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:24.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:24.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Jan 16 21:24:24.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:24.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:24.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:24.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:24.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:24.239: INFO: Jan 16 21:24:27.734: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:27.734: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:27.734: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:27.734: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (277 seconds elapsed) Jan 16 21:24:27.734: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:27.734: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:27.734: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:27.734: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:27.734: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:27.734: INFO: Jan 16 21:24:28.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:28.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:28.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:28.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Jan 16 21:24:28.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:28.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:28.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:28.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:28.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:28.240: INFO: Jan 16 21:24:30.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:30.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:30.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:30.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Jan 16 21:24:30.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:30.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:30.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:30.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:30.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:30.243: INFO: Jan 16 21:24:32.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:32.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:32.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:32.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Jan 16 21:24:32.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:32.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:32.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:32.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:32.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:32.240: INFO: Jan 16 21:24:34.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:34.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:34.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:34.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Jan 16 21:24:34.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:34.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:34.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:34.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:34.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:34.240: INFO: Jan 16 21:24:36.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:36.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:36.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:36.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Jan 16 21:24:36.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:36.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:36.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:36.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:36.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:36.239: INFO: Jan 16 21:24:38.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:38.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:38.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:38.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Jan 16 21:24:38.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:38.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:38.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:38.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:38.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:38.239: INFO: Jan 16 21:24:40.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:40.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:40.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:40.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Jan 16 21:24:40.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:40.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:40.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:40.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:40.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:40.242: INFO: Jan 16 21:24:42.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:42.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:42.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:42.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Jan 16 21:24:42.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:42.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:42.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:42.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:42.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:42.243: INFO: Jan 16 21:24:44.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:44.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:44.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:44.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Jan 16 21:24:44.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:44.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:44.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:44.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:44.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:44.244: INFO: Jan 16 21:24:46.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:46.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:46.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:46.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Jan 16 21:24:46.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:46.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:46.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:46.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:46.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:46.240: INFO: Jan 16 21:24:48.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:48.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:48.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:48.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Jan 16 21:24:48.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:48.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:48.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:48.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:48.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:48.239: INFO: Jan 16 21:24:50.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:50.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:50.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:50.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Jan 16 21:24:50.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:50.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:50.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:50.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:50.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:50.239: INFO: Jan 16 21:24:52.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:52.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:52.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:52.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Jan 16 21:24:52.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:52.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:52.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:52.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:52.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:52.238: INFO: Jan 16 21:24:54.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:54.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:54.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:54.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Jan 16 21:24:54.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:54.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:54.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:54.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:54.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:54.238: INFO: Jan 16 21:24:56.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:56.249: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:56.249: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:56.249: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Jan 16 21:24:56.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:56.249: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:56.249: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:56.249: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:56.249: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:56.249: INFO: Jan 16 21:24:58.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:58.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:58.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:24:58.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Jan 16 21:24:58.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:24:58.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:24:58.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:58.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:58.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:24:58.240: INFO: Jan 16 21:25:00.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:00.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:00.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:00.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Jan 16 21:25:00.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:00.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:00.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:00.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:00.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:00.239: INFO: Jan 16 21:25:02.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:02.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:02.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:02.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Jan 16 21:25:02.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:02.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:02.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:02.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:02.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:02.238: INFO: Jan 16 21:25:04.255: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:04.255: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:04.255: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:04.255: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Jan 16 21:25:04.255: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:04.255: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:04.255: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:04.255: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:04.255: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:04.255: INFO: Jan 16 21:25:06.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:06.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:06.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:06.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Jan 16 21:25:06.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:06.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:06.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:06.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:06.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:06.238: INFO: Jan 16 21:25:08.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:08.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:08.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:08.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Jan 16 21:25:08.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:08.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:08.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:08.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:08.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:08.240: INFO: Jan 16 21:25:10.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:10.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:10.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:10.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Jan 16 21:25:10.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:10.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:10.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:10.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:10.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:10.238: INFO: Jan 16 21:25:12.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:12.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:12.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:12.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Jan 16 21:25:12.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:12.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:12.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:12.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:12.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:12.242: INFO: Jan 16 21:25:14.249: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:14.250: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:14.250: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:14.250: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Jan 16 21:25:14.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:14.250: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:14.250: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:14.250: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:14.250: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:14.250: INFO: Jan 16 21:25:16.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:16.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:16.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:16.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Jan 16 21:25:16.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:16.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:16.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:16.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:16.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:16.244: INFO: Jan 16 21:25:18.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:18.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:18.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:18.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Jan 16 21:25:18.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:18.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:18.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:18.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:18.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:18.240: INFO: Jan 16 21:25:20.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:20.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:20.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:20.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Jan 16 21:25:20.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:20.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:20.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:20.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:20.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:20.238: INFO: Jan 16 21:25:22.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:22.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:22.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:22.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Jan 16 21:25:22.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:22.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:22.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:22.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:22.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:22.241: INFO: Jan 16 21:25:24.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:24.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:24.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:24.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Jan 16 21:25:24.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:24.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:24.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:24.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:24.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:24.238: INFO: Jan 16 21:25:26.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:26.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:26.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:26.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Jan 16 21:25:26.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:26.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:26.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:26.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:26.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:26.241: INFO: Jan 16 21:25:28.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:28.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:28.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:28.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Jan 16 21:25:28.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:28.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:28.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:28.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:28.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:28.238: INFO: Jan 16 21:25:30.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:30.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:30.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:30.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Jan 16 21:25:30.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:30.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:30.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:30.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:30.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:30.240: INFO: Jan 16 21:25:32.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:32.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:32.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:32.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Jan 16 21:25:32.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:32.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:32.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:32.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:32.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:32.239: INFO: Jan 16 21:25:34.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:34.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:34.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:34.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Jan 16 21:25:34.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:34.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:34.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:34.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:34.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:34.247: INFO: Jan 16 21:25:36.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:36.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:36.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:36.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Jan 16 21:25:36.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:36.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:36.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:36.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:36.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:36.240: INFO: Jan 16 21:25:38.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:38.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:38.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:38.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Jan 16 21:25:38.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:38.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:38.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:38.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:38.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:38.240: INFO: Jan 16 21:25:40.237: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:40.237: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:40.237: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:40.237: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Jan 16 21:25:40.237: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:40.237: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:40.237: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:40.237: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:40.237: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:40.237: INFO: Jan 16 21:25:42.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:42.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:42.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:42.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Jan 16 21:25:42.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:42.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:42.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:42.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:42.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:42.243: INFO: Jan 16 21:25:44.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:44.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:44.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:44.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Jan 16 21:25:44.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:44.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:44.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:44.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:44.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:44.243: INFO: Jan 16 21:25:46.250: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:46.250: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:46.250: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:46.250: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Jan 16 21:25:46.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:46.250: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:46.250: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:46.250: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:46.250: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:46.250: INFO: Jan 16 21:25:48.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:48.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:48.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:48.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Jan 16 21:25:48.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:48.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:48.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:48.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:48.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:48.241: INFO: Jan 16 21:25:50.251: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:50.251: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:50.251: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:50.251: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Jan 16 21:25:50.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:50.251: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:50.251: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:50.251: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:50.251: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:50.251: INFO: Jan 16 21:25:52.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:52.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:52.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:52.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Jan 16 21:25:52.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:52.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:52.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:52.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:52.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:52.241: INFO: Jan 16 21:25:54.248: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:54.248: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:54.248: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:54.248: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Jan 16 21:25:54.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:54.248: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:54.248: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:54.248: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:54.248: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:54.248: INFO: Jan 16 21:25:56.251: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:56.251: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:56.251: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:56.251: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Jan 16 21:25:56.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:56.251: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:56.251: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:56.251: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:56.251: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:56.251: INFO: Jan 16 21:25:58.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:58.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:58.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:25:58.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Jan 16 21:25:58.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:25:58.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:25:58.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:58.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:58.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:25:58.239: INFO: Jan 16 21:26:00.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:00.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:00.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:00.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Jan 16 21:26:00.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:00.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:00.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:00.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:00.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:00.239: INFO: Jan 16 21:26:02.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:02.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:02.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:02.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Jan 16 21:26:02.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:02.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:02.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:02.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:02.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:02.241: INFO: Jan 16 21:26:04.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:04.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:04.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:04.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Jan 16 21:26:04.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:04.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:04.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:04.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:04.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:04.238: INFO: Jan 16 21:26:06.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:06.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:06.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:06.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Jan 16 21:26:06.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:06.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:06.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:06.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:06.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:06.240: INFO: Jan 16 21:26:08.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:08.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:08.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:08.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Jan 16 21:26:08.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:08.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:08.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:08.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:08.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:08.239: INFO: Jan 16 21:26:10.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:10.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:10.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:10.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Jan 16 21:26:10.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:10.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:10.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:10.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:10.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:10.240: INFO: Jan 16 21:26:12.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:12.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:12.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:12.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Jan 16 21:26:12.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:12.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:12.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:12.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:12.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:12.239: INFO: Jan 16 21:26:14.258: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:14.258: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:14.258: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:14.258: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Jan 16 21:26:14.258: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:14.258: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:14.258: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:14.258: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:14.258: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:14.258: INFO: Jan 16 21:26:16.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:16.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:16.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:16.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Jan 16 21:26:16.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:16.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:16.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:16.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:16.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:16.239: INFO: Jan 16 21:26:18.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:18.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:18.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:18.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Jan 16 21:26:18.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:18.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:18.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:18.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:18.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:18.241: INFO: Jan 16 21:26:20.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:20.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:20.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:20.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Jan 16 21:26:20.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:20.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:20.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:20.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:20.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:20.239: INFO: Jan 16 21:26:22.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:22.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:22.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:22.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Jan 16 21:26:22.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:22.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:22.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:22.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:22.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:22.241: INFO: Jan 16 21:26:24.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:24.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:24.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:24.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Jan 16 21:26:24.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:24.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:24.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:24.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:24.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:24.241: INFO: Jan 16 21:26:26.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:26.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:26.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:26.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Jan 16 21:26:26.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:26.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:26.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:26.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:26.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:26.241: INFO: Jan 16 21:26:28.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:28.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:28.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:28.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Jan 16 21:26:28.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:28.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:28.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:28.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:28.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:28.241: INFO: Jan 16 21:26:30.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:30.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:30.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:30.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Jan 16 21:26:30.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:30.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:30.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:30.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:30.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:30.241: INFO: Jan 16 21:26:32.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:32.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:32.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:32.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Jan 16 21:26:32.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:32.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:32.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:32.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:32.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:32.241: INFO: Jan 16 21:26:34.247: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:34.247: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:34.247: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:34.247: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Jan 16 21:26:34.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:34.247: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:34.247: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:34.247: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:34.247: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:34.247: INFO: Jan 16 21:26:36.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:36.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:36.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:36.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Jan 16 21:26:36.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:36.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:36.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:36.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:36.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:36.244: INFO: Jan 16 21:26:38.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:38.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:38.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:38.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Jan 16 21:26:38.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:38.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:38.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:38.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:38.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:38.240: INFO: Jan 16 21:26:40.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:40.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:40.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:40.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Jan 16 21:26:40.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:40.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:40.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:40.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:40.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:40.239: INFO: Jan 16 21:26:42.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:42.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:42.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:42.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Jan 16 21:26:42.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:42.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:42.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:42.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:42.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:42.239: INFO: Jan 16 21:26:44.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:44.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:44.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:44.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Jan 16 21:26:44.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:44.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:44.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:44.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:44.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:44.242: INFO: Jan 16 21:26:46.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:46.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:46.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:46.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Jan 16 21:26:46.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:46.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:46.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:46.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:46.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:46.244: INFO: Jan 16 21:26:48.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:48.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:48.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:48.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Jan 16 21:26:48.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:48.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:48.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:48.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:48.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:48.241: INFO: Jan 16 21:26:50.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:50.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:50.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:50.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Jan 16 21:26:50.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:50.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:50.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:50.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:50.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:50.238: INFO: Jan 16 21:26:52.237: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:52.237: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:52.237: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:52.237: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Jan 16 21:26:52.237: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:52.237: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:52.237: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:52.237: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:52.237: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:52.237: INFO: Jan 16 21:26:54.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:54.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:54.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:54.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Jan 16 21:26:54.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:54.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:54.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:54.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:54.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:54.239: INFO: Jan 16 21:26:56.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:56.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:56.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:56.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Jan 16 21:26:56.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:56.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:56.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:56.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:56.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:56.242: INFO: Jan 16 21:26:58.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:58.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:58.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:26:58.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Jan 16 21:26:58.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:26:58.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:26:58.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:58.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:58.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:26:58.243: INFO: Jan 16 21:27:00.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:00.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:00.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:00.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Jan 16 21:27:00.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:00.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:00.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:00.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:00.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:00.241: INFO: Jan 16 21:27:02.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:02.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:02.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:02.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Jan 16 21:27:02.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:02.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:02.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:02.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:02.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:02.240: INFO: Jan 16 21:27:04.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:04.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:04.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:04.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Jan 16 21:27:04.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:04.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:04.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:04.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:04.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:04.241: INFO: Jan 16 21:27:06.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:06.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:06.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:06.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Jan 16 21:27:06.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:06.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:06.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:06.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:06.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:06.239: INFO: Jan 16 21:27:08.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:08.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:08.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:08.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Jan 16 21:27:08.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:08.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:08.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:08.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:08.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:08.239: INFO: Jan 16 21:27:10.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:10.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:10.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:10.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Jan 16 21:27:10.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:10.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:10.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:10.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:10.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:10.239: INFO: Jan 16 21:27:12.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:12.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:12.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:12.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Jan 16 21:27:12.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:12.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:12.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:12.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:12.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:12.239: INFO: Jan 16 21:27:14.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:14.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:14.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:14.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Jan 16 21:27:14.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:14.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:14.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:14.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:14.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:14.238: INFO: Jan 16 21:27:16.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:16.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:16.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:16.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Jan 16 21:27:16.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:16.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:16.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:16.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:16.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:16.244: INFO: Jan 16 21:27:18.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:18.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:18.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:18.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Jan 16 21:27:18.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:18.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:18.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:18.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:18.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:18.239: INFO: Jan 16 21:27:20.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:20.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:20.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:20.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Jan 16 21:27:20.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:20.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:20.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:20.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:20.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:20.240: INFO: Jan 16 21:27:22.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:22.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:22.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:22.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Jan 16 21:27:22.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:22.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:22.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:22.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:22.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:22.239: INFO: Jan 16 21:27:24.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:24.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:24.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:24.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Jan 16 21:27:24.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:24.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:24.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:24.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:24.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:24.239: INFO: Jan 16 21:27:26.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:26.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:26.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:26.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Jan 16 21:27:26.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:26.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:26.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:26.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:26.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:26.239: INFO: Jan 16 21:27:28.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:28.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:28.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:28.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Jan 16 21:27:28.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:28.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:28.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:28.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:28.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:28.239: INFO: Jan 16 21:27:30.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:30.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:30.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:30.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Jan 16 21:27:30.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:30.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:30.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:30.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:30.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:30.238: INFO: Jan 16 21:27:32.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:32.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:32.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:32.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Jan 16 21:27:32.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:32.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:32.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:32.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:32.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:32.240: INFO: Jan 16 21:27:34.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:34.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:34.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:34.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Jan 16 21:27:34.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:34.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:34.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:34.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:34.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:34.240: INFO: Jan 16 21:27:36.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:36.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:36.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:36.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Jan 16 21:27:36.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:36.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:36.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:36.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:36.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:36.238: INFO: Jan 16 21:27:38.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:38.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:38.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:38.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Jan 16 21:27:38.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:38.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:38.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:38.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:38.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:38.238: INFO: Jan 16 21:27:40.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:40.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:40.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:40.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Jan 16 21:27:40.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:40.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:40.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:40.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:40.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:40.239: INFO: Jan 16 21:27:42.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:42.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:42.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:42.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Jan 16 21:27:42.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:42.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:42.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:42.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:42.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:42.241: INFO: Jan 16 21:27:44.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:44.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:44.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:44.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Jan 16 21:27:44.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:44.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:44.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:44.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:44.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:44.243: INFO: Jan 16 21:27:46.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:46.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:46.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:46.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Jan 16 21:27:46.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:46.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:46.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:46.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:46.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:46.238: INFO: Jan 16 21:27:48.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:48.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:48.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:48.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Jan 16 21:27:48.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:48.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:48.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:48.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:48.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:48.242: INFO: Jan 16 21:27:50.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:50.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:50.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:50.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Jan 16 21:27:50.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:50.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:50.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:50.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:50.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:50.239: INFO: Jan 16 21:27:52.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:52.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:52.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:52.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Jan 16 21:27:52.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:52.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:52.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:52.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:52.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:52.244: INFO: Jan 16 21:27:54.243: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:54.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:54.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:54.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Jan 16 21:27:54.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:54.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:54.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:54.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:54.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:54.243: INFO: Jan 16 21:27:56.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:56.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:56.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:56.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Jan 16 21:27:56.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:56.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:56.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:56.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:56.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:56.240: INFO: Jan 16 21:27:58.244: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:58.244: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:58.244: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:27:58.244: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Jan 16 21:27:58.244: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:27:58.244: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:27:58.244: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:58.244: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:58.244: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:27:58.244: INFO: Jan 16 21:28:00.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:00.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:00.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:00.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Jan 16 21:28:00.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:00.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:00.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:00.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:00.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:00.240: INFO: Jan 16 21:28:02.237: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:02.237: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:02.237: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:02.237: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Jan 16 21:28:02.237: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:02.237: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:02.237: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:02.237: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:02.237: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:02.237: INFO: Jan 16 21:28:04.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:04.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:04.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:04.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Jan 16 21:28:04.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:04.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:04.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:04.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:04.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:04.240: INFO: Jan 16 21:28:06.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:06.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:06.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:06.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Jan 16 21:28:06.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:06.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:06.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:06.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:06.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:06.239: INFO: Jan 16 21:28:08.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:08.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:08.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:08.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Jan 16 21:28:08.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:08.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:08.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:08.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:08.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:08.238: INFO: Jan 16 21:28:10.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:10.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:10.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:10.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Jan 16 21:28:10.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:10.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:10.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:10.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:10.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:10.240: INFO: Jan 16 21:28:12.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:12.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:12.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:12.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Jan 16 21:28:12.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:12.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:12.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:12.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:12.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:12.241: INFO: Jan 16 21:28:14.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:14.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:14.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:14.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Jan 16 21:28:14.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:14.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:14.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:14.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:14.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:14.238: INFO: Jan 16 21:28:16.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:16.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:16.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:16.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Jan 16 21:28:16.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:16.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:16.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:16.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:16.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:16.239: INFO: Jan 16 21:28:18.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:18.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:18.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:18.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Jan 16 21:28:18.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:18.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:18.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:18.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:18.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:18.238: INFO: Jan 16 21:28:20.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:20.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:20.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:20.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Jan 16 21:28:20.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:20.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:20.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:20.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:20.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:20.238: INFO: Jan 16 21:28:22.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:22.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:22.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:22.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Jan 16 21:28:22.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:22.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:22.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:22.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:22.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:22.239: INFO: Jan 16 21:28:24.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:24.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:24.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:24.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Jan 16 21:28:24.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:24.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:24.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:24.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:24.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:24.239: INFO: Jan 16 21:28:26.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:26.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:26.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:26.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Jan 16 21:28:26.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:26.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:26.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:26.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:26.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:26.239: INFO: Jan 16 21:28:28.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:28.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:28.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:28.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Jan 16 21:28:28.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:28.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:28.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:28.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:28.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:28.241: INFO: Jan 16 21:28:30.245: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:30.245: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:30.245: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:30.245: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Jan 16 21:28:30.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:30.245: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:30.245: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:30.245: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:30.245: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:30.245: INFO: Jan 16 21:28:32.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:32.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:32.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:32.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Jan 16 21:28:32.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:32.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:32.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:32.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:32.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:32.240: INFO: Jan 16 21:28:34.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:34.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:34.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:34.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Jan 16 21:28:34.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:34.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:34.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:34.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:34.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:34.238: INFO: Jan 16 21:28:36.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:36.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:36.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:36.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Jan 16 21:28:36.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:36.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:36.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:36.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:36.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:36.241: INFO: Jan 16 21:28:38.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:38.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:38.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:38.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Jan 16 21:28:38.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:38.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:38.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:38.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:38.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:38.241: INFO: Jan 16 21:28:40.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:40.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:40.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:40.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Jan 16 21:28:40.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:40.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:40.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:40.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:40.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:40.240: INFO: Jan 16 21:28:42.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:42.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:42.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:42.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Jan 16 21:28:42.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:42.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:42.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:42.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:42.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:42.240: INFO: Jan 16 21:28:44.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:44.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:44.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:44.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Jan 16 21:28:44.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:44.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:44.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:44.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:44.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:44.240: INFO: Jan 16 21:28:46.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:46.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:46.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:46.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Jan 16 21:28:46.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:46.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:46.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:46.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:46.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:46.240: INFO: Jan 16 21:28:48.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:48.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:48.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:48.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Jan 16 21:28:48.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:48.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:48.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:48.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:48.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:48.238: INFO: Jan 16 21:28:50.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:50.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:50.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:50.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Jan 16 21:28:50.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:50.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:50.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:50.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:50.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:50.238: INFO: Jan 16 21:28:52.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:52.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:52.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:52.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Jan 16 21:28:52.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:52.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:52.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:52.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:52.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:52.241: INFO: Jan 16 21:28:54.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:54.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:54.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:54.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Jan 16 21:28:54.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:54.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:54.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:54.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:54.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:54.239: INFO: Jan 16 21:28:56.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:56.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:56.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:56.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Jan 16 21:28:56.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:56.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:56.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:56.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:56.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:56.238: INFO: Jan 16 21:28:58.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:58.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:58.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:28:58.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Jan 16 21:28:58.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:28:58.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:28:58.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:58.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:58.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:28:58.239: INFO: Jan 16 21:29:00.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:00.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:00.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:00.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Jan 16 21:29:00.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:00.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:00.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:00.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:00.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:00.238: INFO: Jan 16 21:29:02.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:02.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:02.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:02.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Jan 16 21:29:02.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:02.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:02.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:02.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:02.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:02.238: INFO: Jan 16 21:29:04.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:04.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:04.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:04.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Jan 16 21:29:04.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:04.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:04.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:04.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:04.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:04.239: INFO: Jan 16 21:29:06.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:06.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:06.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:06.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Jan 16 21:29:06.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:06.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:06.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:06.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:06.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:06.240: INFO: Jan 16 21:29:08.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:08.243: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:08.243: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:08.243: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Jan 16 21:29:08.243: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:08.243: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:08.243: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:08.243: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:08.243: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:08.243: INFO: Jan 16 21:29:10.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:10.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:10.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:10.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Jan 16 21:29:10.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:10.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:10.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:10.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:10.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:10.241: INFO: Jan 16 21:29:12.246: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:12.246: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:12.246: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:12.246: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Jan 16 21:29:12.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:12.246: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:12.246: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:12.246: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:12.246: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:12.246: INFO: Jan 16 21:29:14.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:14.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:14.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:14.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Jan 16 21:29:14.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:14.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:14.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:14.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:14.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:14.239: INFO: Jan 16 21:29:16.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:16.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:16.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:16.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Jan 16 21:29:16.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:16.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:16.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:16.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:16.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:16.240: INFO: Jan 16 21:29:18.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:18.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:18.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:18.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Jan 16 21:29:18.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:18.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:18.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:18.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:18.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:18.238: INFO: Jan 16 21:29:20.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:20.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:20.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:20.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Jan 16 21:29:20.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:20.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:20.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:20.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:20.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:20.240: INFO: Jan 16 21:29:22.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:22.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:22.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:22.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Jan 16 21:29:22.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:22.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:22.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:22.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:22.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:22.241: INFO: Jan 16 21:29:24.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:24.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:24.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:24.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Jan 16 21:29:24.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:24.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:24.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:24.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:24.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:24.240: INFO: Jan 16 21:29:26.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:26.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:26.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:26.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Jan 16 21:29:26.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:26.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:26.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:26.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:26.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:26.241: INFO: Jan 16 21:29:28.238: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:28.238: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:28.238: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:28.238: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Jan 16 21:29:28.238: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:28.238: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:28.238: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:28.238: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:28.238: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:28.238: INFO: Jan 16 21:29:30.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:30.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:30.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:30.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Jan 16 21:29:30.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:30.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:30.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:30.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:30.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:30.239: INFO: Jan 16 21:29:32.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:32.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:32.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:32.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Jan 16 21:29:32.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:32.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:32.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:32.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:32.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:32.240: INFO: Jan 16 21:29:34.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:34.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:34.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:34.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Jan 16 21:29:34.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:34.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:34.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:34.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:34.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:34.241: INFO: Jan 16 21:29:36.240: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:36.240: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:36.240: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:36.240: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Jan 16 21:29:36.240: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:36.240: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:36.240: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:36.240: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:36.240: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:36.240: INFO: Jan 16 21:29:38.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:38.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:38.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:38.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Jan 16 21:29:38.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:38.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:38.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:38.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:38.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:38.239: INFO: Jan 16 21:29:40.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:40.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:40.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:40.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Jan 16 21:29:40.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:40.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:40.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:40.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:40.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:40.242: INFO: Jan 16 21:29:42.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:42.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:42.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:42.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Jan 16 21:29:42.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:42.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:42.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:42.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:42.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:42.241: INFO: Jan 16 21:29:44.241: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:44.241: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:44.241: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:44.241: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Jan 16 21:29:44.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:44.241: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:44.241: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:44.241: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:44.241: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:44.241: INFO: Jan 16 21:29:46.242: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:46.242: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:46.242: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:46.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Jan 16 21:29:46.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:46.242: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:46.242: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:46.242: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:46.242: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:46.242: INFO: Jan 16 21:29:48.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:48.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:48.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:48.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Jan 16 21:29:48.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:48.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:48.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:48.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:48.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:48.239: INFO: Jan 16 21:29:50.239: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:50.239: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:50.239: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:50.239: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 16 21:29:50.239: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:50.239: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:50.239: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.239: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.239: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.239: INFO: Jan 16 21:29:50.368: INFO: The status of Pod kube-apiserver-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:50.368: INFO: The status of Pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:50.368: INFO: The status of Pod kube-scheduler-capz-conf-le680f-control-plane-zdszh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 16 21:29:50.368: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 16 21:29:50.368: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 16 21:29:50.368: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:50.368: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.368: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.368: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.368: INFO: STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/16/23 21:29:50.368 STEP: Found 116 events. - test/e2e/framework/debug/dump.go:46 @ 01/16/23 21:29:50.421 Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:37 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-le680f-control-plane-zdszh_e8145ca1-03f7-400a-adf9-9a3f4aa3f2d4 became leader Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:38 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-le680f-control-plane-zdszh_1ea36c05-733e-4f2d-89b8-5bd7d60c382d became leader Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:42 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-xnkx8 Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:42 +0000 UTC - event for kube-proxy-xnkx8: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-xnkx8 to capz-conf-le680f-control-plane-zdszh Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:43 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2 Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:43 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-5vkgx Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:43 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-dxwgb Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:43 +0000 UTC - event for coredns-56f4c55bf9-5vkgx: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:43 +0000 UTC - event for coredns-56f4c55bf9-dxwgb: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:43 +0000 UTC - event for etcd-capz-conf-le680f-control-plane-zdszh: {node-controller } NodeNotReady: Node is not ready Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:43 +0000 UTC - event for kube-proxy-xnkx8: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:45 +0000 UTC - event for kube-proxy-xnkx8: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14" in 1.460302022s (1.460446063s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:45 +0000 UTC - event for kube-proxy-xnkx8: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container kube-proxy Jan 16 21:29:50.421: INFO: At 2023-01-16 21:16:45 +0000 UTC - event for kube-proxy-xnkx8: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container kube-proxy Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:04 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:04 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-t785x Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:04 +0000 UTC - event for metrics-server-c9574f845-t785x: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:17 +0000 UTC - event for coredns-56f4c55bf9-5vkgx: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-5vkgx to capz-conf-le680f-control-plane-zdszh Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:17 +0000 UTC - event for metrics-server-c9574f845-t785x: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-t785x to capz-conf-le680f-control-plane-zdszh Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:19 +0000 UTC - event for coredns-56f4c55bf9-5vkgx: {kubelet capz-conf-le680f-control-plane-zdszh} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "68b2ad2c2b179e5f2e42bcf69c73e13e90ad6c2c4c571ddf2d6a731f2abebad9": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:19 +0000 UTC - event for coredns-56f4c55bf9-dxwgb: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-dxwgb to capz-conf-le680f-control-plane-zdszh Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:22 +0000 UTC - event for coredns-56f4c55bf9-dxwgb: {kubelet capz-conf-le680f-control-plane-zdszh} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "8c97454f4cf55c5ed3490944531de16abee9f30553176413ce19d655171b0acc": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:22 +0000 UTC - event for metrics-server-c9574f845-t785x: {kubelet capz-conf-le680f-control-plane-zdszh} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "be6cffab5eef1089d2d14bb99136fb9e582ff1f669496db1e72a85024cc38e52": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:38 +0000 UTC - event for coredns-56f4c55bf9-5vkgx: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:38 +0000 UTC - event for coredns-56f4c55bf9-5vkgx: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container coredns Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:39 +0000 UTC - event for coredns-56f4c55bf9-5vkgx: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container coredns Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:39 +0000 UTC - event for coredns-56f4c55bf9-dxwgb: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container coredns Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:39 +0000 UTC - event for coredns-56f4c55bf9-dxwgb: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:40 +0000 UTC - event for coredns-56f4c55bf9-dxwgb: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container coredns Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:40 +0000 UTC - event for metrics-server-c9574f845-t785x: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:50 +0000 UTC - event for metrics-server-c9574f845-t785x: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.675664575s (10.451372036s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:50 +0000 UTC - event for metrics-server-c9574f845-t785x: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container metrics-server Jan 16 21:29:50.421: INFO: At 2023-01-16 21:17:50 +0000 UTC - event for metrics-server-c9574f845-t785x: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container metrics-server Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:11 +0000 UTC - event for csi-azuredisk-controller: {deployment-controller } ScalingReplicaSet: Scaled up replica set csi-azuredisk-controller-7c87ff77db to 1 Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:11 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db: {replicaset-controller } SuccessfulCreate: Created pod: csi-azuredisk-controller-7c87ff77db-l5w7c Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:11 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-controller-7c87ff77db-l5w7c to capz-conf-le680f-control-plane-zdszh Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:11 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-6nbdr Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:11 +0000 UTC - event for csi-azuredisk-node-6nbdr: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-6nbdr to capz-conf-le680f-control-plane-zdszh Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:12 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:12 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:13 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container liveness-probe Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:13 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container liveness-probe Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:13 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 1.076716497s (1.0768996s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:13 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:17 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0" in 4.623995234s (5.564081201s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:18 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:18 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container csi-provisioner Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:18 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container csi-provisioner Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:19 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container node-driver-registrar Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:19 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:19 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container node-driver-registrar Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:19 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 1.136719094s (5.404624627s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:21 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0" in 2.681087861s (3.426455995s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:21 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container csi-attacher Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container csi-attacher Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:39 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container azuredisk Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:39 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container azuredisk Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:39 +0000 UTC - event for csi-azuredisk-node-6nbdr: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 17.490014254s (19.854373819s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:42 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:42 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container csi-snapshotter Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:42 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container csi-snapshotter Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:42 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1" in 2.843853653s (18.792937805s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0" in 4.240422256s (4.240429757s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container csi-resizer Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container csi-resizer Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" already present on machine Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container liveness-probe Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container liveness-probe Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" already present on machine Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-6bqcb Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for csi-azuredisk-node-6bqcb: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-6bqcb to capz-conf-le680f-md-0-8xdts Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-mnpqw Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:46 +0000 UTC - event for kube-proxy-mnpqw: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-mnpqw to capz-conf-le680f-md-0-8xdts Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:47 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Created: Created container azuredisk Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:47 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-l5w7c: {kubelet capz-conf-le680f-control-plane-zdszh} Started: Started container azuredisk Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:47 +0000 UTC - event for external-attacher-leader-disk-csi-azure-com: {external-attacher-leader-disk.csi.azure.com/capz-conf-le680f-control-plane-zdszh } LeaderElection: capz-conf-le680f-control-plane-zdszh became leader Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:47 +0000 UTC - event for external-resizer-disk-csi-azure-com: {external-resizer-disk-csi-azure-com/capz-conf-le680f-control-plane-zdszh } LeaderElection: capz-conf-le680f-control-plane-zdszh became leader Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:48 +0000 UTC - event for disk-csi-azure-com: {disk.csi.azure.com/1673903927991-8081-disk.csi.azure.com } LeaderElection: 1673903927991-8081-disk-csi-azure-com became leader Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:48 +0000 UTC - event for external-snapshotter-leader-disk-csi-azure-com: {external-snapshotter-leader-disk.csi.azure.com/capz-conf-le680f-control-plane-zdszh } LeaderElection: capz-conf-le680f-control-plane-zdszh became leader Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:51 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-r2t76 Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:51 +0000 UTC - event for csi-azuredisk-node-r2t76: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-r2t76 to capz-conf-le680f-md-0-mlc8p Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:51 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-4qgks Jan 16 21:29:50.421: INFO: At 2023-01-16 21:18:51 +0000 UTC - event for kube-proxy-4qgks: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-4qgks to capz-conf-le680f-md-0-mlc8p Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:00 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:00 +0000 UTC - event for kube-proxy-mnpqw: {kubelet capz-conf-le680f-md-0-8xdts} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:01 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:01 +0000 UTC - event for kube-proxy-4qgks: {kubelet capz-conf-le680f-md-0-mlc8p} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:02 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:02 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Created: Created container liveness-probe Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:02 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Started: Started container liveness-probe Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:02 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 889.31904ms (889.447643ms including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:02 +0000 UTC - event for kube-proxy-mnpqw: {kubelet capz-conf-le680f-md-0-8xdts} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14" in 1.556103816s (1.556202254s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:02 +0000 UTC - event for kube-proxy-mnpqw: {kubelet capz-conf-le680f-md-0-8xdts} Created: Created container kube-proxy Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:02 +0000 UTC - event for kube-proxy-mnpqw: {kubelet capz-conf-le680f-md-0-8xdts} Started: Started container kube-proxy Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:03 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:03 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 1.148600416s (2.699285697s including waiting) Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:03 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Created: Created container liveness-probe Jan 16 21:29:50.421: INFO: At 2023-01-16 21:19:03 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Started: Started container liveness-probe Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:07 +0000 UTC - event for kube-proxy-4qgks: {kubelet capz-conf-le680f-md-0-mlc8p} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14" in 3.046599379s (5.82392686s including waiting) Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:07 +0000 UTC - event for kube-proxy-4qgks: {kubelet capz-conf-le680f-md-0-mlc8p} Started: Started container kube-proxy Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:07 +0000 UTC - event for kube-proxy-4qgks: {kubelet capz-conf-le680f-md-0-mlc8p} Created: Created container kube-proxy Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:08 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:08 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 956.022879ms (5.664942649s including waiting) Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:08 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Created: Created container node-driver-registrar Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:08 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Started: Started container node-driver-registrar Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:13 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Created: Created container node-driver-registrar Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:13 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Started: Started container node-driver-registrar Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:13 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:13 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 1.07838845s (9.523060025s including waiting) Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:35 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Started: Started container azuredisk Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:35 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 21.504639265s (26.720160294s including waiting) Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:35 +0000 UTC - event for csi-azuredisk-node-r2t76: {kubelet capz-conf-le680f-md-0-mlc8p} Created: Created container azuredisk Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:39 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 20.507353675s (26.070123943s including waiting) Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:39 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Started: Started container azuredisk Jan 16 21:29:50.422: INFO: At 2023-01-16 21:19:39 +0000 UTC - event for csi-azuredisk-node-6bqcb: {kubelet capz-conf-le680f-md-0-8xdts} Created: Created container azuredisk Jan 16 21:29:50.473: INFO: POD NODE PHASE GRACE CONDITIONS Jan 16 21:29:50.473: INFO: coredns-56f4c55bf9-5vkgx capz-conf-le680f-control-plane-zdszh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:17 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:39 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:39 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:17 +0000 UTC }] Jan 16 21:29:50.473: INFO: coredns-56f4c55bf9-dxwgb capz-conf-le680f-control-plane-zdszh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:40 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:40 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:17 +0000 UTC }] Jan 16 21:29:50.473: INFO: csi-azuredisk-controller-7c87ff77db-l5w7c capz-conf-le680f-control-plane-zdszh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:11 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:11 +0000 UTC }] Jan 16 21:29:50.473: INFO: csi-azuredisk-node-6bqcb capz-conf-le680f-md-0-8xdts Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:19:40 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:19:40 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:46 +0000 UTC }] Jan 16 21:29:50.473: INFO: csi-azuredisk-node-6nbdr capz-conf-le680f-control-plane-zdszh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:11 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:40 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:40 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:11 +0000 UTC }] Jan 16 21:29:50.473: INFO: csi-azuredisk-node-r2t76 capz-conf-le680f-md-0-mlc8p Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:57 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:19:35 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:19:35 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:51 +0000 UTC }] Jan 16 21:29:50.473: INFO: etcd-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:16:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:16:41 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:16:41 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:16:39 +0000 UTC }] Jan 16 21:29:50.473: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.473: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.473: INFO: kube-proxy-4qgks capz-conf-le680f-md-0-mlc8p Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:57 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:19:07 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:19:07 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:51 +0000 UTC }] Jan 16 21:29:50.473: INFO: kube-proxy-mnpqw capz-conf-le680f-md-0-8xdts Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:19:02 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:19:02 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:46 +0000 UTC }] Jan 16 21:29:50.473: INFO: kube-proxy-xnkx8 capz-conf-le680f-control-plane-zdszh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:16:42 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:16:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:16:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:16:42 +0000 UTC }] Jan 16 21:29:50.473: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] Jan 16 21:29:50.473: INFO: metrics-server-c9574f845-t785x capz-conf-le680f-control-plane-zdszh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:11 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:18:11 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 21:17:17 +0000 UTC }] Jan 16 21:29:50.473: INFO: Jan 16 21:29:52.365: INFO: Logging node info for node capz-conf-le680f-control-plane-zdszh Jan 16 21:29:52.556: INFO: Node Info: &Node{ObjectMeta:{capz-conf-le680f-control-plane-zdszh e2c8cfe5-ce41-4c45-9020-0c420cf72bcd 3152 0 2023-01-16 21:16:35 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus failure-domain.beta.kubernetes.io/zone:eastus-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-le680f-control-plane-zdszh kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone:eastus-3 topology.kubernetes.io/region:eastus topology.kubernetes.io/zone:eastus-3] map[cluster.x-k8s.io/cluster-name:capz-conf-le680f cluster.x-k8s.io/cluster-namespace:capz-conf-le680f cluster.x-k8s.io/machine:capz-conf-le680f-control-plane-kst8f cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-le680f-control-plane csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-le680f-control-plane-zdszh","disk.csi.azure.com":"capz-conf-le680f-control-plane-zdszh"} 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.11.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-16 21:16: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 2023-01-16 21:16:37 +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 2023-01-16 21:17:00 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2023-01-16 21:17:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {calico-node Update v1 2023-01-16 21:17:31 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-16 21:29:23 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-le680f/providers/Microsoft.Compute/virtualMachines/capz-conf-le680f-control-plane-zdszh,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/control-plane,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123181056 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018323456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 21:17:31 +0000 UTC,LastTransitionTime:2023-01-16 21:17:31 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 21:29:23 +0000 UTC,LastTransitionTime:2023-01-16 21:16:18 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 21:29:23 +0000 UTC,LastTransitionTime:2023-01-16 21:16:18 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 21:29:23 +0000 UTC,LastTransitionTime:2023-01-16 21:16:18 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 21:29:23 +0000 UTC,LastTransitionTime:2023-01-16 21:17:17 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-le680f-control-plane-zdszh,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:c9fe5aa370a64460ae758fb5120bfb64,SystemUUID:5269925e-01f1-8d4c-bd08-f58dfab4fb67,BootID:4b91cdd0-232c-41ff-9821-1cc5ba0de976,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1007+e7406b4abe5d14,KubeProxyVersion:v1.27.0-alpha.0.1007+e7406b4abe5d14,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner@sha256:3ef7d954946bd1cf9e5e3564a8d1acf8e5852616f7ae96bcbc5ced8c275483ee mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0],SizeBytes:61391360,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-resizer@sha256:9ba6483d2f8aa6051cb3a50e42d638fc17a6e4699a6689f054969024b7c12944 mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0],SizeBytes:58560473,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-attacher@sha256:bc317fea7e7bbaff65130d7ac6ea7c96bc15eb1f086374b8c3359f11988ac024 mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0],SizeBytes:57948644,},ContainerImage{Names:[docker.io/calico/apiserver@sha256:9819c1b569e60eec4dbab82c1b41cee80fe8af282b25ba2c174b2a00ae555af6 docker.io/calico/apiserver:v3.25.0],SizeBytes:35624155,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:539d876fd1bcefbbf39606df09ed065db1cf6f537ccf8e39344271092e7cb860 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.1001_62d7937b2e8175],SizeBytes:35446858,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:2fd6074ef1e432863bd4b98269943fe2f11fef4fd28049e96b7aa207eda0f6d3 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.1001_62d7937b2e8175],SizeBytes:32311072,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:c45af3a9692d87a527451cf544557138fedf86f92b6e39bf2003e2fdb848dce3 docker.io/calico/kube-controllers:v3.25.0],SizeBytes:31271800,},ContainerImage{Names:[docker.io/calico/typha@sha256:f7e0557e03f422c8ba5fcf64ef0fac054ee99935b5d101a0a50b5e9b65f6a5c5 docker.io/calico/typha:v3.25.0],SizeBytes:28533187,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter@sha256:a889e925e15f9423f7842f1b769f64cbcf6a20b6956122836fc835cf22d9073f mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1],SizeBytes:22192414,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:89851769b32a5ed73f821e6f315c2edbe4f89decd7ba01caf07223680ab0e235 gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.1001_62d7937b2e8175],SizeBytes:21485038,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:f89612e6223ff228aa2279a23971aa8966baf934e4ac5d5012090e87d6c8db7c capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14],SizeBytes:21483010,},ContainerImage{Names:[quay.io/tigera/operator@sha256:89eef35e1bbe8c88792ce69c3f3f38fb9838e58602c570524350b5f3ab127582 quay.io/tigera/operator:v1.29.0],SizeBytes:21108896,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:77dc2b789eab47dbb36c0c85236010bd50728181269e63371f5f4b634b5198da gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.1001_62d7937b2e8175],SizeBytes:17469386,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 16 21:29:52.556: INFO: Logging kubelet events for node capz-conf-le680f-control-plane-zdszh Jan 16 21:29:52.754: INFO: Logging pods the kubelet thinks is on node capz-conf-le680f-control-plane-zdszh Jan 16 21:29:52.974: INFO: csi-azuredisk-controller-7c87ff77db-l5w7c started at 2023-01-16 21:18:11 +0000 UTC (0+6 container statuses recorded) Jan 16 21:29:52.974: INFO: Container azuredisk ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container csi-attacher ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container csi-provisioner ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container csi-resizer ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container csi-snapshotter ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container liveness-probe ready: true, restart count 0 Jan 16 21:29:52.974: INFO: kube-controller-manager-capz-conf-le680f-control-plane-zdszh started at <nil> (0+0 container statuses recorded) Jan 16 21:29:52.974: INFO: calico-node-zg6l9 started at 2023-01-16 21:16:51 +0000 UTC (2+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Init container flexvol-driver ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Init container install-cni ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container calico-node ready: true, restart count 0 Jan 16 21:29:52.974: INFO: calico-kube-controllers-6b7b9c649d-4phll started at 2023-01-16 21:17:19 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container calico-kube-controllers ready: true, restart count 0 Jan 16 21:29:52.974: INFO: csi-azuredisk-node-6nbdr started at 2023-01-16 21:18:11 +0000 UTC (0+3 container statuses recorded) Jan 16 21:29:52.974: INFO: Container azuredisk ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container liveness-probe ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 16 21:29:52.974: INFO: kube-scheduler-capz-conf-le680f-control-plane-zdszh started at <nil> (0+0 container statuses recorded) Jan 16 21:29:52.974: INFO: csi-node-driver-6w6vs started at 2023-01-16 21:17:21 +0000 UTC (0+2 container statuses recorded) Jan 16 21:29:52.974: INFO: Container calico-csi ready: true, restart count 0 Jan 16 21:29:52.974: INFO: Container csi-node-driver-registrar ready: true, restart count 0 Jan 16 21:29:52.974: INFO: coredns-56f4c55bf9-dxwgb started at 2023-01-16 21:17:19 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container coredns ready: true, restart count 0 Jan 16 21:29:52.974: INFO: calico-apiserver-789874bb44-ntwpp started at 2023-01-16 21:17:51 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container calico-apiserver ready: true, restart count 0 Jan 16 21:29:52.974: INFO: etcd-capz-conf-le680f-control-plane-zdszh started at 2023-01-16 21:16:39 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container etcd ready: true, restart count 0 Jan 16 21:29:52.974: INFO: calico-typha-7b7dd5699c-fjcxx started at 2023-01-16 21:16:51 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container calico-typha ready: true, restart count 0 Jan 16 21:29:52.974: INFO: coredns-56f4c55bf9-5vkgx started at 2023-01-16 21:17:17 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container coredns ready: true, restart count 0 Jan 16 21:29:52.974: INFO: metrics-server-c9574f845-t785x started at 2023-01-16 21:17:19 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container metrics-server ready: true, restart count 0 Jan 16 21:29:52.974: INFO: kube-apiserver-capz-conf-le680f-control-plane-zdszh started at <nil> (0+0 container statuses recorded) Jan 16 21:29:52.974: INFO: kube-proxy-xnkx8 started at 2023-01-16 21:16:42 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container kube-proxy ready: true, restart count 0 Jan 16 21:29:52.974: INFO: tigera-operator-54b47459dd-whbfv started at 2023-01-16 21:16:43 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container tigera-operator ready: true, restart count 0 Jan 16 21:29:52.974: INFO: calico-apiserver-789874bb44-6tzlc started at 2023-01-16 21:17:51 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:52.974: INFO: Container calico-apiserver ready: true, restart count 0 Jan 16 21:29:53.617: INFO: Latency metrics for node capz-conf-le680f-control-plane-zdszh Jan 16 21:29:53.617: INFO: Logging node info for node capz-conf-le680f-md-0-8xdts Jan 16 21:29:53.754: INFO: Node Info: &Node{ObjectMeta:{capz-conf-le680f-md-0-8xdts 05444bfe-7a7f-4117-82f9-082da5badb91 2461 0 2023-01-16 21:18:46 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-le680f-md-0-8xdts kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:eastus topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-le680f cluster.x-k8s.io/cluster-namespace:capz-conf-le680f cluster.x-k8s.io/machine:capz-conf-le680f-md-0-cb797cbfc-rsxb5 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-le680f-md-0-cb797cbfc csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-le680f-md-0-8xdts","disk.csi.azure.com":"capz-conf-le680f-md-0-8xdts"} kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.5/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.206.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-16 21:18:46 +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 2023-01-16 21:18:47 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {manager Update v1 2023-01-16 21:19:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2023-01-16 21:19:29 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {calico-node Update v1 2023-01-16 21:19:50 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-16 21:25:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-le680f/providers/Microsoft.Compute/virtualMachines/capz-conf-le680f-md-0-8xdts,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123181056 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018323456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 21:19:50 +0000 UTC,LastTransitionTime:2023-01-16 21:19:50 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 21:25:14 +0000 UTC,LastTransitionTime:2023-01-16 21:18:46 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 21:25:14 +0000 UTC,LastTransitionTime:2023-01-16 21:18:46 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 21:25:14 +0000 UTC,LastTransitionTime:2023-01-16 21:18:46 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 21:25:14 +0000 UTC,LastTransitionTime:2023-01-16 21:19:29 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-le680f-md-0-8xdts,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:604c33e219ae498680679d273f0c42e0,SystemUUID:799a4e33-cd7d-944f-a2d7-2df110fb5866,BootID:7abef19d-85fb-4c42-ac60-30e412e5f6fc,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1007+e7406b4abe5d14,KubeProxyVersion:v1.27.0-alpha.0.1007+e7406b4abe5d14,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[docker.io/calico/typha@sha256:f7e0557e03f422c8ba5fcf64ef0fac054ee99935b5d101a0a50b5e9b65f6a5c5 docker.io/calico/typha:v3.25.0],SizeBytes:28533187,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:adc0d8c9bc694b1a2486ca24880f8e1d3c7750268174d4414de668b166f99629 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14],SizeBytes:21483003,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 16 21:29:53.754: INFO: Logging kubelet events for node capz-conf-le680f-md-0-8xdts Jan 16 21:29:53.955: INFO: Logging pods the kubelet thinks is on node capz-conf-le680f-md-0-8xdts Jan 16 21:29:54.164: INFO: kube-proxy-mnpqw started at 2023-01-16 21:18:53 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:54.164: INFO: Container kube-proxy ready: true, restart count 0 Jan 16 21:29:54.164: INFO: calico-typha-7b7dd5699c-xsjq7 started at 2023-01-16 21:19:00 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:54.164: INFO: Container calico-typha ready: true, restart count 0 Jan 16 21:29:54.164: INFO: csi-node-driver-hpv5n started at 2023-01-16 21:19:29 +0000 UTC (0+2 container statuses recorded) Jan 16 21:29:54.164: INFO: Container calico-csi ready: true, restart count 0 Jan 16 21:29:54.164: INFO: Container csi-node-driver-registrar ready: true, restart count 0 Jan 16 21:29:54.164: INFO: calico-node-bb4ng started at 2023-01-16 21:18:53 +0000 UTC (2+1 container statuses recorded) Jan 16 21:29:54.164: INFO: Init container flexvol-driver ready: true, restart count 0 Jan 16 21:29:54.164: INFO: Init container install-cni ready: true, restart count 0 Jan 16 21:29:54.164: INFO: Container calico-node ready: true, restart count 0 Jan 16 21:29:54.164: INFO: csi-azuredisk-node-6bqcb started at 2023-01-16 21:18:53 +0000 UTC (0+3 container statuses recorded) Jan 16 21:29:54.164: INFO: Container azuredisk ready: true, restart count 0 Jan 16 21:29:54.164: INFO: Container liveness-probe ready: true, restart count 0 Jan 16 21:29:54.164: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 16 21:29:54.789: INFO: Latency metrics for node capz-conf-le680f-md-0-8xdts Jan 16 21:29:54.789: INFO: Logging node info for node capz-conf-le680f-md-0-mlc8p Jan 16 21:29:54.954: INFO: Node Info: &Node{ObjectMeta:{capz-conf-le680f-md-0-mlc8p 5be77c70-1f71-4ced-861e-69f66e037735 2478 0 2023-01-16 21:18:49 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-le680f-md-0-mlc8p kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:eastus topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-le680f cluster.x-k8s.io/cluster-namespace:capz-conf-le680f cluster.x-k8s.io/machine:capz-conf-le680f-md-0-cb797cbfc-z9b4q cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-le680f-md-0-cb797cbfc csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-le680f-md-0-mlc8p","disk.csi.azure.com":"capz-conf-le680f-md-0-mlc8p"} kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.178.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-16 21:18:49 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2023-01-16 21:18:51 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {manager Update v1 2023-01-16 21:19:15 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2023-01-16 21:19:23 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {calico-node Update v1 2023-01-16 21:19:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-16 21:25:20 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-le680f/providers/Microsoft.Compute/virtualMachines/capz-conf-le680f-md-0-mlc8p,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123181056 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018323456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 21:19:45 +0000 UTC,LastTransitionTime:2023-01-16 21:19:45 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 21:25:20 +0000 UTC,LastTransitionTime:2023-01-16 21:18:49 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 21:25:20 +0000 UTC,LastTransitionTime:2023-01-16 21:18:49 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 21:25:20 +0000 UTC,LastTransitionTime:2023-01-16 21:18:49 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 21:25:20 +0000 UTC,LastTransitionTime:2023-01-16 21:19:23 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-le680f-md-0-mlc8p,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:7ed3df6d0d894fca839afc80ddf63011,SystemUUID:f6ac627b-fc20-8c47-ba59-b52a4bcd610f,BootID:888dffdf-f778-4294-a9f4-7042ab7cbb78,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1007+e7406b4abe5d14,KubeProxyVersion:v1.27.0-alpha.0.1007+e7406b4abe5d14,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:adc0d8c9bc694b1a2486ca24880f8e1d3c7750268174d4414de668b166f99629 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1007_e7406b4abe5d14],SizeBytes:21483003,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 16 21:29:54.954: INFO: Logging kubelet events for node capz-conf-le680f-md-0-mlc8p Jan 16 21:29:55.155: INFO: Logging pods the kubelet thinks is on node capz-conf-le680f-md-0-mlc8p Jan 16 21:29:55.372: INFO: csi-node-driver-vsnvg started at 2023-01-16 21:19:23 +0000 UTC (0+2 container statuses recorded) Jan 16 21:29:55.372: INFO: Container calico-csi ready: true, restart count 0 Jan 16 21:29:55.372: INFO: Container csi-node-driver-registrar ready: true, restart count 0 Jan 16 21:29:55.372: INFO: kube-proxy-4qgks started at 2023-01-16 21:18:57 +0000 UTC (0+1 container statuses recorded) Jan 16 21:29:55.372: INFO: Container kube-proxy ready: true, restart count 0 Jan 16 21:29:55.372: INFO: calico-node-czs9j started at 2023-01-16 21:18:57 +0000 UTC (2+1 container statuses recorded) Jan 16 21:29:55.372: INFO: Init container flexvol-driver ready: true, restart count 0 Jan 16 21:29:55.372: INFO: Init container install-cni ready: true, restart count 0 Jan 16 21:29:55.372: INFO: Container calico-node ready: true, restart count 0 Jan 16 21:29:55.372: INFO: csi-azuredisk-node-r2t76 started at 2023-01-16 21:18:57 +0000 UTC (0+3 container statuses recorded) Jan 16 21:29:55.372: INFO: Container azuredisk ready: true, restart count 0 Jan 16 21:29:55.372: INFO: Container liveness-probe ready: true, restart count 0 Jan 16 21:29:55.372: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 16 21:29:55.986: INFO: Latency metrics for node capz-conf-le680f-md-0-mlc8p Jan 16 21:29:56.174: INFO: Running kubectl logs on non-ready containers in kube-system Jan 16 21:29:56.556: INFO: Failed to get logs of pod kube-apiserver-capz-conf-le680f-control-plane-zdszh, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-le680f-control-plane-zdszh) Jan 16 21:29:56.556: INFO: Logs of kube-system/kube-apiserver-capz-conf-le680f-control-plane-zdszh:kube-apiserver on node capz-conf-le680f-control-plane-zdszh Jan 16 21:29:56.556: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-le680f-control-plane-zdszh:kube-apiserver Jan 16 21:29:56.955: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-le680f-control-plane-zdszh, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-le680f-control-plane-zdszh) Jan 16 21:29:56.955: INFO: Logs of kube-system/kube-controller-manager-capz-conf-le680f-control-plane-zdszh:kube-controller-manager on node capz-conf-le680f-control-plane-zdszh Jan 16 21:29:56.955: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-le680f-control-plane-zdszh:kube-controller-manager Jan 16 21:29:57.354: INFO: Failed to get logs of pod kube-scheduler-capz-conf-le680f-control-plane-zdszh, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-le680f-control-plane-zdszh) Jan 16 21:29:57.354: INFO: Logs of kube-system/kube-scheduler-capz-conf-le680f-control-plane-zdszh:kube-scheduler on node capz-conf-le680f-control-plane-zdszh Jan 16 21:29:57.354: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-le680f-control-plane-zdszh:kube-scheduler [FAILED] Error waiting for all pods to be running and ready: 3 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s POD NODE PHASE GRACE CONDITIONS kube-apiserver-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] kube-controller-manager-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] kube-scheduler-capz-conf-le680f-control-plane-zdszh capz-conf-le680f-control-plane-zdszh Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/16/23 21:29:57.355 < Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/16/23 21:29:57.355 (10m7.645s)
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.402from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.402
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.385from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.385
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.383
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.384
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.389from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.389
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.392from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/16/23 21:29:57.392
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [ReportBeforeSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
capz-e2e [It] Conformance Tests conformance-tests
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [It] Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e [It] Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e [It] Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e [It] Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e [It] Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e [It] Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e [It] Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e [It] Workload cluster creation Creating a cluster that uses the external cloud provider and machinepools [OPTIONAL] with 1 control plane node and 1 machinepool
capz-e2e [It] Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e [It] Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e [It] Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e [It] Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e [It] Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
capz-e2e [It] [K8s-Upgrade] Running the CSI migration tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with out-of-tree cloud provider
capz-e2e [It] [K8s-Upgrade] Running the CSI migration tests [CSI Migration] Running CSI migration test CSI=external CCM=internal AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [It] [K8s-Upgrade] Running the CSI migration tests [CSI Migration] Running CSI migration test CSI=internal CCM=internal AzureDiskCSIMigration=false: upgrade to v1.23 should create volumes dynamically with intree cloud provider