PR #107826 pull-kubernetes-e2e-capz-conformance #1615473425084583936
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | smarterclayton: wait: Introduce new methods that allow detection of context cancellation |
| Result | SUCCESS |
| Tests | 25 failed / 30 succeeded |
| Started | |
| Elapsed | 58m54s |
| Revision | 9311b48f9fc938e1b76db3e1f954746b56618cb4 |
| Refs |
107826 |
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/17/23 23:11:43.014from 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/17/23 23:11:43.014
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/17/23 23:11:43.019from 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/17/23 23:11:43.019
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/17/23 23:11:43.019from 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/17/23 23:11:43.019
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/17/23 23:11:43.016from 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/17/23 23:11:43.016
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/17/23 23:11:43.014from 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/17/23 23:11:43.014
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/17/23 23:11:43.019from 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/17/23 23:11:43.019
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/17/23 23:11:43.014from 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/17/23 23:11:43.014
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/17/23 23:11:43.012from 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/17/23 23:11:43.012
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/17/23 23:11:43.015from 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/17/23 23:11:43.015
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/17/23 23:11:43.025from 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/17/23 23:11:43.025
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/17/23 23:11:43.014from 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/17/23 23:11:43.014
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/17/23 23:11:43.019from 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/17/23 23:11:43.019
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/17/23 23:11:43.014from 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/17/23 23:11:43.014
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/17/23 23:11:43.042from 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/17/23 23:11:43.042
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/17/23 23:11:43.027from 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/17/23 23:11:43.027
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/17/23 23:11:43.016from 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/17/23 23:11:43.016
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/17/23 23:11:43.015from 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/17/23 23:11:43.015
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/17/23 23:11:43.015from 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/17/23 23:11:43.015
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/17/23 23:11:43.014from 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/17/23 23:11:43.014
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-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/17/23 23:11:42.965from junit.kubetest.01.xml
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/17/23 23:01:35.272 Jan 17 23:01:35.272: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 17 23:01:35.276: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 17 23:01:35.526: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 17 23:01:35.726: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:35.726: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:35.726: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:35.726: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 17 23:01:35.726: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:35.726: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:35.726: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:35.726: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:35.726: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:35.726: INFO: Jan 17 23:01:37.873: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:37.873: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:37.873: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:37.873: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Jan 17 23:01:37.873: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:37.873: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:37.873: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:37.873: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:37.873: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:37.873: INFO: Jan 17 23:01:39.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:39.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:39.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:39.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Jan 17 23:01:39.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:39.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:39.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:39.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:39.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:39.866: INFO: Jan 17 23:01:41.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:41.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:41.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:41.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Jan 17 23:01:41.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:41.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:41.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:41.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:41.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:41.862: INFO: Jan 17 23:01:43.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:43.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:43.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:43.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Jan 17 23:01:43.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:43.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:43.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:43.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:43.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:43.861: INFO: Jan 17 23:01:45.873: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:45.873: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:45.873: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:45.873: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Jan 17 23:01:45.873: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:45.873: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:45.873: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:45.873: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:45.873: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:45.873: INFO: Jan 17 23:01:47.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:47.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:47.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:47.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Jan 17 23:01:47.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:47.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:47.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:47.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:47.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:47.859: INFO: Jan 17 23:01:49.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:49.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:49.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:49.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Jan 17 23:01:49.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:49.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:49.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:49.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:49.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:49.863: INFO: Jan 17 23:01:51.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:51.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:51.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:51.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Jan 17 23:01:51.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:51.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:51.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:51.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:51.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:51.864: INFO: Jan 17 23:01:53.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:53.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:53.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:53.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Jan 17 23:01:53.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:53.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:53.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:53.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:53.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:53.858: INFO: Jan 17 23:01:55.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:55.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:55.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:55.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Jan 17 23:01:55.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:55.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:55.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:55.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:55.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:55.860: INFO: Jan 17 23:01:57.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:57.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:57.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:57.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Jan 17 23:01:57.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:57.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:57.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:57.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:57.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:57.862: INFO: Jan 17 23:01:59.867: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:59.867: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:59.867: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:01:59.867: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Jan 17 23:01:59.867: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:01:59.867: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:01:59.867: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:59.867: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:59.867: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:01:59.867: INFO: Jan 17 23:02:01.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:01.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:01.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:01.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Jan 17 23:02:01.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:01.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:01.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:01.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:01.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:01.859: INFO: Jan 17 23:02:03.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:03.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:03.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:03.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Jan 17 23:02:03.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:03.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:03.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:03.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:03.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:03.859: INFO: Jan 17 23:02:05.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:05.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:05.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:05.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Jan 17 23:02:05.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:05.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:05.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:05.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:05.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:05.863: INFO: Jan 17 23:02:07.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:07.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:07.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:07.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Jan 17 23:02:07.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:07.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:07.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:07.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:07.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:07.861: INFO: Jan 17 23:02:09.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:09.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:09.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:09.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Jan 17 23:02:09.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:09.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:09.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:09.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:09.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:09.861: INFO: Jan 17 23:02:11.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:11.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:11.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:11.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Jan 17 23:02:11.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:11.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:11.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:11.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:11.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:11.864: INFO: Jan 17 23:02:13.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:13.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:13.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:13.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Jan 17 23:02:13.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:13.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:13.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:13.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:13.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:13.859: INFO: Jan 17 23:02:15.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:15.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:15.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:15.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Jan 17 23:02:15.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:15.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:15.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:15.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:15.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:15.858: INFO: Jan 17 23:02:17.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:17.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:17.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:17.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Jan 17 23:02:17.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:17.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:17.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:17.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:17.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:17.860: INFO: Jan 17 23:02:19.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:19.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:19.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:19.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Jan 17 23:02:19.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:19.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:19.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:19.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:19.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:19.862: INFO: Jan 17 23:02:21.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:21.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:21.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:21.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Jan 17 23:02:21.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:21.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:21.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:21.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:21.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:21.862: INFO: Jan 17 23:02:23.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:23.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:23.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:23.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Jan 17 23:02:23.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:23.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:23.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:23.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:23.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:23.863: INFO: Jan 17 23:02:25.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:25.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:25.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:25.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Jan 17 23:02:25.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:25.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:25.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:25.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:25.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:25.866: INFO: Jan 17 23:02:27.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:27.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:27.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:27.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Jan 17 23:02:27.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:27.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:27.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:27.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:27.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:27.863: INFO: Jan 17 23:02:29.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:29.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:29.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:29.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Jan 17 23:02:29.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:29.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:29.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:29.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:29.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:29.863: INFO: Jan 17 23:02:31.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:31.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:31.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:31.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Jan 17 23:02:31.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:31.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:31.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:31.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:31.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:31.859: INFO: Jan 17 23:02:33.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:33.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:33.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:33.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Jan 17 23:02:33.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:33.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:33.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:33.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:33.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:33.859: INFO: Jan 17 23:02:35.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:35.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:35.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:35.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Jan 17 23:02:35.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:35.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:35.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:35.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:35.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:35.858: INFO: Jan 17 23:02:37.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:37.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:37.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:37.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Jan 17 23:02:37.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:37.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:37.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:37.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:37.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:37.866: INFO: Jan 17 23:02:39.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:39.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:39.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:39.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Jan 17 23:02:39.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:39.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:39.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:39.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:39.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:39.864: INFO: Jan 17 23:02:41.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:41.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:41.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:41.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Jan 17 23:02:41.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:41.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:41.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:41.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:41.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:41.858: INFO: Jan 17 23:02:43.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:43.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:43.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:43.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Jan 17 23:02:43.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:43.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:43.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:43.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:43.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:43.864: INFO: Jan 17 23:02:45.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:45.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:45.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:45.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Jan 17 23:02:45.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:45.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:45.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:45.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:45.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:45.864: INFO: Jan 17 23:02:47.875: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:47.875: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:47.875: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:47.875: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Jan 17 23:02:47.875: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:47.875: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:47.875: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:47.875: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:47.875: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:47.875: INFO: Jan 17 23:02:49.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:49.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:49.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:49.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Jan 17 23:02:49.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:49.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:49.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:49.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:49.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:49.865: INFO: Jan 17 23:02:51.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:51.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:51.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:51.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Jan 17 23:02:51.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:51.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:51.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:51.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:51.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:51.863: INFO: Jan 17 23:02:53.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:53.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:53.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:53.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Jan 17 23:02:53.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:53.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:53.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:53.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:53.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:53.860: INFO: Jan 17 23:02:55.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:55.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:55.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:55.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Jan 17 23:02:55.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:55.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:55.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:55.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:55.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:55.863: INFO: Jan 17 23:02:57.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:57.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:57.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:57.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Jan 17 23:02:57.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:57.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:57.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:57.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:57.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:57.865: INFO: Jan 17 23:02:59.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:59.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:59.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:02:59.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Jan 17 23:02:59.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:02:59.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:02:59.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:59.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:59.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:02:59.859: INFO: Jan 17 23:03:01.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:01.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:01.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:01.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Jan 17 23:03:01.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:01.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:01.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:01.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:01.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:01.861: INFO: Jan 17 23:03:03.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:03.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:03.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:03.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Jan 17 23:03:03.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:03.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:03.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:03.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:03.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:03.860: INFO: Jan 17 23:03:05.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:05.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:05.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:05.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Jan 17 23:03:05.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:05.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:05.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:05.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:05.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:05.858: INFO: Jan 17 23:03:07.867: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:07.867: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:07.867: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:07.867: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Jan 17 23:03:07.867: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:07.867: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:07.867: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:07.867: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:07.867: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:07.867: INFO: Jan 17 23:03:09.867: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:09.867: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:09.867: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:09.867: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Jan 17 23:03:09.867: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:09.867: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:09.867: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:09.867: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:09.867: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:09.867: INFO: Jan 17 23:03:11.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:11.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:11.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:11.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Jan 17 23:03:11.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:11.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:11.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:11.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:11.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:11.860: INFO: Jan 17 23:03:13.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:13.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:13.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:13.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Jan 17 23:03:13.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:13.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:13.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:13.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:13.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:13.859: INFO: Jan 17 23:03:15.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:15.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:15.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:15.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Jan 17 23:03:15.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:15.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:15.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:15.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:15.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:15.860: INFO: Jan 17 23:03:17.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:17.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:17.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:17.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Jan 17 23:03:17.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:17.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:17.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:17.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:17.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:17.859: INFO: Jan 17 23:03:19.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:19.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:19.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:19.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Jan 17 23:03:19.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:19.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:19.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:19.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:19.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:19.858: INFO: Jan 17 23:03:21.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:21.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:21.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:21.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Jan 17 23:03:21.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:21.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:21.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:21.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:21.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:21.859: INFO: Jan 17 23:03:23.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:23.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:23.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:23.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Jan 17 23:03:23.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:23.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:23.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:23.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:23.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:23.859: INFO: Jan 17 23:03:25.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:25.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:25.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:25.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Jan 17 23:03:25.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:25.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:25.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:25.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:25.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:25.860: INFO: Jan 17 23:03:27.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:27.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:27.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:27.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Jan 17 23:03:27.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:27.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:27.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:27.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:27.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:27.858: INFO: Jan 17 23:03:29.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:29.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:29.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:29.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Jan 17 23:03:29.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:29.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:29.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:29.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:29.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:29.865: INFO: Jan 17 23:03:31.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:31.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:31.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:31.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Jan 17 23:03:31.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:31.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:31.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:31.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:31.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:31.861: INFO: Jan 17 23:03:33.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:33.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:33.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:33.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Jan 17 23:03:33.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:33.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:33.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:33.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:33.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:33.863: INFO: Jan 17 23:03:35.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:35.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:35.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:35.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Jan 17 23:03:35.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:35.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:35.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:35.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:35.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:35.861: INFO: Jan 17 23:03:37.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:37.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:37.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:37.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Jan 17 23:03:37.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:37.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:37.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:37.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:37.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:37.861: INFO: Jan 17 23:03:39.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:39.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:39.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:39.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Jan 17 23:03:39.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:39.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:39.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:39.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:39.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:39.858: INFO: Jan 17 23:03:41.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:41.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:41.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:41.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Jan 17 23:03:41.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:41.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:41.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:41.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:41.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:41.859: INFO: Jan 17 23:03:43.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:43.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:43.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:43.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Jan 17 23:03:43.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:43.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:43.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:43.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:43.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:43.862: INFO: Jan 17 23:03:45.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:45.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:45.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:45.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Jan 17 23:03:45.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:45.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:45.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:45.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:45.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:45.861: INFO: Jan 17 23:03:47.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:47.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:47.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:47.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Jan 17 23:03:47.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:47.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:47.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:47.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:47.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:47.858: INFO: Jan 17 23:03:49.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:49.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:49.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:49.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Jan 17 23:03:49.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:49.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:49.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:49.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:49.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:49.860: INFO: Jan 17 23:03:51.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:51.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:51.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:51.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Jan 17 23:03:51.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:51.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:51.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:51.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:51.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:51.859: INFO: Jan 17 23:03:53.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:53.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:53.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:53.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Jan 17 23:03:53.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:53.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:53.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:53.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:53.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:53.860: INFO: Jan 17 23:03:55.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:55.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:55.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:55.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Jan 17 23:03:55.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:55.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:55.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:55.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:55.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:55.861: INFO: Jan 17 23:03:57.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:57.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:57.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:57.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Jan 17 23:03:57.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:57.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:57.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:57.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:57.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:57.861: INFO: Jan 17 23:03:59.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:59.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:59.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:03:59.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Jan 17 23:03:59.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:03:59.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:03:59.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:59.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:59.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:03:59.860: INFO: Jan 17 23:04:01.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:01.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:01.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:01.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Jan 17 23:04:01.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:01.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:01.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:01.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:01.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:01.861: INFO: Jan 17 23:04:03.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:03.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:03.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:03.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Jan 17 23:04:03.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:03.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:03.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:03.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:03.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:03.859: INFO: Jan 17 23:04:05.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:05.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:05.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:05.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Jan 17 23:04:05.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:05.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:05.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:05.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:05.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:05.859: INFO: Jan 17 23:04:07.870: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:07.870: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:07.870: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:07.870: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Jan 17 23:04:07.870: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:07.870: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:07.870: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:07.870: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:07.870: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:07.870: INFO: Jan 17 23:04:09.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:09.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:09.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:09.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Jan 17 23:04:09.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:09.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:09.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:09.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:09.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:09.858: INFO: Jan 17 23:04:11.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:11.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:11.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:11.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Jan 17 23:04:11.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:11.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:11.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:11.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:11.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:11.859: INFO: Jan 17 23:04:13.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:13.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:13.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:13.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Jan 17 23:04:13.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:13.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:13.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:13.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:13.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:13.862: INFO: Jan 17 23:04:15.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:15.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:15.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:15.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Jan 17 23:04:15.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:15.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:15.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:15.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:15.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:15.859: INFO: Jan 17 23:04:17.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:17.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:17.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:17.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Jan 17 23:04:17.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:17.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:17.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:17.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:17.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:17.858: INFO: Jan 17 23:04:19.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:19.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:19.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:19.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Jan 17 23:04:19.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:19.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:19.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:19.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:19.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:19.860: INFO: Jan 17 23:04:21.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:21.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:21.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:21.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Jan 17 23:04:21.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:21.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:21.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:21.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:21.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:21.861: INFO: Jan 17 23:04:23.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:23.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:23.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:23.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Jan 17 23:04:23.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:23.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:23.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:23.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:23.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:23.863: INFO: Jan 17 23:04:25.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:25.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:25.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:25.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Jan 17 23:04:25.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:25.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:25.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:25.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:25.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:25.859: INFO: Jan 17 23:04:27.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:27.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:27.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:27.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Jan 17 23:04:27.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:27.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:27.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:27.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:27.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:27.860: INFO: Jan 17 23:04:29.867: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:29.867: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:29.867: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:29.867: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Jan 17 23:04:29.867: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:29.867: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:29.867: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:29.867: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:29.867: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:29.867: INFO: Jan 17 23:04:31.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:31.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:31.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:31.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Jan 17 23:04:31.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:31.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:31.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:31.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:31.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:31.859: INFO: Jan 17 23:04:33.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:33.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:33.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:33.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Jan 17 23:04:33.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:33.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:33.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:33.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:33.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:33.860: INFO: Jan 17 23:04:35.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:35.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:35.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:35.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Jan 17 23:04:35.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:35.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:35.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:35.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:35.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:35.861: INFO: Jan 17 23:04:37.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:37.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:37.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:37.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Jan 17 23:04:37.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:37.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:37.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:37.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:37.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:37.862: INFO: Jan 17 23:04:39.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:39.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:39.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:39.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Jan 17 23:04:39.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:39.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:39.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:39.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:39.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:39.859: INFO: Jan 17 23:04:41.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:41.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:41.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:41.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Jan 17 23:04:41.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:41.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:41.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:41.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:41.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:41.859: INFO: Jan 17 23:04:43.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:43.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:43.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:43.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Jan 17 23:04:43.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:43.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:43.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:43.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:43.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:43.863: INFO: Jan 17 23:04:45.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:45.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:45.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:45.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Jan 17 23:04:45.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:45.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:45.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:45.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:45.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:45.858: INFO: Jan 17 23:04:47.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:47.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:47.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:47.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Jan 17 23:04:47.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:47.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:47.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:47.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:47.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:47.862: INFO: Jan 17 23:04:49.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:49.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:49.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:49.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Jan 17 23:04:49.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:49.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:49.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:49.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:49.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:49.865: INFO: Jan 17 23:04:51.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:51.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:51.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:51.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Jan 17 23:04:51.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:51.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:51.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:51.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:51.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:51.860: INFO: Jan 17 23:04:53.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:53.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:53.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:53.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Jan 17 23:04:53.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:53.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:53.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:53.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:53.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:53.858: INFO: Jan 17 23:04:55.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:55.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:55.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:55.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Jan 17 23:04:55.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:55.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:55.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:55.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:55.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:55.863: INFO: Jan 17 23:04:57.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:57.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:57.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:57.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Jan 17 23:04:57.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:57.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:57.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:57.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:57.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:57.862: INFO: Jan 17 23:04:59.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:59.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:59.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:04:59.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Jan 17 23:04:59.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:04:59.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:04:59.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:59.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:59.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:04:59.864: INFO: Jan 17 23:05:01.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:01.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:01.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:01.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Jan 17 23:05:01.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:01.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:01.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:01.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:01.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:01.861: INFO: Jan 17 23:05:03.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:03.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:03.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:03.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Jan 17 23:05:03.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:03.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:03.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:03.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:03.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:03.860: INFO: Jan 17 23:05:05.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:05.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:05.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:05.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Jan 17 23:05:05.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:05.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:05.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:05.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:05.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:05.860: INFO: Jan 17 23:05:07.872: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:07.872: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:07.872: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:07.872: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Jan 17 23:05:07.872: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:07.872: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:07.872: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:07.872: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:07.872: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:07.872: INFO: Jan 17 23:05:09.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:09.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:09.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:09.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Jan 17 23:05:09.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:09.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:09.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:09.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:09.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:09.858: INFO: Jan 17 23:05:11.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:11.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:11.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:11.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Jan 17 23:05:11.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:11.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:11.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:11.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:11.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:11.860: INFO: Jan 17 23:05:13.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:13.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:13.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:13.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Jan 17 23:05:13.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:13.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:13.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:13.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:13.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:13.861: INFO: Jan 17 23:05:15.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:15.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:15.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:15.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Jan 17 23:05:15.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:15.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:15.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:15.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:15.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:15.858: INFO: Jan 17 23:05:17.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:17.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:17.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:17.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Jan 17 23:05:17.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:17.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:17.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:17.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:17.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:17.859: INFO: Jan 17 23:05:19.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:19.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:19.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:19.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Jan 17 23:05:19.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:19.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:19.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:19.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:19.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:19.858: INFO: Jan 17 23:05:21.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:21.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:21.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:21.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Jan 17 23:05:21.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:21.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:21.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:21.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:21.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:21.859: INFO: Jan 17 23:05:23.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:23.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:23.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:23.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Jan 17 23:05:23.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:23.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:23.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:23.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:23.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:23.859: INFO: Jan 17 23:05:25.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:25.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:25.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:25.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Jan 17 23:05:25.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:25.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:25.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:25.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:25.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:25.864: INFO: Jan 17 23:05:27.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:27.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:27.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:27.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Jan 17 23:05:27.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:27.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:27.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:27.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:27.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:27.859: INFO: Jan 17 23:05:29.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:29.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:29.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:29.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Jan 17 23:05:29.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:29.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:29.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:29.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:29.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:29.866: INFO: Jan 17 23:05:31.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:31.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:31.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:31.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Jan 17 23:05:31.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:31.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:31.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:31.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:31.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:31.862: INFO: Jan 17 23:05:33.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:33.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:33.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:33.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Jan 17 23:05:33.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:33.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:33.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:33.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:33.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:33.860: INFO: Jan 17 23:05:35.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:35.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:35.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:35.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Jan 17 23:05:35.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:35.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:35.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:35.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:35.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:35.860: INFO: Jan 17 23:05:37.872: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:37.872: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:37.872: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:37.872: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Jan 17 23:05:37.872: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:37.872: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:37.872: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:37.872: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:37.872: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:37.872: INFO: Jan 17 23:05:39.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:39.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:39.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:39.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Jan 17 23:05:39.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:39.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:39.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:39.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:39.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:39.860: INFO: Jan 17 23:05:41.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:41.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:41.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:41.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Jan 17 23:05:41.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:41.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:41.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:41.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:41.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:41.859: INFO: Jan 17 23:05:43.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:43.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:43.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:43.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Jan 17 23:05:43.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:43.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:43.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:43.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:43.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:43.862: INFO: Jan 17 23:05:45.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:45.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:45.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:45.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Jan 17 23:05:45.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:45.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:45.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:45.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:45.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:45.860: INFO: Jan 17 23:05:47.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:47.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:47.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:47.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Jan 17 23:05:47.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:47.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:47.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:47.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:47.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:47.859: INFO: Jan 17 23:05:49.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:49.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:49.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:49.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Jan 17 23:05:49.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:49.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:49.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:49.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:49.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:49.859: INFO: Jan 17 23:05:51.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:51.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:51.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:51.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Jan 17 23:05:51.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:51.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:51.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:51.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:51.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:51.859: INFO: Jan 17 23:05:53.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:53.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:53.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:53.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Jan 17 23:05:53.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:53.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:53.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:53.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:53.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:53.858: INFO: Jan 17 23:05:55.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:55.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:55.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:55.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Jan 17 23:05:55.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:55.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:55.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:55.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:55.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:55.859: INFO: Jan 17 23:05:57.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:57.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:57.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:57.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Jan 17 23:05:57.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:57.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:57.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:57.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:57.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:57.860: INFO: Jan 17 23:05:59.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:59.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:59.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:05:59.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Jan 17 23:05:59.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:05:59.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:05:59.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:59.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:59.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:05:59.861: INFO: Jan 17 23:06:01.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:01.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:01.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:01.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Jan 17 23:06:01.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:01.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:01.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:01.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:01.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:01.858: INFO: Jan 17 23:06:03.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:03.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:03.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:03.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Jan 17 23:06:03.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:03.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:03.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:03.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:03.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:03.862: INFO: Jan 17 23:06:05.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:05.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:05.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:05.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Jan 17 23:06:05.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:05.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:05.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:05.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:05.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:05.859: INFO: Jan 17 23:06:07.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:07.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:07.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:07.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Jan 17 23:06:07.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:07.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:07.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:07.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:07.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:07.865: INFO: Jan 17 23:06:09.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:09.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:09.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:09.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Jan 17 23:06:09.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:09.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:09.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:09.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:09.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:09.861: INFO: Jan 17 23:06:11.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:11.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:11.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:11.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Jan 17 23:06:11.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:11.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:11.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:11.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:11.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:11.861: INFO: Jan 17 23:06:13.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:13.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:13.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:13.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Jan 17 23:06:13.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:13.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:13.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:13.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:13.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:13.861: INFO: Jan 17 23:06:15.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:15.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:15.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:15.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Jan 17 23:06:15.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:15.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:15.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:15.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:15.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:15.859: INFO: Jan 17 23:06:17.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:17.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:17.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:17.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Jan 17 23:06:17.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:17.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:17.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:17.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:17.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:17.863: INFO: Jan 17 23:06:19.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:19.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:19.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:19.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Jan 17 23:06:19.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:19.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:19.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:19.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:19.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:19.859: INFO: Jan 17 23:06:21.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:21.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:21.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:21.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Jan 17 23:06:21.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:21.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:21.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:21.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:21.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:21.859: INFO: Jan 17 23:06:23.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:23.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:23.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:23.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Jan 17 23:06:23.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:23.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:23.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:23.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:23.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:23.858: INFO: Jan 17 23:06:25.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:25.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:25.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:25.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Jan 17 23:06:25.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:25.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:25.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:25.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:25.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:25.860: INFO: Jan 17 23:06:27.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:27.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:27.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:27.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Jan 17 23:06:27.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:27.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:27.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:27.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:27.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:27.859: INFO: Jan 17 23:06:29.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:29.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:29.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:29.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Jan 17 23:06:29.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:29.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:29.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:29.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:29.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:29.861: INFO: Jan 17 23:06:31.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:31.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:31.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:31.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Jan 17 23:06:31.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:31.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:31.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:31.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:31.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:31.859: INFO: Jan 17 23:06:33.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:33.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:33.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:33.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Jan 17 23:06:33.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:33.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:33.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:33.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:33.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:33.859: INFO: Jan 17 23:06:35.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:35.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:35.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:35.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Jan 17 23:06:35.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:35.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:35.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:35.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:35.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:35.862: INFO: Jan 17 23:06:37.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:37.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:37.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:37.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Jan 17 23:06:37.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:37.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:37.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:37.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:37.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:37.862: INFO: Jan 17 23:06:39.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:39.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:39.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:39.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Jan 17 23:06:39.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:39.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:39.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:39.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:39.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:39.858: INFO: Jan 17 23:06:41.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:41.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:41.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:41.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Jan 17 23:06:41.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:41.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:41.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:41.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:41.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:41.860: INFO: Jan 17 23:06:43.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:43.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:43.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:43.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Jan 17 23:06:43.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:43.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:43.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:43.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:43.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:43.862: INFO: Jan 17 23:06:45.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:45.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:45.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:45.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Jan 17 23:06:45.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:45.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:45.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:45.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:45.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:45.859: INFO: Jan 17 23:06:47.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:47.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:47.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:47.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Jan 17 23:06:47.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:47.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:47.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:47.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:47.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:47.859: INFO: Jan 17 23:06:49.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:49.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:49.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:49.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Jan 17 23:06:49.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:49.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:49.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:49.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:49.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:49.859: INFO: Jan 17 23:06:51.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:51.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:51.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:51.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Jan 17 23:06:51.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:51.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:51.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:51.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:51.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:51.860: INFO: Jan 17 23:06:53.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:53.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:53.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:53.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Jan 17 23:06:53.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:53.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:53.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:53.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:53.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:53.858: INFO: Jan 17 23:06:55.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:55.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:55.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:55.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Jan 17 23:06:55.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:55.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:55.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:55.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:55.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:55.862: INFO: Jan 17 23:06:57.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:57.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:57.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:57.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Jan 17 23:06:57.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:57.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:57.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:57.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:57.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:57.859: INFO: Jan 17 23:06:59.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:59.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:59.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:06:59.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Jan 17 23:06:59.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:06:59.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:06:59.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:59.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:59.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:06:59.866: INFO: Jan 17 23:07:01.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:01.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:01.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:01.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Jan 17 23:07:01.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:01.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:01.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:01.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:01.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:01.860: INFO: Jan 17 23:07:03.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:03.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:03.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:03.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Jan 17 23:07:03.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:03.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:03.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:03.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:03.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:03.860: INFO: Jan 17 23:07:05.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:05.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:05.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:05.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Jan 17 23:07:05.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:05.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:05.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:05.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:05.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:05.859: INFO: Jan 17 23:07:07.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:07.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:07.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:07.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Jan 17 23:07:07.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:07.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:07.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:07.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:07.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:07.862: INFO: Jan 17 23:07:09.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:09.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:09.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:09.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Jan 17 23:07:09.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:09.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:09.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:09.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:09.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:09.861: INFO: Jan 17 23:07:11.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:11.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:11.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:11.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Jan 17 23:07:11.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:11.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:11.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:11.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:11.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:11.860: INFO: Jan 17 23:07:13.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:13.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:13.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:13.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Jan 17 23:07:13.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:13.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:13.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:13.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:13.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:13.859: INFO: Jan 17 23:07:15.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:15.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:15.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:15.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Jan 17 23:07:15.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:15.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:15.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:15.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:15.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:15.859: INFO: Jan 17 23:07:17.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:17.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:17.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:17.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Jan 17 23:07:17.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:17.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:17.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:17.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:17.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:17.860: INFO: Jan 17 23:07:19.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:19.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:19.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:19.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Jan 17 23:07:19.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:19.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:19.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:19.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:19.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:19.860: INFO: Jan 17 23:07:21.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:21.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:21.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:21.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Jan 17 23:07:21.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:21.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:21.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:21.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:21.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:21.860: INFO: Jan 17 23:07:23.869: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:23.869: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:23.869: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:23.869: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Jan 17 23:07:23.869: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:23.869: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:23.869: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:23.869: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:23.869: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:23.869: INFO: Jan 17 23:07:25.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:25.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:25.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:25.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Jan 17 23:07:25.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:25.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:25.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:25.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:25.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:25.861: INFO: Jan 17 23:07:27.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:27.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:27.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:27.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Jan 17 23:07:27.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:27.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:27.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:27.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:27.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:27.858: INFO: Jan 17 23:07:29.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:29.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:29.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:29.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Jan 17 23:07:29.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:29.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:29.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:29.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:29.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:29.860: INFO: Jan 17 23:07:31.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:31.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:31.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:31.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Jan 17 23:07:31.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:31.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:31.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:31.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:31.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:31.862: INFO: Jan 17 23:07:33.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:33.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:33.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:33.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Jan 17 23:07:33.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:33.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:33.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:33.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:33.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:33.859: INFO: Jan 17 23:07:35.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:35.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:35.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:35.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Jan 17 23:07:35.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:35.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:35.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:35.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:35.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:35.859: INFO: Jan 17 23:07:37.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:37.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:37.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:37.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Jan 17 23:07:37.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:37.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:37.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:37.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:37.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:37.859: INFO: Jan 17 23:07:39.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:39.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:39.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:39.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Jan 17 23:07:39.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:39.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:39.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:39.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:39.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:39.859: INFO: Jan 17 23:07:41.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:41.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:41.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:41.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Jan 17 23:07:41.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:41.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:41.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:41.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:41.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:41.858: INFO: Jan 17 23:07:43.871: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:43.871: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:43.871: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:43.871: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Jan 17 23:07:43.871: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:43.871: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:43.871: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:43.871: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:43.872: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:43.872: INFO: Jan 17 23:07:45.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:45.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:45.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:45.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Jan 17 23:07:45.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:45.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:45.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:45.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:45.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:45.858: INFO: Jan 17 23:07:47.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:47.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:47.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:47.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Jan 17 23:07:47.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:47.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:47.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:47.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:47.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:47.860: INFO: Jan 17 23:07:49.867: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:49.867: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:49.867: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:49.867: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Jan 17 23:07:49.867: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:49.867: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:49.867: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:49.867: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:49.867: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:49.867: INFO: Jan 17 23:07:51.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:51.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:51.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:51.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Jan 17 23:07:51.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:51.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:51.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:51.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:51.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:51.860: INFO: Jan 17 23:07:53.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:53.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:53.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:53.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Jan 17 23:07:53.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:53.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:53.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:53.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:53.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:53.861: INFO: Jan 17 23:07:55.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:55.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:55.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:55.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Jan 17 23:07:55.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:55.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:55.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:55.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:55.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:55.862: INFO: Jan 17 23:07:57.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:57.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:57.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:57.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Jan 17 23:07:57.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:57.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:57.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:57.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:57.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:57.858: INFO: Jan 17 23:07:59.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:59.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:59.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:07:59.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Jan 17 23:07:59.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:07:59.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:07:59.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:59.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:59.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:07:59.865: INFO: Jan 17 23:08:01.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:01.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:01.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:01.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Jan 17 23:08:01.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:01.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:01.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:01.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:01.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:01.859: INFO: Jan 17 23:08:03.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:03.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:03.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:03.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Jan 17 23:08:03.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:03.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:03.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:03.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:03.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:03.860: INFO: Jan 17 23:08:05.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:05.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:05.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:05.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Jan 17 23:08:05.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:05.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:05.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:05.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:05.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:05.859: INFO: Jan 17 23:08:07.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:07.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:07.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:07.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Jan 17 23:08:07.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:07.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:07.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:07.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:07.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:07.863: INFO: Jan 17 23:08:09.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:09.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:09.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:09.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Jan 17 23:08:09.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:09.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:09.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:09.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:09.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:09.859: INFO: Jan 17 23:08:11.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:11.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:11.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:11.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Jan 17 23:08:11.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:11.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:11.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:11.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:11.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:11.860: INFO: Jan 17 23:08:13.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:13.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:13.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:13.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Jan 17 23:08:13.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:13.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:13.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:13.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:13.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:13.859: INFO: Jan 17 23:08:15.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:15.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:15.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:15.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Jan 17 23:08:15.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:15.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:15.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:15.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:15.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:15.858: INFO: Jan 17 23:08:17.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:17.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:17.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:17.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Jan 17 23:08:17.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:17.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:17.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:17.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:17.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:17.860: INFO: Jan 17 23:08:19.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:19.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:19.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:19.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Jan 17 23:08:19.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:19.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:19.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:19.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:19.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:19.858: INFO: Jan 17 23:08:21.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:21.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:21.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:21.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Jan 17 23:08:21.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:21.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:21.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:21.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:21.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:21.858: INFO: Jan 17 23:08:23.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:23.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:23.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:23.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Jan 17 23:08:23.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:23.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:23.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:23.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:23.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:23.864: INFO: Jan 17 23:08:25.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:25.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:25.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:25.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Jan 17 23:08:25.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:25.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:25.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:25.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:25.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:25.861: INFO: Jan 17 23:08:27.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:27.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:27.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:27.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Jan 17 23:08:27.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:27.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:27.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:27.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:27.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:27.862: INFO: Jan 17 23:08:29.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:29.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:29.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:29.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Jan 17 23:08:29.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:29.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:29.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:29.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:29.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:29.860: INFO: Jan 17 23:08:31.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:31.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:31.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:31.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Jan 17 23:08:31.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:31.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:31.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:31.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:31.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:31.865: INFO: Jan 17 23:08:33.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:33.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:33.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:33.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Jan 17 23:08:33.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:33.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:33.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:33.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:33.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:33.865: INFO: Jan 17 23:08:35.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:35.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:35.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:35.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Jan 17 23:08:35.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:35.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:35.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:35.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:35.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:35.860: INFO: Jan 17 23:08:37.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:37.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:37.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:37.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Jan 17 23:08:37.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:37.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:37.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:37.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:37.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:37.858: INFO: Jan 17 23:08:39.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:39.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:39.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:39.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Jan 17 23:08:39.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:39.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:39.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:39.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:39.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:39.861: INFO: Jan 17 23:08:41.857: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:41.857: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:41.857: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:41.857: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Jan 17 23:08:41.857: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:41.857: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:41.857: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:41.857: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:41.857: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:41.857: INFO: Jan 17 23:08:43.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:43.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:43.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:43.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Jan 17 23:08:43.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:43.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:43.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:43.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:43.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:43.863: INFO: Jan 17 23:08:45.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:45.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:45.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:45.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Jan 17 23:08:45.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:45.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:45.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:45.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:45.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:45.859: INFO: Jan 17 23:08:47.873: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:47.873: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:47.873: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:47.873: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Jan 17 23:08:47.873: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:47.873: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:47.873: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:47.873: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:47.873: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:47.873: INFO: Jan 17 23:08:49.869: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:49.869: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:49.869: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:49.869: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Jan 17 23:08:49.869: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:49.869: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:49.869: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:49.869: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:49.869: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:49.869: INFO: Jan 17 23:08:51.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:51.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:51.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:51.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Jan 17 23:08:51.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:51.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:51.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:51.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:51.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:51.862: INFO: Jan 17 23:08:53.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:53.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:53.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:53.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Jan 17 23:08:53.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:53.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:53.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:53.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:53.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:53.865: INFO: Jan 17 23:08:55.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:55.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:55.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:55.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Jan 17 23:08:55.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:55.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:55.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:55.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:55.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:55.859: INFO: Jan 17 23:08:57.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:57.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:57.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:57.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Jan 17 23:08:57.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:57.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:57.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:57.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:57.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:57.858: INFO: Jan 17 23:08:59.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:59.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:59.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:08:59.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Jan 17 23:08:59.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:08:59.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:08:59.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:59.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:59.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:08:59.864: INFO: Jan 17 23:09:01.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:01.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:01.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:01.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Jan 17 23:09:01.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:01.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:01.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:01.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:01.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:01.860: INFO: Jan 17 23:09:03.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:03.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:03.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:03.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Jan 17 23:09:03.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:03.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:03.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:03.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:03.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:03.859: INFO: Jan 17 23:09:05.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:05.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:05.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:05.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Jan 17 23:09:05.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:05.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:05.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:05.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:05.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:05.861: INFO: Jan 17 23:09:07.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:07.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:07.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:07.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Jan 17 23:09:07.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:07.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:07.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:07.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:07.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:07.858: INFO: Jan 17 23:09:09.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:09.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:09.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:09.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Jan 17 23:09:09.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:09.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:09.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:09.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:09.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:09.863: INFO: Jan 17 23:09:11.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:11.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:11.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:11.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Jan 17 23:09:11.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:11.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:11.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:11.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:11.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:11.862: INFO: Jan 17 23:09:13.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:13.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:13.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:13.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Jan 17 23:09:13.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:13.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:13.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:13.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:13.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:13.859: INFO: Jan 17 23:09:15.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:15.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:15.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:15.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Jan 17 23:09:15.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:15.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:15.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:15.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:15.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:15.858: INFO: Jan 17 23:09:17.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:17.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:17.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:17.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Jan 17 23:09:17.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:17.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:17.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:17.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:17.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:17.860: INFO: Jan 17 23:09:19.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:19.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:19.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:19.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Jan 17 23:09:19.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:19.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:19.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:19.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:19.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:19.862: INFO: Jan 17 23:09:21.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:21.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:21.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:21.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Jan 17 23:09:21.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:21.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:21.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:21.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:21.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:21.859: INFO: Jan 17 23:09:23.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:23.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:23.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:23.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Jan 17 23:09:23.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:23.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:23.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:23.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:23.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:23.859: INFO: Jan 17 23:09:25.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:25.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:25.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:25.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Jan 17 23:09:25.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:25.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:25.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:25.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:25.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:25.866: INFO: Jan 17 23:09:27.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:27.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:27.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:27.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Jan 17 23:09:27.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:27.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:27.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:27.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:27.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:27.866: INFO: Jan 17 23:09:29.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:29.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:29.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:29.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Jan 17 23:09:29.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:29.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:29.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:29.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:29.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:29.865: INFO: Jan 17 23:09:31.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:31.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:31.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:31.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Jan 17 23:09:31.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:31.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:31.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:31.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:31.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:31.858: INFO: Jan 17 23:09:33.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:33.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:33.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:33.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Jan 17 23:09:33.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:33.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:33.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:33.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:33.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:33.863: INFO: Jan 17 23:09:35.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:35.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:35.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:35.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Jan 17 23:09:35.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:35.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:35.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:35.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:35.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:35.858: INFO: Jan 17 23:09:37.874: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:37.874: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:37.874: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:37.874: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Jan 17 23:09:37.874: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:37.874: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:37.874: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:37.874: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:37.874: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:37.874: INFO: Jan 17 23:09:39.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:39.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:39.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:39.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Jan 17 23:09:39.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:39.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:39.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:39.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:39.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:39.859: INFO: Jan 17 23:09:41.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:41.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:41.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:41.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Jan 17 23:09:41.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:41.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:41.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:41.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:41.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:41.859: INFO: Jan 17 23:09:43.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:43.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:43.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:43.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Jan 17 23:09:43.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:43.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:43.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:43.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:43.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:43.862: INFO: Jan 17 23:09:45.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:45.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:45.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:45.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Jan 17 23:09:45.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:45.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:45.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:45.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:45.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:45.860: INFO: Jan 17 23:09:47.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:47.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:47.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:47.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Jan 17 23:09:47.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:47.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:47.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:47.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:47.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:47.859: INFO: Jan 17 23:09:49.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:49.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:49.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:49.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Jan 17 23:09:49.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:49.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:49.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:49.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:49.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:49.859: INFO: Jan 17 23:09:51.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:51.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:51.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:51.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Jan 17 23:09:51.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:51.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:51.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:51.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:51.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:51.860: INFO: Jan 17 23:09:53.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:53.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:53.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:53.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Jan 17 23:09:53.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:53.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:53.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:53.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:53.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:53.865: INFO: Jan 17 23:09:55.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:55.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:55.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:55.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Jan 17 23:09:55.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:55.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:55.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:55.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:55.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:55.866: INFO: Jan 17 23:09:57.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:57.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:57.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:57.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Jan 17 23:09:57.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:57.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:57.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:57.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:57.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:57.860: INFO: Jan 17 23:09:59.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:59.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:59.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:09:59.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Jan 17 23:09:59.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:09:59.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:09:59.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:59.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:59.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:09:59.861: INFO: Jan 17 23:10:01.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:01.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:01.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:01.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Jan 17 23:10:01.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:01.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:01.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:01.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:01.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:01.861: INFO: Jan 17 23:10:03.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:03.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:03.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:03.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Jan 17 23:10:03.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:03.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:03.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:03.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:03.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:03.862: INFO: Jan 17 23:10:05.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:05.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:05.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:05.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Jan 17 23:10:05.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:05.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:05.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:05.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:05.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:05.858: INFO: Jan 17 23:10:07.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:07.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:07.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:07.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Jan 17 23:10:07.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:07.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:07.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:07.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:07.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:07.862: INFO: Jan 17 23:10:09.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:09.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:09.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:09.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Jan 17 23:10:09.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:09.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:09.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:09.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:09.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:09.859: INFO: Jan 17 23:10:11.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:11.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:11.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:11.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Jan 17 23:10:11.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:11.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:11.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:11.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:11.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:11.859: INFO: Jan 17 23:10:13.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:13.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:13.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:13.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Jan 17 23:10:13.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:13.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:13.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:13.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:13.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:13.860: INFO: Jan 17 23:10:15.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:15.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:15.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:15.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Jan 17 23:10:15.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:15.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:15.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:15.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:15.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:15.860: INFO: Jan 17 23:10:17.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:17.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:17.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:17.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Jan 17 23:10:17.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:17.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:17.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:17.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:17.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:17.859: INFO: Jan 17 23:10:19.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:19.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:19.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:19.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Jan 17 23:10:19.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:19.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:19.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:19.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:19.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:19.866: INFO: Jan 17 23:10:21.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:21.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:21.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:21.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Jan 17 23:10:21.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:21.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:21.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:21.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:21.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:21.861: INFO: Jan 17 23:10:23.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:23.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:23.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:23.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Jan 17 23:10:23.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:23.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:23.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:23.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:23.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:23.862: INFO: Jan 17 23:10:25.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:25.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:25.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:25.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Jan 17 23:10:25.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:25.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:25.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:25.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:25.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:25.859: INFO: Jan 17 23:10:27.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:27.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:27.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:27.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Jan 17 23:10:27.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:27.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:27.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:27.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:27.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:27.859: INFO: Jan 17 23:10:29.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:29.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:29.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:29.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Jan 17 23:10:29.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:29.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:29.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:29.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:29.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:29.861: INFO: Jan 17 23:10:31.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:31.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:31.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:31.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Jan 17 23:10:31.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:31.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:31.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:31.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:31.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:31.860: INFO: Jan 17 23:10:33.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:33.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:33.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:33.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Jan 17 23:10:33.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:33.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:33.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:33.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:33.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:33.859: INFO: Jan 17 23:10:35.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:35.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:35.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:35.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Jan 17 23:10:35.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:35.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:35.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:35.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:35.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:35.860: INFO: Jan 17 23:10:37.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:37.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:37.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:37.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Jan 17 23:10:37.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:37.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:37.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:37.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:37.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:37.862: INFO: Jan 17 23:10:39.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:39.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:39.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:39.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Jan 17 23:10:39.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:39.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:39.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:39.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:39.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:39.858: INFO: Jan 17 23:10:41.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:41.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:41.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:41.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Jan 17 23:10:41.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:41.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:41.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:41.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:41.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:41.859: INFO: Jan 17 23:10:43.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:43.865: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:43.865: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:43.865: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Jan 17 23:10:43.865: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:43.865: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:43.865: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:43.865: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:43.865: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:43.865: INFO: Jan 17 23:10:45.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:45.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:45.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:45.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Jan 17 23:10:45.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:45.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:45.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:45.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:45.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:45.861: INFO: Jan 17 23:10:47.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:47.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:47.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:47.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Jan 17 23:10:47.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:47.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:47.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:47.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:47.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:47.860: INFO: Jan 17 23:10:49.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:49.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:49.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:49.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Jan 17 23:10:49.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:49.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:49.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:49.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:49.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:49.864: INFO: Jan 17 23:10:51.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:51.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:51.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:51.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Jan 17 23:10:51.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:51.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:51.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:51.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:51.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:51.859: INFO: Jan 17 23:10:53.858: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:53.858: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:53.858: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:53.858: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Jan 17 23:10:53.858: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:53.858: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:53.858: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:53.858: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:53.858: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:53.858: INFO: Jan 17 23:10:55.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:55.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:55.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:55.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Jan 17 23:10:55.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:55.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:55.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:55.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:55.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:55.862: INFO: Jan 17 23:10:57.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:57.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:57.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:57.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Jan 17 23:10:57.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:57.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:57.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:57.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:57.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:57.864: INFO: Jan 17 23:10:59.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:59.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:59.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:10:59.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Jan 17 23:10:59.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:10:59.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:10:59.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:59.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:59.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:10:59.862: INFO: Jan 17 23:11:01.869: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:01.869: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:01.869: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:01.869: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Jan 17 23:11:01.869: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:01.869: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:01.869: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:01.869: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:01.869: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:01.869: INFO: Jan 17 23:11:03.861: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:03.861: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:03.861: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:03.861: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Jan 17 23:11:03.861: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:03.861: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:03.861: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:03.861: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:03.861: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:03.861: INFO: Jan 17 23:11:05.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:05.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:05.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:05.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Jan 17 23:11:05.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:05.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:05.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:05.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:05.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:05.859: INFO: Jan 17 23:11:07.860: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:07.860: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:07.860: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:07.860: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Jan 17 23:11:07.860: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:07.860: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:07.860: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:07.860: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:07.860: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:07.860: INFO: Jan 17 23:11:09.859: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:09.859: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:09.859: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:09.859: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Jan 17 23:11:09.859: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:09.859: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:09.859: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:09.859: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:09.859: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:09.859: INFO: Jan 17 23:11:11.868: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:11.868: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:11.868: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:11.868: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Jan 17 23:11:11.868: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:11.868: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:11.868: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:11.868: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:11.868: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:11.868: INFO: Jan 17 23:11:13.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:13.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:13.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:13.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Jan 17 23:11:13.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:13.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:13.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:13.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:13.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:13.866: INFO: Jan 17 23:11:15.862: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:15.862: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:15.862: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:15.862: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Jan 17 23:11:15.862: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:15.862: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:15.862: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:15.862: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:15.862: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:15.862: INFO: Jan 17 23:11:17.865: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:17.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:17.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:17.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Jan 17 23:11:17.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:17.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:17.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:17.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:17.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:17.866: INFO: Jan 17 23:11:19.870: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:19.870: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:19.870: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:19.870: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Jan 17 23:11:19.870: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:19.870: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:19.870: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:19.870: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:19.870: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:19.870: INFO: Jan 17 23:11:21.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:21.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:21.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:21.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Jan 17 23:11:21.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:21.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:21.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:21.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:21.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:21.866: INFO: Jan 17 23:11:23.867: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:23.867: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:23.867: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:23.867: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Jan 17 23:11:23.867: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:23.867: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:23.867: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:23.867: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:23.867: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:23.867: INFO: Jan 17 23:11:25.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:25.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:25.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:25.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Jan 17 23:11:25.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:25.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:25.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:25.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:25.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:25.863: INFO: Jan 17 23:11:27.866: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:27.866: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:27.866: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:27.866: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Jan 17 23:11:27.866: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:27.866: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:27.866: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:27.866: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:27.866: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:27.866: INFO: Jan 17 23:11:29.864: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:29.864: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:29.864: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:29.864: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Jan 17 23:11:29.864: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:29.864: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:29.864: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:29.864: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:29.864: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:29.864: INFO: Jan 17 23:11:31.869: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:31.869: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:31.869: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:31.869: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Jan 17 23:11:31.869: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:31.869: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:31.869: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:31.869: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:31.869: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:31.869: INFO: Jan 17 23:11:33.863: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:33.863: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:33.863: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:33.863: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Jan 17 23:11:33.863: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:33.863: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:33.863: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:33.863: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:33.863: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:33.863: INFO: Jan 17 23:11:35.867: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:35.867: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:35.867: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:35.867: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 17 23:11:35.867: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:35.867: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:35.867: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:35.867: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:35.867: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:35.867: INFO: Jan 17 23:11:36.011: INFO: The status of Pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:36.011: INFO: The status of Pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:36.011: INFO: The status of Pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 17 23:11:36.011: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 17 23:11:36.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 17 23:11:36.011: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:36.011: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:36.011: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:36.011: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:36.011: INFO: STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/17/23 23:11:36.011 STEP: Found 117 events. - test/e2e/framework/debug/dump.go:46 @ 01/17/23 23:11:36.073 Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:42 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-jrfrhh-control-plane-c7wdf_63ac3666-9149-4621-a35a-0663fc3610e9 became leader Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:44 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-jrfrhh-control-plane-c7wdf_ccc5bf4f-ec72-4b0b-8d7a-0441ea89bc64 became leader Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:47 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2 Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:47 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-z4dlb Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:47 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-6mwwc Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:47 +0000 UTC - event for coredns-56f4c55bf9-6mwwc: {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 17 23:11:36.073: INFO: At 2023-01-17 22:58:47 +0000 UTC - event for coredns-56f4c55bf9-z4dlb: {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 17 23:11:36.073: INFO: At 2023-01-17 22:58:47 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-v4xgj Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:47 +0000 UTC - event for kube-proxy-v4xgj: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-v4xgj to capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:48 +0000 UTC - event for kube-proxy-v4xgj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2" Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:50 +0000 UTC - event for kube-proxy-v4xgj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2" in 1.395013485s (1.395018385s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:50 +0000 UTC - event for kube-proxy-v4xgj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container kube-proxy Jan 17 23:11:36.073: INFO: At 2023-01-17 22:58:50 +0000 UTC - event for kube-proxy-v4xgj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container kube-proxy Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:01 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:01 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-k69qz Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:01 +0000 UTC - event for metrics-server-c9574f845-k69qz: {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 17 23:11:36.073: INFO: At 2023-01-17 22:59:26 +0000 UTC - event for coredns-56f4c55bf9-6mwwc: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-6mwwc to capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:26 +0000 UTC - event for coredns-56f4c55bf9-z4dlb: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-z4dlb to capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:26 +0000 UTC - event for coredns-56f4c55bf9-z4dlb: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "2a1b00fb9371a0175c24faae4b3aa7cc6b931ae777e07dac966d4ee0af58127e": 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 17 23:11:36.073: INFO: At 2023-01-17 22:59:26 +0000 UTC - event for metrics-server-c9574f845-k69qz: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-k69qz to capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:27 +0000 UTC - event for coredns-56f4c55bf9-6mwwc: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "29597d10996d2959fa6a357540c25b8ea84245650e9aa6cbb1cdd1ad17243abc": 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 17 23:11:36.073: INFO: At 2023-01-17 22:59:27 +0000 UTC - event for metrics-server-c9574f845-k69qz: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "b9007cbf2cce1c95db42b400dc87aa8cb05a0cd71767ef45f8e2bb75c8488ded": 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 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for coredns-56f4c55bf9-6mwwc: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for coredns-56f4c55bf9-6mwwc: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container coredns Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for coredns-56f4c55bf9-6mwwc: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for coredns-56f4c55bf9-6mwwc: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container coredns Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for coredns-56f4c55bf9-z4dlb: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for coredns-56f4c55bf9-z4dlb: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container coredns Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for coredns-56f4c55bf9-z4dlb: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container coredns Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for coredns-56f4c55bf9-z4dlb: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:44 +0000 UTC - event for metrics-server-c9574f845-k69qz: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:49 +0000 UTC - event for metrics-server-c9574f845-k69qz: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.863693651s (5.415763758s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:49 +0000 UTC - event for metrics-server-c9574f845-k69qz: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container metrics-server Jan 17 23:11:36.073: INFO: At 2023-01-17 22:59:49 +0000 UTC - event for metrics-server-c9574f845-k69qz: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container metrics-server Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:16 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-64tpl Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:16 +0000 UTC - event for kube-proxy-64tpl: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-64tpl to capz-conf-jrfrhh-md-0-6trbn Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:19 +0000 UTC - event for csi-azuredisk-controller: {deployment-controller } ScalingReplicaSet: Scaled up replica set csi-azuredisk-controller-7c87ff77db to 1 Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:19 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db: {replicaset-controller } SuccessfulCreate: Created pod: csi-azuredisk-controller-7c87ff77db-vg8zj Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:19 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-controller-7c87ff77db-vg8zj to capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:19 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-cbp7v Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:19 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-j2mcp Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:19 +0000 UTC - event for csi-azuredisk-node-cbp7v: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-cbp7v to capz-conf-jrfrhh-md-0-6trbn Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:19 +0000 UTC - event for csi-azuredisk-node-j2mcp: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-j2mcp to capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:20 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:20 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:21 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 784.934007ms (785.081807ms including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:21 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:21 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container liveness-probe Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:21 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container liveness-probe Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0" in 1.888476089s (2.617003831s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container csi-provisioner Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container csi-provisioner Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:24 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:24 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:24 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container node-driver-registrar Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:24 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container node-driver-registrar Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:24 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 879.850582ms (2.509859737s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:24 +0000 UTC - event for kube-proxy-64tpl: {kubelet capz-conf-jrfrhh-md-0-6trbn} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:26 +0000 UTC - event for kube-proxy-64tpl: {kubelet capz-conf-jrfrhh-md-0-6trbn} Started: Started container kube-proxy Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:26 +0000 UTC - event for kube-proxy-64tpl: {kubelet capz-conf-jrfrhh-md-0-6trbn} Created: Created container kube-proxy Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:26 +0000 UTC - event for kube-proxy-64tpl: {kubelet capz-conf-jrfrhh-md-0-6trbn} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2" in 1.834110392s (1.834182196s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:27 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container csi-attacher Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:27 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container csi-attacher Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:27 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0" in 3.393387687s (4.101231284s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:27 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:33 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Created: Created container liveness-probe Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:33 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:33 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Started: Started container liveness-probe Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:33 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 3.581691884s (8.81099869s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:40 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-6kgr7 Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:41 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-md7w8 Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:41 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 13.720018036s (16.930949988s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:41 +0000 UTC - event for csi-azuredisk-node-md7w8: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-md7w8 to capz-conf-jrfrhh-md-0-t8m7b Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:41 +0000 UTC - event for kube-proxy-6kgr7: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-6kgr7 to capz-conf-jrfrhh-md-0-t8m7b Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:42 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container azuredisk Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:42 +0000 UTC - event for csi-azuredisk-node-j2mcp: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container azuredisk Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:45 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container csi-snapshotter Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:45 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1" in 3.977891103s (17.322357482s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:45 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container csi-snapshotter Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:45 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:47 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container csi-resizer Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:47 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0" in 2.50253137s (2.50253717s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container csi-resizer Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" already present on machine Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container liveness-probe Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container liveness-probe Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" already present on machine Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Created: Created container azuredisk Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-vg8zj: {kubelet capz-conf-jrfrhh-control-plane-c7wdf} Started: Started container azuredisk Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 7.341242692s (15.128409796s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for external-attacher-leader-disk-csi-azure-com: {external-attacher-leader-disk.csi.azure.com/capz-conf-jrfrhh-control-plane-c7wdf } LeaderElection: capz-conf-jrfrhh-control-plane-c7wdf became leader Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:48 +0000 UTC - event for external-snapshotter-leader-disk-csi-azure-com: {external-snapshotter-leader-disk.csi.azure.com/capz-conf-jrfrhh-control-plane-c7wdf } LeaderElection: capz-conf-jrfrhh-control-plane-c7wdf became leader Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:49 +0000 UTC - event for disk-csi-azure-com: {disk.csi.azure.com/1673996449272-8081-disk.csi.azure.com } LeaderElection: 1673996449272-8081-disk-csi-azure-com became leader Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:49 +0000 UTC - event for external-resizer-disk-csi-azure-com: {external-resizer-disk-csi-azure-com/capz-conf-jrfrhh-control-plane-c7wdf } LeaderElection: capz-conf-jrfrhh-control-plane-c7wdf became leader Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:51 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Created: Created container node-driver-registrar Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:53 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:53 +0000 UTC - event for kube-proxy-6kgr7: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:54 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:00:54 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Started: Started container node-driver-registrar Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:00 +0000 UTC - event for kube-proxy-6kgr7: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2" in 2.09240068s (6.466495949s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:00 +0000 UTC - event for kube-proxy-6kgr7: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Created: Created container kube-proxy Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:00 +0000 UTC - event for kube-proxy-6kgr7: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Started: Started container kube-proxy Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:01 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Created: Created container liveness-probe Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:01 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:01 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 856.766082ms (7.321047065s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:01 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Started: Started container liveness-probe Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:08 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Created: Created container azuredisk Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:08 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 11.253851061s (14.021090655s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:09 +0000 UTC - event for csi-azuredisk-node-cbp7v: {kubelet capz-conf-jrfrhh-md-0-6trbn} Started: Started container azuredisk Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:12 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 5.885561081s (11.17322573s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:13 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Created: Created container node-driver-registrar Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:13 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Started: Started container node-driver-registrar Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:13 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:27 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 13.606547356s (13.606642987s including waiting) Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:27 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Started: Started container azuredisk Jan 17 23:11:36.073: INFO: At 2023-01-17 23:01:27 +0000 UTC - event for csi-azuredisk-node-md7w8: {kubelet capz-conf-jrfrhh-md-0-t8m7b} Created: Created container azuredisk Jan 17 23:11:36.134: INFO: POD NODE PHASE GRACE CONDITIONS Jan 17 23:11:36.134: INFO: coredns-56f4c55bf9-6mwwc capz-conf-jrfrhh-control-plane-c7wdf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:26 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:26 +0000 UTC }] Jan 17 23:11:36.135: INFO: coredns-56f4c55bf9-z4dlb capz-conf-jrfrhh-control-plane-c7wdf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:26 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:26 +0000 UTC }] Jan 17 23:11:36.135: INFO: csi-azuredisk-controller-7c87ff77db-vg8zj capz-conf-jrfrhh-control-plane-c7wdf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:48 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:19 +0000 UTC }] Jan 17 23:11:36.135: INFO: csi-azuredisk-node-cbp7v capz-conf-jrfrhh-md-0-6trbn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:01:09 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:01:09 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:19 +0000 UTC }] Jan 17 23:11:36.135: INFO: csi-azuredisk-node-j2mcp capz-conf-jrfrhh-control-plane-c7wdf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:43 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:43 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:19 +0000 UTC }] Jan 17 23:11:36.135: INFO: csi-azuredisk-node-md7w8 capz-conf-jrfrhh-md-0-t8m7b Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:01:27 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:01:27 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:41 +0000 UTC }] Jan 17 23:11:36.135: INFO: etcd-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:58:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:58:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:58:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:58:44 +0000 UTC }] Jan 17 23:11:36.135: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:36.135: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:36.135: INFO: kube-proxy-64tpl capz-conf-jrfrhh-md-0-6trbn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:17 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:27 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:27 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:16 +0000 UTC }] Jan 17 23:11:36.135: INFO: kube-proxy-6kgr7 capz-conf-jrfrhh-md-0-t8m7b Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:01:00 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:01:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:41 +0000 UTC }] Jan 17 23:11:36.135: INFO: kube-proxy-v4xgj capz-conf-jrfrhh-control-plane-c7wdf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:58:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:58:50 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:58:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:58:47 +0000 UTC }] Jan 17 23:11:36.135: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] Jan 17 23:11:36.135: INFO: metrics-server-c9574f845-k69qz capz-conf-jrfrhh-control-plane-c7wdf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:26 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 23:00:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-17 22:59:26 +0000 UTC }] Jan 17 23:11:36.135: INFO: Jan 17 23:11:37.971: INFO: Logging node info for node capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:38.165: INFO: Node Info: &Node{ObjectMeta:{capz-conf-jrfrhh-control-plane-c7wdf 9a5e2f8f-b9af-4fe1-aade-bbca049ee1f7 3193 0 2023-01-17 22:58:40 +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:eastus2 failure-domain.beta.kubernetes.io/zone:eastus2-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-jrfrhh-control-plane-c7wdf 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:eastus2-1 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:eastus2-1] map[cluster.x-k8s.io/cluster-name:capz-conf-jrfrhh cluster.x-k8s.io/cluster-namespace:capz-conf-jrfrhh cluster.x-k8s.io/machine:capz-conf-jrfrhh-control-plane-vlcjq cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-jrfrhh-control-plane csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-jrfrhh-control-plane-c7wdf","disk.csi.azure.com":"capz-conf-jrfrhh-control-plane-c7wdf"} 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.128.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-17 22:58:40 +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-17 22:58:43 +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-17 22:58:57 +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-17 22:59:26 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {calico-node Update v1 2023-01-17 22:59:36 +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-17 23:11:30 +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:capacity":{"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-jrfrhh/providers/Microsoft.Compute/virtualMachines/capz-conf-jrfrhh-control-plane-c7wdf,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/control-plane,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4123181056 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4018323456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-17 22:59:36 +0000 UTC,LastTransitionTime:2023-01-17 22:59:36 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-17 23:11:30 +0000 UTC,LastTransitionTime:2023-01-17 22:58:21 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-17 23:11:30 +0000 UTC,LastTransitionTime:2023-01-17 22:58:21 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-17 23:11:30 +0000 UTC,LastTransitionTime:2023-01-17 22:58:21 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-17 23:11:30 +0000 UTC,LastTransitionTime:2023-01-17 22:59:26 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-jrfrhh-control-plane-c7wdf,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:105e3e45bc2a4290b096bdb5333eb84b,SystemUUID:6724273e-1ebe-2a47-b694-15ae0e738c11,BootID:041f8b13-19a9-4a91-ac3d-3eb1c438f0c2,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1045+caf5140169cfe2,KubeProxyVersion:v1.27.0-alpha.0.1045+caf5140169cfe2,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:d30153f62ced88ebc925d85afd02cfade128c23ffae6fe9890cb397c2e0df04d gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.1032_5e9fc39d17fbc6],SizeBytes:35447824,},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:683a74cc1d47e4f69bb0995e96130d79e605c35fdc3fbc8415e85e0c850077ed gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.1032_5e9fc39d17fbc6],SizeBytes:32311027,},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:[capzci.azurecr.io/kube-proxy@sha256:e26db24b96aab189a74ad9d694c95f438deb391225f562e932f5c56627c91e1b capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2],SizeBytes:21490958,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:391422d653ac010ed9e411b54298606a16c49f50896ad54456429c8ced570373 gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.1032_5e9fc39d17fbc6],SizeBytes:21483540,},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:16071b3a7697761a18f51d14b1f34bbfdb5f69e9c6f156a18ab2ec7b1619a44f gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.1032_5e9fc39d17fbc6],SizeBytes:17469661,},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 17 23:11:38.165: INFO: Logging kubelet events for node capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:38.364: INFO: Logging pods the kubelet thinks is on node capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:38.590: INFO: calico-node-xpbmx started at 2023-01-17 22:58:56 +0000 UTC (2+1 container statuses recorded) Jan 17 23:11:38.590: INFO: Init container flexvol-driver ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Init container install-cni ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container calico-node ready: true, restart count 0 Jan 17 23:11:38.590: INFO: coredns-56f4c55bf9-6mwwc started at 2023-01-17 22:59:26 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.590: INFO: Container coredns ready: true, restart count 0 Jan 17 23:11:38.590: INFO: csi-node-driver-k2vj8 started at 2023-01-17 22:59:26 +0000 UTC (0+2 container statuses recorded) Jan 17 23:11:38.590: INFO: Container calico-csi ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container csi-node-driver-registrar ready: true, restart count 0 Jan 17 23:11:38.590: INFO: csi-azuredisk-node-j2mcp started at 2023-01-17 23:00:19 +0000 UTC (0+3 container statuses recorded) Jan 17 23:11:38.590: INFO: Container azuredisk ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container liveness-probe ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 17 23:11:38.590: INFO: csi-azuredisk-controller-7c87ff77db-vg8zj started at 2023-01-17 23:00:19 +0000 UTC (0+6 container statuses recorded) Jan 17 23:11:38.590: INFO: Container azuredisk ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container csi-attacher ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container csi-provisioner ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container csi-resizer ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container csi-snapshotter ready: true, restart count 0 Jan 17 23:11:38.590: INFO: Container liveness-probe ready: true, restart count 0 Jan 17 23:11:38.590: INFO: kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf started at <nil> (0+0 container statuses recorded) Jan 17 23:11:38.590: INFO: tigera-operator-54b47459dd-lhhrp started at 2023-01-17 22:58:49 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.590: INFO: Container tigera-operator ready: true, restart count 0 Jan 17 23:11:38.590: INFO: coredns-56f4c55bf9-z4dlb started at 2023-01-17 22:59:26 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.590: INFO: Container coredns ready: true, restart count 0 Jan 17 23:11:38.590: INFO: calico-kube-controllers-6b7b9c649d-n7tmb started at 2023-01-17 22:59:26 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.590: INFO: Container calico-kube-controllers ready: true, restart count 0 Jan 17 23:11:38.590: INFO: metrics-server-c9574f845-k69qz started at 2023-01-17 22:59:26 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.591: INFO: Container metrics-server ready: true, restart count 0 Jan 17 23:11:38.591: INFO: calico-apiserver-856658844b-z2ldj started at 2023-01-17 22:59:56 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.591: INFO: Container calico-apiserver ready: true, restart count 0 Jan 17 23:11:38.591: INFO: calico-apiserver-856658844b-6k2hh started at 2023-01-17 22:59:56 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.591: INFO: Container calico-apiserver ready: true, restart count 0 Jan 17 23:11:38.591: INFO: etcd-capz-conf-jrfrhh-control-plane-c7wdf started at 2023-01-17 22:58:44 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.591: INFO: Container etcd ready: true, restart count 0 Jan 17 23:11:38.591: INFO: kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf started at <nil> (0+0 container statuses recorded) Jan 17 23:11:38.591: INFO: calico-typha-574c4874f7-nx747 started at 2023-01-17 22:58:56 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.591: INFO: Container calico-typha ready: true, restart count 0 Jan 17 23:11:38.591: INFO: kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf started at <nil> (0+0 container statuses recorded) Jan 17 23:11:38.591: INFO: kube-proxy-v4xgj started at 2023-01-17 22:58:47 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:38.591: INFO: Container kube-proxy ready: true, restart count 0 Jan 17 23:11:39.244: INFO: Latency metrics for node capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:39.244: INFO: Logging node info for node capz-conf-jrfrhh-md-0-6trbn Jan 17 23:11:39.365: INFO: Node Info: &Node{ObjectMeta:{capz-conf-jrfrhh-md-0-6trbn b70bd0e6-cde1-4bb7-a97a-2ebdc0e7678f 2423 0 2023-01-17 23:00:16 +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:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-jrfrhh-md-0-6trbn kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-jrfrhh cluster.x-k8s.io/cluster-namespace:capz-conf-jrfrhh cluster.x-k8s.io/machine:capz-conf-jrfrhh-md-0-5958789f5c-2rgl9 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-jrfrhh-md-0-5958789f5c csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-jrfrhh-md-0-6trbn","disk.csi.azure.com":"capz-conf-jrfrhh-md-0-6trbn"} 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.169.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-17 23:00:16 +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-17 23:00:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {manager Update v1 2023-01-17 23:00:38 +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-17 23:00:50 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {calico-node Update v1 2023-01-17 23:01:20 +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-17 23:06:55 +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-jrfrhh/providers/Microsoft.Compute/virtualMachines/capz-conf-jrfrhh-md-0-6trbn,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4123181056 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4018323456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-17 23:01:20 +0000 UTC,LastTransitionTime:2023-01-17 23:01:20 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-17 23:06:55 +0000 UTC,LastTransitionTime:2023-01-17 23:00:16 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-17 23:06:55 +0000 UTC,LastTransitionTime:2023-01-17 23:00:16 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-17 23:06:55 +0000 UTC,LastTransitionTime:2023-01-17 23:00:16 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-17 23:06:55 +0000 UTC,LastTransitionTime:2023-01-17 23:00:49 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-jrfrhh-md-0-6trbn,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:2294ec9f56ba4b8fb44fc4652c28ac19,SystemUUID:0078dba6-8cac-cd4e-b312-d1da77ac8cdb,BootID:33bab2d1-a975-4a35-8abd-c5aa51b48aee,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1045+caf5140169cfe2,KubeProxyVersion:v1.27.0-alpha.0.1045+caf5140169cfe2,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:e26db24b96aab189a74ad9d694c95f438deb391225f562e932f5c56627c91e1b capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2],SizeBytes:21490958,},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 17 23:11:39.365: INFO: Logging kubelet events for node capz-conf-jrfrhh-md-0-6trbn Jan 17 23:11:39.564: INFO: Logging pods the kubelet thinks is on node capz-conf-jrfrhh-md-0-6trbn Jan 17 23:11:39.777: INFO: calico-node-dshk6 started at 2023-01-17 23:00:17 +0000 UTC (2+1 container statuses recorded) Jan 17 23:11:39.777: INFO: Init container flexvol-driver ready: true, restart count 0 Jan 17 23:11:39.777: INFO: Init container install-cni ready: true, restart count 0 Jan 17 23:11:39.777: INFO: Container calico-node ready: true, restart count 0 Jan 17 23:11:39.777: INFO: kube-proxy-64tpl started at 2023-01-17 23:00:17 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:39.777: INFO: Container kube-proxy ready: true, restart count 0 Jan 17 23:11:39.777: INFO: csi-azuredisk-node-cbp7v started at 2023-01-17 23:00:19 +0000 UTC (0+3 container statuses recorded) Jan 17 23:11:39.777: INFO: Container azuredisk ready: true, restart count 0 Jan 17 23:11:39.777: INFO: Container liveness-probe ready: true, restart count 0 Jan 17 23:11:39.777: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 17 23:11:39.777: INFO: calico-typha-574c4874f7-n44sn started at 2023-01-17 23:00:45 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:39.777: INFO: Container calico-typha ready: true, restart count 0 Jan 17 23:11:39.777: INFO: csi-node-driver-85rvd started at 2023-01-17 23:00:50 +0000 UTC (0+2 container statuses recorded) Jan 17 23:11:39.777: INFO: Container calico-csi ready: true, restart count 0 Jan 17 23:11:39.777: INFO: Container csi-node-driver-registrar ready: true, restart count 0 Jan 17 23:11:40.399: INFO: Latency metrics for node capz-conf-jrfrhh-md-0-6trbn Jan 17 23:11:40.399: INFO: Logging node info for node capz-conf-jrfrhh-md-0-t8m7b Jan 17 23:11:40.567: INFO: Node Info: &Node{ObjectMeta:{capz-conf-jrfrhh-md-0-t8m7b 94c69c46-d21e-4168-8ef6-2981bccda602 2459 0 2023-01-17 23:00:39 +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:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-jrfrhh-md-0-t8m7b kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-jrfrhh cluster.x-k8s.io/cluster-namespace:capz-conf-jrfrhh cluster.x-k8s.io/machine:capz-conf-jrfrhh-md-0-5958789f5c-m4k84 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-jrfrhh-md-0-5958789f5c csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-jrfrhh-md-0-t8m7b","disk.csi.azure.com":"capz-conf-jrfrhh-md-0-t8m7b"} 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.100.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-17 23:00:39 +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-17 23:00:41 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2023-01-17 23:01:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2023-01-17 23:01:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {calico-node Update v1 2023-01-17 23:01:36 +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-17 23:07:08 +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-jrfrhh/providers/Microsoft.Compute/virtualMachines/capz-conf-jrfrhh-md-0-t8m7b,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4123181056 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4018323456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-17 23:01:36 +0000 UTC,LastTransitionTime:2023-01-17 23:01:36 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-17 23:07:08 +0000 UTC,LastTransitionTime:2023-01-17 23:00:39 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-17 23:07:08 +0000 UTC,LastTransitionTime:2023-01-17 23:00:39 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-17 23:07:08 +0000 UTC,LastTransitionTime:2023-01-17 23:00:39 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-17 23:07:08 +0000 UTC,LastTransitionTime:2023-01-17 23:01:13 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-jrfrhh-md-0-t8m7b,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:b9cfe768745b42e89c6361e7ce7a9ec1,SystemUUID:bd8ab479-e93a-414a-ba27-cf7a21292c3b,BootID:6b8d5ff7-3d4c-4bf1-b701-c3cf95ff4acb,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1045+caf5140169cfe2,KubeProxyVersion:v1.27.0-alpha.0.1045+caf5140169cfe2,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:e26db24b96aab189a74ad9d694c95f438deb391225f562e932f5c56627c91e1b capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1045_caf5140169cfe2],SizeBytes:21490958,},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 17 23:11:40.567: INFO: Logging kubelet events for node capz-conf-jrfrhh-md-0-t8m7b Jan 17 23:11:40.769: INFO: Logging pods the kubelet thinks is on node capz-conf-jrfrhh-md-0-t8m7b Jan 17 23:11:40.999: INFO: csi-node-driver-rg6tv started at 2023-01-17 23:01:13 +0000 UTC (0+2 container statuses recorded) Jan 17 23:11:40.999: INFO: Container calico-csi ready: true, restart count 0 Jan 17 23:11:40.999: INFO: Container csi-node-driver-registrar ready: true, restart count 0 Jan 17 23:11:40.999: INFO: calico-node-jpwsx started at 2023-01-17 23:00:47 +0000 UTC (2+1 container statuses recorded) Jan 17 23:11:40.999: INFO: Init container flexvol-driver ready: true, restart count 0 Jan 17 23:11:40.999: INFO: Init container install-cni ready: true, restart count 0 Jan 17 23:11:40.999: INFO: Container calico-node ready: true, restart count 0 Jan 17 23:11:40.999: INFO: kube-proxy-6kgr7 started at 2023-01-17 23:00:47 +0000 UTC (0+1 container statuses recorded) Jan 17 23:11:40.999: INFO: Container kube-proxy ready: true, restart count 0 Jan 17 23:11:40.999: INFO: csi-azuredisk-node-md7w8 started at 2023-01-17 23:00:47 +0000 UTC (0+3 container statuses recorded) Jan 17 23:11:40.999: INFO: Container azuredisk ready: true, restart count 0 Jan 17 23:11:40.999: INFO: Container liveness-probe ready: true, restart count 0 Jan 17 23:11:40.999: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 17 23:11:41.608: INFO: Latency metrics for node capz-conf-jrfrhh-md-0-t8m7b Jan 17 23:11:41.793: INFO: Running kubectl logs on non-ready containers in kube-system Jan 17 23:11:42.165: INFO: Failed to get logs of pod kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf) Jan 17 23:11:42.165: INFO: Logs of kube-system/kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf:kube-apiserver on node capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:42.165: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-jrfrhh-control-plane-c7wdf:kube-apiserver Jan 17 23:11:42.566: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf) Jan 17 23:11:42.566: INFO: Logs of kube-system/kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf:kube-controller-manager on node capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:42.566: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf:kube-controller-manager Jan 17 23:11:42.964: INFO: Failed to get logs of pod kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf) Jan 17 23:11:42.964: INFO: Logs of kube-system/kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf:kube-scheduler on node capz-conf-jrfrhh-control-plane-c7wdf Jan 17 23:11:42.964: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf: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-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] kube-controller-manager-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] kube-scheduler-capz-conf-jrfrhh-control-plane-c7wdf capz-conf-jrfrhh-control-plane-c7wdf Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/17/23 23:11:42.965 < Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/17/23 23:11:42.965 (10m7.694s)
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/17/23 23:11:43.012from 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/17/23 23:11:43.012
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/17/23 23:11:43.015from 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/17/23 23:11:43.015
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/17/23 23:11:43.014from 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/17/23 23:11:43.014
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/17/23 23:11:43.015from 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/17/23 23:11:43.015
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/17/23 23:11:43.015from 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/17/23 23:11:43.015
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