PR #110981 pull-kubernetes-e2e-capz-conformance #1612789842914054144
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | claudiubelu: DO NOT MERGE: Windows unit tests |
| Result | SUCCESS |
| Tests | 25 failed / 27 succeeded |
| Started | |
| Elapsed | 54m5s |
| Revision | 9a237ccc56cb9b276b3362b4070e806a6e07636f |
| Refs |
110981 |
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/10/23 13:24:03.346from 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/10/23 13:24:03.346
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/10/23 13:24:03.339from 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/10/23 13:24:03.339
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/10/23 13:24:03.35from 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/10/23 13:24:03.35
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/10/23 13:24:03.339from 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/10/23 13:24:03.339
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/10/23 13:24:03.353from 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/10/23 13:24:03.353
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/10/23 13:24:03.353from 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/10/23 13:24:03.353
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/10/23 13:24:03.347from 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/10/23 13:24:03.347
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/10/23 13:24:03.452from 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/10/23 13:24:03.452
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/10/23 13:24:03.352from 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/10/23 13:24:03.352
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/10/23 13:24:03.356from 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/10/23 13:24:03.356
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/10/23 13:24:03.456from 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/10/23 13:24:03.456
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/10/23 13:24:03.367from 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/10/23 13:24:03.367
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/10/23 13:24:03.453from 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/10/23 13:24:03.453
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/10/23 13:24:03.454from 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/10/23 13:24:03.454
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/10/23 13:24:03.353from 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/10/23 13:24:03.353
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/10/23 13:24:03.354from 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/10/23 13:24:03.354
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/10/23 13:24:03.348from 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/10/23 13:24:03.348
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/10/23 13:24:03.363from 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/10/23 13:24:03.363
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/10/23 13:24:03.339from 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/10/23 13:24:03.339
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/10/23 13:24:03.354from 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/10/23 13:24:03.354
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/10/23 13:24:03.352from 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/10/23 13:24:03.352
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/10/23 13:24:03.455from 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/10/23 13:24:03.455
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/10/23 13:24:03.348from 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/10/23 13:24:03.348
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/10/23 13:24:03.443from 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/10/23 13:24:03.443
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-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:249 @ 01/10/23 13:24:03.336from junit.kubetest.01.xml
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/10/23 13:13:57.499 Jan 10 13:13:57.499: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 10 13:13:57.503: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 10 13:13:57.721: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 10 13:13:57.896: INFO: The status of Pod calico-node-hrhsd is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:13:57.896: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:13:57.896: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:13:57.896: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:13:57.896: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 10 13:13:57.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:13:57.896: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:13:57.896: INFO: calico-node-hrhsd capz-conf-r48k3z-md-0-77wj5 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:46 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:28 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:28 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:21 +0000 UTC }] Jan 10 13:13:57.897: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:13:57.897: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:13:57.897: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:13:57.897: INFO: Jan 10 13:14:00.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:00.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:00.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:00.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Jan 10 13:14:00.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:00.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:00.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:00.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:00.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:00.023: INFO: Jan 10 13:14:02.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:02.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:02.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:02.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Jan 10 13:14:02.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:02.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:02.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:02.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:02.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:02.016: INFO: Jan 10 13:14:04.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:04.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:04.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:04.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Jan 10 13:14:04.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:04.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:04.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:04.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:04.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:04.017: INFO: Jan 10 13:14:06.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:06.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:06.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:06.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Jan 10 13:14:06.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:06.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:06.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:06.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:06.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:06.017: INFO: Jan 10 13:14:08.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:08.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:08.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:08.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Jan 10 13:14:08.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:08.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:08.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:08.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:08.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:08.017: INFO: Jan 10 13:14:10.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:10.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:10.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:10.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Jan 10 13:14:10.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:10.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:10.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:10.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:10.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:10.018: INFO: Jan 10 13:14:12.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:12.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:12.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:12.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Jan 10 13:14:12.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:12.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:12.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:12.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:12.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:12.015: INFO: Jan 10 13:14:14.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:14.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:14.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:14.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Jan 10 13:14:14.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:14.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:14.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:14.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:14.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:14.015: INFO: Jan 10 13:14:16.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:16.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:16.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:16.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Jan 10 13:14:16.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:16.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:16.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:16.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:16.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:16.016: INFO: Jan 10 13:14:18.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:18.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:18.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:18.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Jan 10 13:14:18.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:18.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:18.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:18.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:18.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:18.017: INFO: Jan 10 13:14:20.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:20.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:20.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:20.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Jan 10 13:14:20.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:20.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:20.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:20.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:20.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:20.017: INFO: Jan 10 13:14:22.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:22.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:22.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:22.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Jan 10 13:14:22.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:22.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:22.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:22.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:22.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:22.017: INFO: Jan 10 13:14:24.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:24.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:24.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:24.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Jan 10 13:14:24.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:24.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:24.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:24.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:24.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:24.016: INFO: Jan 10 13:14:26.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:26.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:26.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:26.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Jan 10 13:14:26.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:26.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:26.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:26.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:26.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:26.017: INFO: Jan 10 13:14:28.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:28.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:28.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:28.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Jan 10 13:14:28.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:28.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:28.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:28.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:28.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:28.017: INFO: Jan 10 13:14:30.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:30.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:30.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:30.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Jan 10 13:14:30.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:30.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:30.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:30.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:30.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:30.018: INFO: Jan 10 13:14:32.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:32.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:32.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:32.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Jan 10 13:14:32.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:32.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:32.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:32.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:32.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:32.016: INFO: Jan 10 13:14:34.025: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:34.025: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:34.025: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:34.025: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Jan 10 13:14:34.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:34.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:34.025: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:34.025: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:34.025: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:34.025: INFO: Jan 10 13:14:36.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:36.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:36.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:36.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Jan 10 13:14:36.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:36.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:36.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:36.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:36.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:36.016: INFO: Jan 10 13:14:38.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:38.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:38.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:38.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Jan 10 13:14:38.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:38.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:38.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:38.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:38.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:38.016: INFO: Jan 10 13:14:40.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:40.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:40.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:40.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Jan 10 13:14:40.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:40.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:40.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:40.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:40.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:40.017: INFO: Jan 10 13:14:42.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:42.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:42.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:42.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Jan 10 13:14:42.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:42.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:42.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:42.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:42.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:42.015: INFO: Jan 10 13:14:44.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:44.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:44.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:44.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Jan 10 13:14:44.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:44.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:44.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:44.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:44.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:44.016: INFO: Jan 10 13:14:46.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:46.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:46.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:46.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Jan 10 13:14:46.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:46.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:46.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:46.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:46.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:46.016: INFO: Jan 10 13:14:48.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:48.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:48.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:48.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Jan 10 13:14:48.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:48.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:48.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:48.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:48.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:48.018: INFO: Jan 10 13:14:50.047: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:50.047: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:50.047: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:50.047: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Jan 10 13:14:50.047: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:50.047: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:50.047: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:50.047: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:50.047: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:50.047: INFO: Jan 10 13:14:52.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:52.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:52.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:52.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Jan 10 13:14:52.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:52.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:52.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:52.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:52.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:52.017: INFO: Jan 10 13:14:54.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:54.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:54.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:54.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Jan 10 13:14:54.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:54.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:54.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:54.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:54.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:54.016: INFO: Jan 10 13:14:56.031: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:56.031: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:56.031: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:56.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Jan 10 13:14:56.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:56.031: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:56.031: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:56.031: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:56.031: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:56.031: INFO: Jan 10 13:14:58.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:58.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:58.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:14:58.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Jan 10 13:14:58.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:14:58.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:14:58.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:58.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:58.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:14:58.015: INFO: Jan 10 13:15:00.152: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:00.152: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:00.152: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:00.152: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Jan 10 13:15:00.152: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:00.152: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:00.152: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:00.152: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:00.152: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:00.152: INFO: Jan 10 13:15:02.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:02.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:02.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:02.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Jan 10 13:15:02.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:02.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:02.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:02.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:02.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:02.016: INFO: Jan 10 13:15:04.083: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:04.083: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:04.083: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:04.083: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Jan 10 13:15:04.083: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:04.083: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:04.083: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:04.083: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:04.083: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:04.083: INFO: Jan 10 13:15:06.138: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:06.138: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:06.138: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:06.138: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Jan 10 13:15:06.138: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:06.138: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:06.138: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:06.138: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:06.138: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:06.138: INFO: Jan 10 13:15:08.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:08.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:08.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:08.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Jan 10 13:15:08.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:08.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:08.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:08.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:08.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:08.018: INFO: Jan 10 13:15:10.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:10.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:10.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:10.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Jan 10 13:15:10.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:10.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:10.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:10.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:10.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:10.016: INFO: Jan 10 13:15:12.103: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:12.103: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:12.103: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:12.103: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Jan 10 13:15:12.103: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:12.103: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:12.103: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:12.103: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:12.103: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:12.103: INFO: Jan 10 13:15:14.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:14.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:14.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:14.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Jan 10 13:15:14.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:14.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:14.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:14.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:14.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:14.016: INFO: Jan 10 13:15:16.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:16.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:16.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:16.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Jan 10 13:15:16.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:16.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:16.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:16.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:16.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:16.017: INFO: Jan 10 13:15:18.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:18.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:18.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:18.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Jan 10 13:15:18.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:18.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:18.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:18.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:18.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:18.017: INFO: Jan 10 13:15:20.025: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:20.025: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:20.025: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:20.025: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Jan 10 13:15:20.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:20.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:20.025: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:20.025: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:20.025: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:20.025: INFO: Jan 10 13:15:22.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:22.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:22.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:22.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Jan 10 13:15:22.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:22.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:22.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:22.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:22.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:22.016: INFO: Jan 10 13:15:24.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:24.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:24.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:24.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Jan 10 13:15:24.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:24.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:24.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:24.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:24.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:24.017: INFO: Jan 10 13:15:26.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:26.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:26.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:26.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Jan 10 13:15:26.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:26.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:26.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:26.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:26.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:26.022: INFO: Jan 10 13:15:28.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:28.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:28.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:28.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Jan 10 13:15:28.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:28.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:28.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:28.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:28.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:28.016: INFO: Jan 10 13:15:30.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:30.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:30.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:30.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Jan 10 13:15:30.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:30.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:30.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:30.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:30.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:30.016: INFO: Jan 10 13:15:32.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:32.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:32.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:32.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Jan 10 13:15:32.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:32.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:32.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:32.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:32.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:32.019: INFO: Jan 10 13:15:34.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:34.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:34.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:34.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Jan 10 13:15:34.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:34.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:34.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:34.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:34.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:34.018: INFO: Jan 10 13:15:36.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:36.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:36.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:36.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Jan 10 13:15:36.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:36.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:36.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:36.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:36.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:36.017: INFO: Jan 10 13:15:38.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:38.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:38.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:38.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Jan 10 13:15:38.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:38.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:38.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:38.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:38.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:38.016: INFO: Jan 10 13:15:40.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:40.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:40.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:40.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Jan 10 13:15:40.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:40.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:40.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:40.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:40.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:40.017: INFO: Jan 10 13:15:42.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:42.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:42.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:42.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Jan 10 13:15:42.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:42.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:42.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:42.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:42.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:42.017: INFO: Jan 10 13:15:44.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:44.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:44.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:44.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Jan 10 13:15:44.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:44.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:44.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:44.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:44.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:44.015: INFO: Jan 10 13:15:46.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:46.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:46.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:46.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Jan 10 13:15:46.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:46.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:46.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:46.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:46.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:46.017: INFO: Jan 10 13:15:48.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:48.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:48.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:48.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Jan 10 13:15:48.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:48.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:48.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:48.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:48.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:48.017: INFO: Jan 10 13:15:50.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:50.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:50.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:50.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Jan 10 13:15:50.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:50.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:50.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:50.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:50.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:50.019: INFO: Jan 10 13:15:52.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:52.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:52.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:52.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Jan 10 13:15:52.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:52.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:52.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:52.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:52.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:52.016: INFO: Jan 10 13:15:54.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:54.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:54.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:54.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Jan 10 13:15:54.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:54.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:54.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:54.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:54.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:54.016: INFO: Jan 10 13:15:56.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:56.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:56.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:56.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Jan 10 13:15:56.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:56.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:56.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:56.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:56.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:56.016: INFO: Jan 10 13:15:58.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:58.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:58.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:15:58.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Jan 10 13:15:58.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:15:58.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:15:58.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:58.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:58.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:15:58.016: INFO: Jan 10 13:16:00.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:00.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:00.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:00.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Jan 10 13:16:00.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:00.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:00.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:00.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:00.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:00.019: INFO: Jan 10 13:16:02.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:02.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:02.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:02.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Jan 10 13:16:02.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:02.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:02.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:02.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:02.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:02.018: INFO: Jan 10 13:16:04.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:04.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:04.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:04.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Jan 10 13:16:04.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:04.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:04.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:04.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:04.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:04.016: INFO: Jan 10 13:16:06.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:06.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:06.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:06.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Jan 10 13:16:06.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:06.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:06.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:06.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:06.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:06.016: INFO: Jan 10 13:16:08.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:08.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:08.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:08.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Jan 10 13:16:08.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:08.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:08.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:08.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:08.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:08.016: INFO: Jan 10 13:16:10.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:10.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:10.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:10.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Jan 10 13:16:10.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:10.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:10.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:10.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:10.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:10.017: INFO: Jan 10 13:16:12.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:12.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:12.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:12.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Jan 10 13:16:12.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:12.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:12.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:12.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:12.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:12.016: INFO: Jan 10 13:16:14.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:14.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:14.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:14.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Jan 10 13:16:14.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:14.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:14.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:14.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:14.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:14.016: INFO: Jan 10 13:16:16.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:16.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:16.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:16.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Jan 10 13:16:16.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:16.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:16.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:16.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:16.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:16.017: INFO: Jan 10 13:16:18.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:18.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:18.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:18.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Jan 10 13:16:18.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:18.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:18.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:18.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:18.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:18.017: INFO: Jan 10 13:16:20.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:20.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:20.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:20.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Jan 10 13:16:20.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:20.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:20.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:20.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:20.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:20.021: INFO: Jan 10 13:16:22.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:22.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:22.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:22.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Jan 10 13:16:22.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:22.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:22.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:22.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:22.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:22.016: INFO: Jan 10 13:16:24.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:24.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:24.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:24.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Jan 10 13:16:24.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:24.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:24.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:24.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:24.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:24.016: INFO: Jan 10 13:16:26.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:26.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:26.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:26.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Jan 10 13:16:26.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:26.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:26.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:26.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:26.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:26.018: INFO: Jan 10 13:16:28.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:28.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:28.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:28.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Jan 10 13:16:28.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:28.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:28.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:28.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:28.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:28.015: INFO: Jan 10 13:16:30.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:30.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:30.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:30.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Jan 10 13:16:30.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:30.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:30.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:30.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:30.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:30.016: INFO: Jan 10 13:16:32.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:32.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:32.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:32.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Jan 10 13:16:32.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:32.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:32.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:32.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:32.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:32.015: INFO: Jan 10 13:16:34.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:34.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:34.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:34.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Jan 10 13:16:34.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:34.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:34.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:34.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:34.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:34.015: INFO: Jan 10 13:16:36.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:36.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:36.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:36.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Jan 10 13:16:36.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:36.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:36.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:36.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:36.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:36.017: INFO: Jan 10 13:16:38.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:38.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:38.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:38.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Jan 10 13:16:38.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:38.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:38.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:38.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:38.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:38.019: INFO: Jan 10 13:16:40.125: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:40.125: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:40.125: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:40.125: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Jan 10 13:16:40.125: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:40.125: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:40.125: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:40.125: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:40.125: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:40.125: INFO: Jan 10 13:16:42.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:42.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:42.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:42.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Jan 10 13:16:42.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:42.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:42.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:42.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:42.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:42.023: INFO: Jan 10 13:16:44.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:44.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:44.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:44.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Jan 10 13:16:44.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:44.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:44.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:44.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:44.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:44.021: INFO: Jan 10 13:16:46.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:46.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:46.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:46.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Jan 10 13:16:46.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:46.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:46.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:46.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:46.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:46.015: INFO: Jan 10 13:16:48.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:48.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:48.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:48.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Jan 10 13:16:48.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:48.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:48.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:48.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:48.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:48.017: INFO: Jan 10 13:16:50.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:50.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:50.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:50.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Jan 10 13:16:50.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:50.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:50.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:50.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:50.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:50.017: INFO: Jan 10 13:16:52.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:52.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:52.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:52.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Jan 10 13:16:52.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:52.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:52.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:52.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:52.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:52.015: INFO: Jan 10 13:16:54.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:54.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:54.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:54.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Jan 10 13:16:54.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:54.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:54.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:54.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:54.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:54.018: INFO: Jan 10 13:16:56.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:56.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:56.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:56.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Jan 10 13:16:56.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:56.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:56.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:56.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:56.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:56.017: INFO: Jan 10 13:16:58.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:58.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:58.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:16:58.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Jan 10 13:16:58.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:16:58.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:16:58.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:58.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:58.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:16:58.019: INFO: Jan 10 13:17:00.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:00.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:00.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:00.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Jan 10 13:17:00.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:00.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:00.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:00.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:00.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:00.018: INFO: Jan 10 13:17:02.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:02.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:02.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:02.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Jan 10 13:17:02.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:02.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:02.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:02.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:02.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:02.018: INFO: Jan 10 13:17:04.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:04.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:04.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:04.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Jan 10 13:17:04.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:04.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:04.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:04.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:04.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:04.017: INFO: Jan 10 13:17:06.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:06.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:06.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:06.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Jan 10 13:17:06.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:06.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:06.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:06.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:06.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:06.019: INFO: Jan 10 13:17:08.014: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:08.014: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:08.014: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:08.014: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Jan 10 13:17:08.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:08.014: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:08.014: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:08.014: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:08.014: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:08.014: INFO: Jan 10 13:17:10.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:10.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:10.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:10.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Jan 10 13:17:10.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:10.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:10.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:10.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:10.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:10.017: INFO: Jan 10 13:17:12.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:12.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:12.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:12.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Jan 10 13:17:12.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:12.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:12.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:12.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:12.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:12.017: INFO: Jan 10 13:17:14.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:14.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:14.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:14.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Jan 10 13:17:14.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:14.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:14.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:14.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:14.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:14.019: INFO: Jan 10 13:17:16.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:16.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:16.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:16.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Jan 10 13:17:16.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:16.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:16.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:16.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:16.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:16.017: INFO: Jan 10 13:17:18.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:18.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:18.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:18.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Jan 10 13:17:18.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:18.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:18.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:18.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:18.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:18.017: INFO: Jan 10 13:17:20.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:20.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:20.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:20.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Jan 10 13:17:20.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:20.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:20.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:20.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:20.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:20.018: INFO: Jan 10 13:17:22.014: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:22.014: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:22.014: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:22.014: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Jan 10 13:17:22.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:22.014: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:22.014: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:22.014: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:22.014: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:22.014: INFO: Jan 10 13:17:24.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:24.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:24.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:24.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Jan 10 13:17:24.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:24.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:24.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:24.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:24.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:24.016: INFO: Jan 10 13:17:26.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:26.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:26.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:26.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Jan 10 13:17:26.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:26.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:26.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:26.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:26.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:26.017: INFO: Jan 10 13:17:28.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:28.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:28.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:28.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Jan 10 13:17:28.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:28.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:28.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:28.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:28.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:28.017: INFO: Jan 10 13:17:30.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:30.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:30.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:30.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Jan 10 13:17:30.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:30.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:30.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:30.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:30.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:30.015: INFO: Jan 10 13:17:32.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:32.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:32.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:32.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Jan 10 13:17:32.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:32.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:32.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:32.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:32.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:32.016: INFO: Jan 10 13:17:34.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:34.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:34.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:34.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Jan 10 13:17:34.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:34.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:34.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:34.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:34.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:34.015: INFO: Jan 10 13:17:36.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:36.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:36.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:36.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Jan 10 13:17:36.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:36.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:36.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:36.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:36.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:36.016: INFO: Jan 10 13:17:38.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:38.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:38.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:38.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Jan 10 13:17:38.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:38.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:38.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:38.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:38.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:38.017: INFO: Jan 10 13:17:40.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:40.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:40.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:40.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Jan 10 13:17:40.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:40.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:40.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:40.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:40.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:40.015: INFO: Jan 10 13:17:42.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:42.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:42.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:42.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Jan 10 13:17:42.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:42.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:42.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:42.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:42.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:42.015: INFO: Jan 10 13:17:44.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:44.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:44.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:44.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Jan 10 13:17:44.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:44.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:44.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:44.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:44.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:44.017: INFO: Jan 10 13:17:46.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:46.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:46.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:46.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Jan 10 13:17:46.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:46.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:46.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:46.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:46.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:46.018: INFO: Jan 10 13:17:48.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:48.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:48.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:48.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Jan 10 13:17:48.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:48.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:48.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:48.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:48.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:48.017: INFO: Jan 10 13:17:50.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:50.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:50.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:50.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Jan 10 13:17:50.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:50.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:50.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:50.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:50.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:50.016: INFO: Jan 10 13:17:52.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:52.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:52.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:52.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Jan 10 13:17:52.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:52.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:52.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:52.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:52.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:52.021: INFO: Jan 10 13:17:54.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:54.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:54.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:54.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Jan 10 13:17:54.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:54.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:54.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:54.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:54.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:54.015: INFO: Jan 10 13:17:56.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:56.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:56.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:56.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Jan 10 13:17:56.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:56.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:56.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:56.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:56.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:56.019: INFO: Jan 10 13:17:58.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:58.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:58.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:17:58.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Jan 10 13:17:58.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:17:58.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:17:58.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:58.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:58.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:17:58.017: INFO: Jan 10 13:18:00.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:00.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:00.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:00.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Jan 10 13:18:00.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:00.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:00.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:00.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:00.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:00.016: INFO: Jan 10 13:18:02.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:02.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:02.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:02.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Jan 10 13:18:02.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:02.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:02.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:02.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:02.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:02.018: INFO: Jan 10 13:18:04.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:04.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:04.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:04.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Jan 10 13:18:04.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:04.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:04.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:04.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:04.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:04.018: INFO: Jan 10 13:18:06.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:06.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:06.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:06.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Jan 10 13:18:06.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:06.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:06.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:06.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:06.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:06.017: INFO: Jan 10 13:18:08.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:08.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:08.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:08.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Jan 10 13:18:08.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:08.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:08.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:08.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:08.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:08.017: INFO: Jan 10 13:18:10.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:10.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:10.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:10.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Jan 10 13:18:10.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:10.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:10.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:10.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:10.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:10.017: INFO: Jan 10 13:18:12.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:12.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:12.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:12.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Jan 10 13:18:12.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:12.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:12.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:12.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:12.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:12.016: INFO: Jan 10 13:18:14.026: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:14.026: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:14.026: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:14.026: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Jan 10 13:18:14.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:14.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:14.026: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:14.026: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:14.026: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:14.026: INFO: Jan 10 13:18:16.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:16.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:16.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:16.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Jan 10 13:18:16.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:16.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:16.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:16.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:16.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:16.021: INFO: Jan 10 13:18:18.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:18.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:18.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:18.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Jan 10 13:18:18.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:18.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:18.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:18.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:18.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:18.017: INFO: Jan 10 13:18:20.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:20.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:20.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:20.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Jan 10 13:18:20.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:20.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:20.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:20.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:20.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:20.019: INFO: Jan 10 13:18:22.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:22.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:22.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:22.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Jan 10 13:18:22.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:22.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:22.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:22.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:22.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:22.017: INFO: Jan 10 13:18:24.042: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:24.042: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:24.042: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:24.042: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Jan 10 13:18:24.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:24.042: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:24.042: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:24.042: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:24.042: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:24.042: INFO: Jan 10 13:18:26.014: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:26.014: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:26.014: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:26.014: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Jan 10 13:18:26.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:26.014: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:26.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:26.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:26.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:26.015: INFO: Jan 10 13:18:28.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:28.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:28.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:28.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Jan 10 13:18:28.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:28.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:28.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:28.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:28.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:28.018: INFO: Jan 10 13:18:30.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:30.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:30.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:30.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Jan 10 13:18:30.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:30.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:30.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:30.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:30.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:30.017: INFO: Jan 10 13:18:32.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:32.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:32.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:32.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Jan 10 13:18:32.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:32.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:32.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:32.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:32.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:32.016: INFO: Jan 10 13:18:34.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:34.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:34.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:34.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Jan 10 13:18:34.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:34.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:34.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:34.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:34.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:34.019: INFO: Jan 10 13:18:36.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:36.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:36.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:36.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Jan 10 13:18:36.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:36.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:36.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:36.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:36.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:36.016: INFO: Jan 10 13:18:38.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:38.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:38.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:38.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Jan 10 13:18:38.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:38.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:38.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:38.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:38.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:38.022: INFO: Jan 10 13:18:40.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:40.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:40.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:40.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Jan 10 13:18:40.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:40.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:40.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:40.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:40.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:40.021: INFO: Jan 10 13:18:42.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:42.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:42.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:42.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Jan 10 13:18:42.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:42.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:42.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:42.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:42.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:42.015: INFO: Jan 10 13:18:44.028: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:44.028: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:44.028: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:44.028: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Jan 10 13:18:44.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:44.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:44.028: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:44.028: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:44.028: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:44.028: INFO: Jan 10 13:18:46.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:46.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:46.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:46.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Jan 10 13:18:46.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:46.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:46.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:46.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:46.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:46.017: INFO: Jan 10 13:18:48.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:48.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:48.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:48.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Jan 10 13:18:48.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:48.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:48.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:48.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:48.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:48.015: INFO: Jan 10 13:18:50.054: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:50.054: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:50.054: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:50.054: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Jan 10 13:18:50.054: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:50.054: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:50.054: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:50.054: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:50.054: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:50.054: INFO: Jan 10 13:18:52.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:52.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:52.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:52.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Jan 10 13:18:52.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:52.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:52.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:52.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:52.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:52.016: INFO: Jan 10 13:18:54.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:54.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:54.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:54.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Jan 10 13:18:54.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:54.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:54.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:54.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:54.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:54.016: INFO: Jan 10 13:18:56.014: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:56.014: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:56.014: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:56.014: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Jan 10 13:18:56.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:56.014: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:56.014: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:56.014: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:56.014: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:56.014: INFO: Jan 10 13:18:58.014: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:58.014: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:58.014: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:18:58.014: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Jan 10 13:18:58.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:18:58.014: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:18:58.014: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:58.014: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:58.014: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:18:58.014: INFO: Jan 10 13:19:00.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:00.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:00.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:00.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Jan 10 13:19:00.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:00.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:00.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:00.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:00.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:00.016: INFO: Jan 10 13:19:02.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:02.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:02.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:02.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Jan 10 13:19:02.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:02.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:02.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:02.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:02.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:02.015: INFO: Jan 10 13:19:04.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:04.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:04.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:04.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Jan 10 13:19:04.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:04.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:04.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:04.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:04.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:04.017: INFO: Jan 10 13:19:06.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:06.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:06.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:06.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Jan 10 13:19:06.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:06.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:06.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:06.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:06.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:06.016: INFO: Jan 10 13:19:08.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:08.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:08.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:08.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Jan 10 13:19:08.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:08.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:08.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:08.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:08.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:08.022: INFO: Jan 10 13:19:10.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:10.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:10.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:10.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Jan 10 13:19:10.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:10.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:10.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:10.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:10.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:10.015: INFO: Jan 10 13:19:12.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:12.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:12.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:12.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Jan 10 13:19:12.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:12.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:12.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:12.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:12.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:12.015: INFO: Jan 10 13:19:14.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:14.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:14.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:14.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Jan 10 13:19:14.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:14.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:14.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:14.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:14.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:14.016: INFO: Jan 10 13:19:16.014: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:16.014: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:16.014: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:16.014: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Jan 10 13:19:16.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:16.014: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:16.014: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:16.014: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:16.014: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:16.014: INFO: Jan 10 13:19:18.044: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:18.044: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:18.044: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:18.044: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Jan 10 13:19:18.044: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:18.044: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:18.044: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:18.044: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:18.044: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:18.044: INFO: Jan 10 13:19:20.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:20.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:20.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:20.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Jan 10 13:19:20.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:20.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:20.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:20.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:20.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:20.016: INFO: Jan 10 13:19:22.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:22.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:22.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:22.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Jan 10 13:19:22.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:22.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:22.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:22.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:22.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:22.016: INFO: Jan 10 13:19:24.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:24.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:24.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:24.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Jan 10 13:19:24.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:24.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:24.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:24.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:24.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:24.016: INFO: Jan 10 13:19:26.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:26.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:26.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:26.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Jan 10 13:19:26.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:26.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:26.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:26.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:26.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:26.015: INFO: Jan 10 13:19:28.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:28.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:28.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:28.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Jan 10 13:19:28.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:28.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:28.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:28.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:28.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:28.018: INFO: Jan 10 13:19:30.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:30.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:30.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:30.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Jan 10 13:19:30.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:30.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:30.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:30.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:30.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:30.017: INFO: Jan 10 13:19:32.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:32.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:32.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:32.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Jan 10 13:19:32.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:32.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:32.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:32.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:32.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:32.016: INFO: Jan 10 13:19:34.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:34.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:34.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:34.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Jan 10 13:19:34.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:34.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:34.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:34.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:34.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:34.015: INFO: Jan 10 13:19:36.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:36.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:36.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:36.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Jan 10 13:19:36.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:36.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:36.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:36.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:36.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:36.015: INFO: Jan 10 13:19:38.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:38.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:38.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:38.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Jan 10 13:19:38.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:38.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:38.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:38.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:38.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:38.016: INFO: Jan 10 13:19:40.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:40.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:40.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:40.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Jan 10 13:19:40.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:40.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:40.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:40.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:40.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:40.017: INFO: Jan 10 13:19:42.014: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:42.014: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:42.014: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:42.014: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Jan 10 13:19:42.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:42.014: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:42.014: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:42.014: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:42.014: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:42.014: INFO: Jan 10 13:19:44.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:44.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:44.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:44.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Jan 10 13:19:44.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:44.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:44.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:44.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:44.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:44.017: INFO: Jan 10 13:19:46.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:46.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:46.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:46.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Jan 10 13:19:46.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:46.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:46.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:46.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:46.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:46.016: INFO: Jan 10 13:19:48.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:48.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:48.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:48.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Jan 10 13:19:48.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:48.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:48.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:48.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:48.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:48.016: INFO: Jan 10 13:19:50.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:50.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:50.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:50.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Jan 10 13:19:50.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:50.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:50.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:50.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:50.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:50.017: INFO: Jan 10 13:19:52.016: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:52.016: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:52.016: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:52.016: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Jan 10 13:19:52.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:52.016: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:52.016: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:52.016: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:52.016: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:52.016: INFO: Jan 10 13:19:54.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:54.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:54.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:54.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Jan 10 13:19:54.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:54.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:54.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:54.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:54.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:54.020: INFO: Jan 10 13:19:56.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:56.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:56.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:56.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Jan 10 13:19:56.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:56.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:56.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:56.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:56.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:56.021: INFO: Jan 10 13:19:58.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:58.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:58.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:19:58.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Jan 10 13:19:58.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:19:58.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:19:58.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:58.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:58.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:19:58.020: INFO: Jan 10 13:20:00.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:00.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:00.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:00.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Jan 10 13:20:00.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:00.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:00.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:00.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:00.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:00.020: INFO: Jan 10 13:20:02.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:02.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:02.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:02.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Jan 10 13:20:02.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:02.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:02.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:02.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:02.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:02.023: INFO: Jan 10 13:20:04.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:04.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:04.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:04.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Jan 10 13:20:04.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:04.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:04.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:04.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:04.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:04.019: INFO: Jan 10 13:20:06.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:06.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:06.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:06.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Jan 10 13:20:06.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:06.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:06.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:06.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:06.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:06.015: INFO: Jan 10 13:20:08.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:08.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:08.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:08.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Jan 10 13:20:08.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:08.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:08.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:08.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:08.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:08.022: INFO: Jan 10 13:20:10.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:10.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:10.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:10.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Jan 10 13:20:10.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:10.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:10.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:10.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:10.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:10.018: INFO: Jan 10 13:20:12.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:12.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:12.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:12.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Jan 10 13:20:12.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:12.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:12.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:12.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:12.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:12.015: INFO: Jan 10 13:20:14.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:14.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:14.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:14.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Jan 10 13:20:14.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:14.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:14.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:14.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:14.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:14.017: INFO: Jan 10 13:20:16.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:16.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:16.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:16.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Jan 10 13:20:16.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:16.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:16.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:16.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:16.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:16.015: INFO: Jan 10 13:20:18.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:18.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:18.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:18.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Jan 10 13:20:18.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:18.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:18.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:18.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:18.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:18.019: INFO: Jan 10 13:20:20.015: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:20.015: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:20.015: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:20.015: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Jan 10 13:20:20.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:20.015: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:20.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:20.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:20.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:20.015: INFO: Jan 10 13:20:22.014: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:22.014: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:22.014: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:22.014: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Jan 10 13:20:22.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:22.014: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:22.015: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:22.015: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:22.015: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:22.015: INFO: Jan 10 13:20:24.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:24.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:24.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:24.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Jan 10 13:20:24.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:24.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:24.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:24.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:24.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:24.018: INFO: Jan 10 13:20:26.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:26.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:26.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:26.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Jan 10 13:20:26.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:26.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:26.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:26.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:26.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:26.018: INFO: Jan 10 13:20:28.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:28.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:28.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:28.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Jan 10 13:20:28.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:28.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:28.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:28.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:28.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:28.023: INFO: Jan 10 13:20:30.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:30.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:30.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:30.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Jan 10 13:20:30.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:30.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:30.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:30.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:30.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:30.022: INFO: Jan 10 13:20:32.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:32.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:32.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:32.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Jan 10 13:20:32.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:32.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:32.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:32.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:32.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:32.017: INFO: Jan 10 13:20:34.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:34.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:34.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:34.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Jan 10 13:20:34.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:34.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:34.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:34.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:34.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:34.024: INFO: Jan 10 13:20:36.028: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:36.028: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:36.028: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:36.028: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Jan 10 13:20:36.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:36.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:36.028: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:36.028: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:36.028: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:36.028: INFO: Jan 10 13:20:38.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:38.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:38.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:38.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Jan 10 13:20:38.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:38.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:38.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:38.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:38.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:38.019: INFO: Jan 10 13:20:40.026: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:40.026: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:40.026: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:40.026: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Jan 10 13:20:40.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:40.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:40.026: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:40.026: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:40.026: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:40.026: INFO: Jan 10 13:20:42.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:42.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:42.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:42.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Jan 10 13:20:42.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:42.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:42.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:42.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:42.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:42.019: INFO: Jan 10 13:20:44.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:44.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:44.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:44.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Jan 10 13:20:44.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:44.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:44.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:44.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:44.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:44.018: INFO: Jan 10 13:20:46.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:46.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:46.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:46.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Jan 10 13:20:46.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:46.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:46.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:46.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:46.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:46.021: INFO: Jan 10 13:20:48.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:48.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:48.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:48.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Jan 10 13:20:48.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:48.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:48.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:48.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:48.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:48.019: INFO: Jan 10 13:20:50.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:50.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:50.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:50.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Jan 10 13:20:50.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:50.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:50.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:50.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:50.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:50.019: INFO: Jan 10 13:20:52.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:52.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:52.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:52.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Jan 10 13:20:52.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:52.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:52.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:52.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:52.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:52.020: INFO: Jan 10 13:20:54.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:54.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:54.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:54.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Jan 10 13:20:54.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:54.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:54.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:54.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:54.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:54.022: INFO: Jan 10 13:20:56.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:56.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:56.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:56.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Jan 10 13:20:56.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:56.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:56.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:56.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:56.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:56.021: INFO: Jan 10 13:20:58.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:58.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:58.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:20:58.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Jan 10 13:20:58.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:20:58.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:20:58.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:58.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:58.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:20:58.023: INFO: Jan 10 13:21:00.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:00.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:00.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:00.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Jan 10 13:21:00.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:00.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:00.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:00.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:00.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:00.020: INFO: Jan 10 13:21:02.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:02.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:02.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:02.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Jan 10 13:21:02.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:02.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:02.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:02.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:02.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:02.020: INFO: Jan 10 13:21:04.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:04.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:04.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:04.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Jan 10 13:21:04.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:04.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:04.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:04.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:04.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:04.017: INFO: Jan 10 13:21:06.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:06.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:06.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:06.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Jan 10 13:21:06.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:06.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:06.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:06.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:06.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:06.020: INFO: Jan 10 13:21:08.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:08.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:08.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:08.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Jan 10 13:21:08.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:08.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:08.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:08.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:08.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:08.020: INFO: Jan 10 13:21:10.063: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:10.063: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:10.063: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:10.063: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Jan 10 13:21:10.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:10.063: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:10.063: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:10.063: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:10.063: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:10.063: INFO: Jan 10 13:21:12.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:12.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:12.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:12.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Jan 10 13:21:12.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:12.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:12.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:12.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:12.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:12.019: INFO: Jan 10 13:21:14.027: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:14.027: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:14.027: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:14.027: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Jan 10 13:21:14.027: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:14.027: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:14.027: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:14.027: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:14.027: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:14.027: INFO: Jan 10 13:21:16.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:16.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:16.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:16.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Jan 10 13:21:16.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:16.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:16.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:16.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:16.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:16.020: INFO: Jan 10 13:21:18.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:18.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:18.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:18.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Jan 10 13:21:18.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:18.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:18.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:18.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:18.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:18.019: INFO: Jan 10 13:21:20.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:20.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:20.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:20.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Jan 10 13:21:20.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:20.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:20.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:20.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:20.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:20.022: INFO: Jan 10 13:21:22.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:22.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:22.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:22.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Jan 10 13:21:22.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:22.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:22.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:22.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:22.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:22.024: INFO: Jan 10 13:21:24.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:24.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:24.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:24.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Jan 10 13:21:24.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:24.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:24.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:24.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:24.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:24.018: INFO: Jan 10 13:21:26.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:26.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:26.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:26.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Jan 10 13:21:26.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:26.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:26.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:26.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:26.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:26.022: INFO: Jan 10 13:21:28.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:28.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:28.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:28.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Jan 10 13:21:28.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:28.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:28.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:28.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:28.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:28.023: INFO: Jan 10 13:21:30.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:30.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:30.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:30.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Jan 10 13:21:30.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:30.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:30.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:30.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:30.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:30.021: INFO: Jan 10 13:21:32.036: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:32.036: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:32.036: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:32.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Jan 10 13:21:32.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:32.036: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:32.036: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:32.036: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:32.036: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:32.036: INFO: Jan 10 13:21:34.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:34.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:34.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:34.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Jan 10 13:21:34.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:34.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:34.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:34.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:34.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:34.022: INFO: Jan 10 13:21:36.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:36.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:36.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:36.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Jan 10 13:21:36.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:36.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:36.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:36.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:36.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:36.021: INFO: Jan 10 13:21:38.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:38.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:38.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:38.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Jan 10 13:21:38.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:38.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:38.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:38.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:38.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:38.021: INFO: Jan 10 13:21:40.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:40.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:40.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:40.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Jan 10 13:21:40.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:40.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:40.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:40.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:40.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:40.022: INFO: Jan 10 13:21:42.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:42.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:42.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:42.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Jan 10 13:21:42.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:42.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:42.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:42.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:42.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:42.024: INFO: Jan 10 13:21:44.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:44.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:44.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:44.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Jan 10 13:21:44.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:44.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:44.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:44.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:44.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:44.025: INFO: Jan 10 13:21:46.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:46.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:46.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:46.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Jan 10 13:21:46.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:46.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:46.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:46.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:46.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:46.021: INFO: Jan 10 13:21:48.028: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:48.028: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:48.028: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:48.028: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Jan 10 13:21:48.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:48.028: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:48.028: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:48.028: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:48.028: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:48.028: INFO: Jan 10 13:21:50.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:50.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:50.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:50.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Jan 10 13:21:50.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:50.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:50.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:50.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:50.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:50.023: INFO: Jan 10 13:21:52.025: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:52.025: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:52.025: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:52.025: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Jan 10 13:21:52.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:52.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:52.025: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:52.025: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:52.025: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:52.025: INFO: Jan 10 13:21:54.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:54.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:54.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:54.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Jan 10 13:21:54.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:54.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:54.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:54.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:54.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:54.019: INFO: Jan 10 13:21:56.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:56.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:56.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:56.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Jan 10 13:21:56.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:56.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:56.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:56.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:56.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:56.021: INFO: Jan 10 13:21:58.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:58.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:58.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:21:58.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Jan 10 13:21:58.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:21:58.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:21:58.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:58.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:58.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:21:58.024: INFO: Jan 10 13:22:00.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:00.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:00.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:00.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Jan 10 13:22:00.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:00.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:00.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:00.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:00.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:00.024: INFO: Jan 10 13:22:02.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:02.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:02.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:02.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Jan 10 13:22:02.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:02.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:02.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:02.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:02.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:02.024: INFO: Jan 10 13:22:04.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:04.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:04.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:04.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Jan 10 13:22:04.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:04.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:04.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:04.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:04.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:04.022: INFO: Jan 10 13:22:06.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:06.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:06.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:06.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Jan 10 13:22:06.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:06.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:06.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:06.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:06.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:06.020: INFO: Jan 10 13:22:08.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:08.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:08.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:08.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Jan 10 13:22:08.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:08.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:08.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:08.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:08.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:08.019: INFO: Jan 10 13:22:10.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:10.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:10.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:10.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Jan 10 13:22:10.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:10.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:10.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:10.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:10.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:10.019: INFO: Jan 10 13:22:12.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:12.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:12.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:12.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Jan 10 13:22:12.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:12.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:12.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:12.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:12.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:12.022: INFO: Jan 10 13:22:14.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:14.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:14.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:14.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Jan 10 13:22:14.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:14.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:14.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:14.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:14.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:14.019: INFO: Jan 10 13:22:16.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:16.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:16.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:16.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Jan 10 13:22:16.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:16.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:16.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:16.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:16.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:16.017: INFO: Jan 10 13:22:18.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:18.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:18.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:18.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Jan 10 13:22:18.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:18.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:18.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:18.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:18.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:18.021: INFO: Jan 10 13:22:20.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:20.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:20.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:20.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Jan 10 13:22:20.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:20.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:20.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:20.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:20.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:20.023: INFO: Jan 10 13:22:22.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:22.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:22.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:22.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Jan 10 13:22:22.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:22.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:22.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:22.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:22.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:22.024: INFO: Jan 10 13:22:24.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:24.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:24.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:24.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Jan 10 13:22:24.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:24.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:24.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:24.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:24.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:24.020: INFO: Jan 10 13:22:26.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:26.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:26.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:26.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Jan 10 13:22:26.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:26.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:26.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:26.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:26.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:26.020: INFO: Jan 10 13:22:28.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:28.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:28.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:28.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Jan 10 13:22:28.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:28.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:28.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:28.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:28.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:28.020: INFO: Jan 10 13:22:30.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:30.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:30.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:30.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Jan 10 13:22:30.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:30.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:30.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:30.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:30.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:30.019: INFO: Jan 10 13:22:32.025: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:32.025: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:32.025: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:32.025: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Jan 10 13:22:32.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:32.025: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:32.025: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:32.025: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:32.025: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:32.025: INFO: Jan 10 13:22:34.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:34.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:34.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:34.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Jan 10 13:22:34.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:34.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:34.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:34.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:34.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:34.018: INFO: Jan 10 13:22:36.029: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:36.030: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:36.030: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:36.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Jan 10 13:22:36.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:36.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:36.030: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:36.030: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:36.030: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:36.030: INFO: Jan 10 13:22:38.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:38.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:38.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:38.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Jan 10 13:22:38.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:38.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:38.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:38.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:38.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:38.024: INFO: Jan 10 13:22:40.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:40.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:40.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:40.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Jan 10 13:22:40.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:40.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:40.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:40.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:40.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:40.021: INFO: Jan 10 13:22:42.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:42.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:42.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:42.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Jan 10 13:22:42.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:42.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:42.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:42.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:42.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:42.022: INFO: Jan 10 13:22:44.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:44.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:44.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:44.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Jan 10 13:22:44.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:44.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:44.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:44.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:44.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:44.020: INFO: Jan 10 13:22:46.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:46.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:46.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:46.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Jan 10 13:22:46.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:46.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:46.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:46.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:46.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:46.020: INFO: Jan 10 13:22:48.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:48.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:48.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:48.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Jan 10 13:22:48.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:48.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:48.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:48.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:48.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:48.019: INFO: Jan 10 13:22:50.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:50.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:50.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:50.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Jan 10 13:22:50.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:50.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:50.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:50.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:50.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:50.019: INFO: Jan 10 13:22:52.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:52.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:52.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:52.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Jan 10 13:22:52.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:52.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:52.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:52.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:52.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:52.017: INFO: Jan 10 13:22:54.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:54.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:54.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:54.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Jan 10 13:22:54.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:54.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:54.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:54.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:54.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:54.020: INFO: Jan 10 13:22:56.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:56.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:56.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:56.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Jan 10 13:22:56.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:56.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:56.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:56.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:56.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:56.017: INFO: Jan 10 13:22:58.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:58.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:58.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:22:58.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Jan 10 13:22:58.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:22:58.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:22:58.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:58.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:58.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:22:58.021: INFO: Jan 10 13:23:00.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:00.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:00.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:00.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Jan 10 13:23:00.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:00.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:00.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:00.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:00.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:00.022: INFO: Jan 10 13:23:02.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:02.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:02.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:02.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Jan 10 13:23:02.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:02.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:02.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:02.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:02.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:02.020: INFO: Jan 10 13:23:04.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:04.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:04.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:04.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Jan 10 13:23:04.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:04.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:04.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:04.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:04.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:04.022: INFO: Jan 10 13:23:06.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:06.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:06.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:06.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Jan 10 13:23:06.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:06.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:06.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:06.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:06.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:06.020: INFO: Jan 10 13:23:08.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:08.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:08.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:08.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Jan 10 13:23:08.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:08.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:08.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:08.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:08.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:08.020: INFO: Jan 10 13:23:10.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:10.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:10.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:10.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Jan 10 13:23:10.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:10.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:10.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:10.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:10.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:10.021: INFO: Jan 10 13:23:12.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:12.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:12.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:12.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Jan 10 13:23:12.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:12.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:12.023: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:12.023: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:12.023: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:12.023: INFO: Jan 10 13:23:14.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:14.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:14.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:14.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Jan 10 13:23:14.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:14.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:14.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:14.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:14.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:14.022: INFO: Jan 10 13:23:16.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:16.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:16.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:16.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Jan 10 13:23:16.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:16.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:16.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:16.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:16.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:16.022: INFO: Jan 10 13:23:18.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:18.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:18.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:18.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Jan 10 13:23:18.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:18.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:18.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:18.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:18.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:18.019: INFO: Jan 10 13:23:20.023: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:20.023: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:20.023: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:20.023: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Jan 10 13:23:20.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:20.023: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:20.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:20.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:20.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:20.024: INFO: Jan 10 13:23:22.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:22.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:22.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:22.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Jan 10 13:23:22.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:22.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:22.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:22.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:22.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:22.019: INFO: Jan 10 13:23:24.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:24.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:24.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:24.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Jan 10 13:23:24.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:24.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:24.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:24.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:24.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:24.021: INFO: Jan 10 13:23:26.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:26.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:26.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:26.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Jan 10 13:23:26.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:26.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:26.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:26.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:26.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:26.024: INFO: Jan 10 13:23:28.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:28.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:28.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:28.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Jan 10 13:23:28.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:28.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:28.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:28.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:28.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:28.018: INFO: Jan 10 13:23:30.026: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:30.026: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:30.026: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:30.026: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Jan 10 13:23:30.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:30.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:30.026: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:30.026: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:30.026: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:30.026: INFO: Jan 10 13:23:32.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:32.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:32.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:32.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Jan 10 13:23:32.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:32.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:32.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:32.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:32.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:32.020: INFO: Jan 10 13:23:34.030: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:34.030: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:34.030: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:34.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Jan 10 13:23:34.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:34.030: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:34.030: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:34.030: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:34.030: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:34.030: INFO: Jan 10 13:23:36.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:36.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:36.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:36.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Jan 10 13:23:36.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:36.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:36.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:36.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:36.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:36.019: INFO: Jan 10 13:23:38.017: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:38.017: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:38.017: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:38.017: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Jan 10 13:23:38.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:38.017: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:38.017: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:38.017: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:38.017: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:38.017: INFO: Jan 10 13:23:40.026: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:40.026: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:40.026: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:40.026: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Jan 10 13:23:40.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:40.026: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:40.026: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:40.026: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:40.026: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:40.026: INFO: Jan 10 13:23:42.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:42.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:42.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:42.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Jan 10 13:23:42.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:42.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:42.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:42.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:42.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:42.020: INFO: Jan 10 13:23:44.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:44.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:44.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:44.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Jan 10 13:23:44.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:44.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:44.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:44.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:44.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:44.021: INFO: Jan 10 13:23:46.022: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:46.022: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:46.022: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:46.022: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Jan 10 13:23:46.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:46.022: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:46.022: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:46.022: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:46.022: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:46.022: INFO: Jan 10 13:23:48.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:48.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:48.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:48.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Jan 10 13:23:48.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:48.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:48.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:48.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:48.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:48.019: INFO: Jan 10 13:23:50.019: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:50.019: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:50.019: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:50.019: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Jan 10 13:23:50.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:50.019: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:50.019: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:50.019: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:50.019: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:50.019: INFO: Jan 10 13:23:52.021: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:52.021: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:52.021: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:52.021: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Jan 10 13:23:52.021: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:52.021: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:52.021: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:52.021: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:52.021: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:52.021: INFO: Jan 10 13:23:54.020: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:54.020: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:54.020: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:54.020: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Jan 10 13:23:54.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:54.020: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:54.020: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:54.020: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:54.020: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:54.020: INFO: Jan 10 13:23:56.018: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:56.018: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:56.018: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:56.018: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Jan 10 13:23:56.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:56.018: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:56.018: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:56.018: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:56.018: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:56.018: INFO: Jan 10 13:23:58.024: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:58.024: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:58.024: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:58.024: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 10 13:23:58.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:58.024: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:58.024: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.024: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.024: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.024: INFO: Jan 10 13:23:58.154: INFO: The status of Pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:58.154: INFO: The status of Pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:58.154: INFO: The status of Pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 13:23:58.154: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 10 13:23:58.154: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 13:23:58.154: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:58.154: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.154: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.154: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.154: INFO: STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/10/23 13:23:58.154 STEP: Found 96 events. - test/e2e/framework/debug/dump.go:46 @ 01/10/23 13:23:58.208 Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:33 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-r48k3z-control-plane-fjfj4_62bbbba0-ea3e-4548-84e0-c9204e3deb63 became leader Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:34 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-r48k3z-control-plane-fjfj4_f777442a-a275-421b-a1f1-f6b6c5d43569 became leader Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:38 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2 Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:38 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-xjgph Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:38 +0000 UTC - event for kube-proxy-xjgph: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-xjgph to capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:39 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-5szrq Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:39 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-w6fkr Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:39 +0000 UTC - event for coredns-56f4c55bf9-5szrq: {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 10 13:23:58.208: INFO: At 2023-01-10 13:11:39 +0000 UTC - event for coredns-56f4c55bf9-w6fkr: {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 10 13:23:58.208: INFO: At 2023-01-10 13:11:40 +0000 UTC - event for kube-proxy-xjgph: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d" Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:41 +0000 UTC - event for kube-proxy-xjgph: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Started: Started container kube-proxy Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:41 +0000 UTC - event for kube-proxy-xjgph: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Created: Created container kube-proxy Jan 10 13:23:58.208: INFO: At 2023-01-10 13:11:41 +0000 UTC - event for kube-proxy-xjgph: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d" in 1.302976307s (1.302984207s including waiting) Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:06 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:06 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-ms7kj Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:06 +0000 UTC - event for metrics-server-c9574f845-ms7kj: {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 10 13:23:58.208: INFO: At 2023-01-10 13:12:07 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1 Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:07 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-pchk6 Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:07 +0000 UTC - event for calico-kube-controllers-657b584867-pchk6: {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 10 13:23:58.208: INFO: At 2023-01-10 13:12:07 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-jh7v9 Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:07 +0000 UTC - event for calico-node-jh7v9: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-jh7v9 to capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:08 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:14 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Created: Created container upgrade-ipam Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:14 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Started: Started container upgrade-ipam Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:14 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 5.838406896s (5.838414096s including waiting) Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:17 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:17 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Created: Created container install-cni Jan 10 13:23:58.208: INFO: At 2023-01-10 13:12:17 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Started: Started container install-cni Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:19 +0000 UTC - event for calico-kube-controllers-657b584867-pchk6: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-pchk6 to capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:19 +0000 UTC - event for coredns-56f4c55bf9-5szrq: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-5szrq to capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:19 +0000 UTC - event for coredns-56f4c55bf9-w6fkr: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-w6fkr to capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:19 +0000 UTC - event for metrics-server-c9574f845-ms7kj: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-ms7kj to capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:20 +0000 UTC - event for calico-kube-controllers-657b584867-pchk6: {kubelet capz-conf-r48k3z-control-plane-fjfj4} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "078a9f7a73a78bf464f84b3546b69a4221db712d299e36e127b486f0dc16763f": 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 10 13:23:58.209: INFO: At 2023-01-10 13:12:20 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:20 +0000 UTC - event for coredns-56f4c55bf9-5szrq: {kubelet capz-conf-r48k3z-control-plane-fjfj4} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0d6c3056a7e4015879d50c0a6fbd15ec324e714b5006fb16c671915d25dd0353": 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 10 13:23:58.209: INFO: At 2023-01-10 13:12:20 +0000 UTC - event for coredns-56f4c55bf9-w6fkr: {kubelet capz-conf-r48k3z-control-plane-fjfj4} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "2cebcf54e98f57b5dd47393ea2453d29c095f71230a2ef97cd84c54084f027d8": 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 10 13:23:58.209: INFO: At 2023-01-10 13:12:20 +0000 UTC - event for metrics-server-c9574f845-ms7kj: {kubelet capz-conf-r48k3z-control-plane-fjfj4} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "2d67d8c0d06b207145a4a76f4999b5526e9051722aa1c8cb5422481356dab0a7": 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 10 13:23:58.209: INFO: At 2023-01-10 13:12:26 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Started: Started container calico-node Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:26 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Created: Created container calico-node Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:26 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 6.468732154s (6.468757154s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:27 +0000 UTC - event for calico-node-jh7v9: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:31 +0000 UTC - event for metrics-server-c9574f845-ms7kj: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:32 +0000 UTC - event for coredns-56f4c55bf9-w6fkr: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Created: Created container coredns Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:32 +0000 UTC - event for coredns-56f4c55bf9-w6fkr: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:33 +0000 UTC - event for calico-kube-controllers-657b584867-pchk6: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:33 +0000 UTC - event for coredns-56f4c55bf9-5szrq: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:33 +0000 UTC - event for coredns-56f4c55bf9-w6fkr: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Started: Started container coredns Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:34 +0000 UTC - event for coredns-56f4c55bf9-5szrq: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:34 +0000 UTC - event for coredns-56f4c55bf9-5szrq: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Started: Started container coredns Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:34 +0000 UTC - event for coredns-56f4c55bf9-5szrq: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Created: Created container coredns Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:36 +0000 UTC - event for metrics-server-c9574f845-ms7kj: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Started: Started container metrics-server Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:36 +0000 UTC - event for metrics-server-c9574f845-ms7kj: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Created: Created container metrics-server Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:36 +0000 UTC - event for metrics-server-c9574f845-ms7kj: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.648380088s (4.648462988s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:41 +0000 UTC - event for calico-kube-controllers-657b584867-pchk6: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Created: Created container calico-kube-controllers Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:41 +0000 UTC - event for calico-kube-controllers-657b584867-pchk6: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.506767181s (8.5025866s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:12:41 +0000 UTC - event for calico-kube-controllers-657b584867-pchk6: {kubelet capz-conf-r48k3z-control-plane-fjfj4} Started: Started container calico-kube-controllers Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:14 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-sd4jl Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:14 +0000 UTC - event for calico-node-sd4jl: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-sd4jl to capz-conf-r48k3z-md-0-z48wz Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:14 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-5jkkw Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:14 +0000 UTC - event for kube-proxy-5jkkw: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-5jkkw to capz-conf-r48k3z-md-0-z48wz Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:21 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-hrhsd Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:21 +0000 UTC - event for calico-node-hrhsd: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-hrhsd to capz-conf-r48k3z-md-0-77wj5 Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:21 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:21 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-49w5m Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:21 +0000 UTC - event for kube-proxy-49w5m: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-49w5m to capz-conf-r48k3z-md-0-77wj5 Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:21 +0000 UTC - event for kube-proxy-5jkkw: {kubelet capz-conf-r48k3z-md-0-z48wz} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:28 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Started: Started container upgrade-ipam Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:28 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.636276097s (6.63650538s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:28 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Created: Created container upgrade-ipam Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:31 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:31 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Created: Created container install-cni Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:31 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Started: Started container install-cni Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:32 +0000 UTC - event for kube-proxy-5jkkw: {kubelet capz-conf-r48k3z-md-0-z48wz} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d" in 3.939377885s (10.570466665s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:32 +0000 UTC - event for kube-proxy-5jkkw: {kubelet capz-conf-r48k3z-md-0-z48wz} Created: Created container kube-proxy Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:33 +0000 UTC - event for kube-proxy-5jkkw: {kubelet capz-conf-r48k3z-md-0-z48wz} Started: Started container kube-proxy Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:34 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:34 +0000 UTC - event for kube-proxy-49w5m: {kubelet capz-conf-r48k3z-md-0-77wj5} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:35 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:40 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 5.927720701s (5.927841501s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:40 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Created: Created container upgrade-ipam Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:40 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Started: Started container upgrade-ipam Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:41 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 6.375851167s (6.375856967s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:41 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Created: Created container calico-node Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:41 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Started: Started container calico-node Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:42 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:42 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Created: Created container install-cni Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:42 +0000 UTC - event for calico-node-sd4jl: {kubelet capz-conf-r48k3z-md-0-z48wz} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:43 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Started: Started container install-cni Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:44 +0000 UTC - event for kube-proxy-49w5m: {kubelet capz-conf-r48k3z-md-0-77wj5} Created: Created container kube-proxy Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:44 +0000 UTC - event for kube-proxy-49w5m: {kubelet capz-conf-r48k3z-md-0-77wj5} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d" in 3.904108817s (9.829825929s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:45 +0000 UTC - event for kube-proxy-49w5m: {kubelet capz-conf-r48k3z-md-0-77wj5} Started: Started container kube-proxy Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:46 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:52 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 5.778405891s (5.778410991s including waiting) Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:52 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Created: Created container calico-node Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:52 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Started: Started container calico-node Jan 10 13:23:58.209: INFO: At 2023-01-10 13:13:52 +0000 UTC - event for calico-node-hrhsd: {kubelet capz-conf-r48k3z-md-0-77wj5} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused Jan 10 13:23:58.270: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 13:23:58.270: INFO: calico-kube-controllers-657b584867-pchk6 capz-conf-r48k3z-control-plane-fjfj4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:42 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:42 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:19 +0000 UTC }] Jan 10 13:23:58.270: INFO: calico-node-hrhsd capz-conf-r48k3z-md-0-77wj5 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:59 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:59 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:21 +0000 UTC }] Jan 10 13:23:58.270: INFO: calico-node-jh7v9 capz-conf-r48k3z-control-plane-fjfj4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:20 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:38 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:07 +0000 UTC }] Jan 10 13:23:58.270: INFO: calico-node-sd4jl capz-conf-r48k3z-md-0-z48wz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:35 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:43 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:43 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:14 +0000 UTC }] Jan 10 13:23:58.270: INFO: coredns-56f4c55bf9-5szrq capz-conf-r48k3z-control-plane-fjfj4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:35 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:35 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:19 +0000 UTC }] Jan 10 13:23:58.270: INFO: coredns-56f4c55bf9-w6fkr capz-conf-r48k3z-control-plane-fjfj4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:34 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:34 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:19 +0000 UTC }] Jan 10 13:23:58.270: INFO: etcd-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:11:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:11:46 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:11:46 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:11:38 +0000 UTC }] Jan 10 13:23:58.270: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.270: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.270: INFO: kube-proxy-49w5m capz-conf-r48k3z-md-0-77wj5 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:28 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:21 +0000 UTC }] Jan 10 13:23:58.270: INFO: kube-proxy-5jkkw capz-conf-r48k3z-md-0-z48wz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:33 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:14 +0000 UTC }] Jan 10 13:23:58.270: INFO: kube-proxy-xjgph capz-conf-r48k3z-control-plane-fjfj4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:11:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:11:42 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:11:42 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:11:38 +0000 UTC }] Jan 10 13:23:58.270: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] Jan 10 13:23:58.270: INFO: metrics-server-c9574f845-ms7kj capz-conf-r48k3z-control-plane-fjfj4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:00 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:13:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 13:12:19 +0000 UTC }] Jan 10 13:23:58.270: INFO: Jan 10 13:23:58.525: INFO: Logging node info for node capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.558: INFO: Node Info: &Node{ObjectMeta:{capz-conf-r48k3z-control-plane-fjfj4 7527b9b2-7c51-48eb-8a49-e5d6633cf77f 1769 0 2023-01-10 13:11:35 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus2 failure-domain.beta.kubernetes.io/zone:eastus2-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-r48k3z-control-plane-fjfj4 kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:eastus2-1] map[cluster.x-k8s.io/cluster-name:capz-conf-r48k3z cluster.x-k8s.io/cluster-namespace:capz-conf-r48k3z cluster.x-k8s.io/machine:capz-conf-r48k3z-control-plane-mkmhm cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-r48k3z-control-plane kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.0.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.220.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-10 13:11:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2023-01-10 13:11:36 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/control-plane":{},"f:node.kubernetes.io/exclude-from-external-load-balancers":{}}}} } {manager Update v1 2023-01-10 13:12:04 +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-10 13:12:19 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2023-01-10 13:12:27 +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-10 13:23:20 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-r48k3z/providers/Microsoft.Compute/virtualMachines/capz-conf-r48k3z-control-plane-fjfj4,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: {{8344739840 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: {{8239882240 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-10 13:12:26 +0000 UTC,LastTransitionTime:2023-01-10 13:12:26 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-10 13:23:20 +0000 UTC,LastTransitionTime:2023-01-10 13:11:14 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-10 13:23:20 +0000 UTC,LastTransitionTime:2023-01-10 13:11:14 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-10 13:23:20 +0000 UTC,LastTransitionTime:2023-01-10 13:11:14 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-10 13:23:20 +0000 UTC,LastTransitionTime:2023-01-10 13:12:19 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-r48k3z-control-plane-fjfj4,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:7df43e9690224affbf45437508a7384e,SystemUUID:22456b54-30fa-d64d-be19-db814393a939,BootID:b3f445e7-03ed-4708-b13b-aee1a6ed9c08,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.876+182dfc973b410d,KubeProxyVersion:v1.27.0-alpha.0.876+182dfc973b410d,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:78bc199299f966b0694dc4044501aee2d7ebd6862b2b0a00bca3ee8d3813c82f docker.io/calico/kube-controllers:v3.23.0],SizeBytes:56343954,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:289a2c4d442651f5cfa5d434d0157c01b05eb3caa547c477e90501af2723e95e gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.861_3742d14998fc41],SizeBytes:35424169,},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:c30304305e6605d0095adaaa75083b3461e6d22e5883633e1491d308e697759d gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.861_3742d14998fc41],SizeBytes:32318946,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:84ac89ddbaf0eea284244fe4fe514ce96bb0a1037f3ef4f7a71f102291667c7f gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.861_3742d14998fc41],SizeBytes:21541611,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:a2ef93393caf906aef21095f9d1995f3f2e13e4f2959a412d2c33692460d97d3 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d],SizeBytes:21539924,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:420518a0111fe8917a6b387144a2e2c0c42977cfc58404e83565becc71d4877b gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.861_3742d14998fc41],SizeBytes:17522223,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[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 10 13:23:58.559: INFO: Logging kubelet events for node capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.733: INFO: Logging pods the kubelet thinks is on node capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:58.945: INFO: etcd-capz-conf-r48k3z-control-plane-fjfj4 started at 2023-01-10 13:11:38 +0000 UTC (0+1 container statuses recorded) Jan 10 13:23:58.945: INFO: Container etcd ready: true, restart count 0 Jan 10 13:23:58.945: INFO: kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4 started at <nil> (0+0 container statuses recorded) Jan 10 13:23:58.945: INFO: kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 started at <nil> (0+0 container statuses recorded) Jan 10 13:23:58.945: INFO: calico-node-jh7v9 started at 2023-01-10 13:12:07 +0000 UTC (2+1 container statuses recorded) Jan 10 13:23:58.945: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 10 13:23:58.945: INFO: Init container install-cni ready: true, restart count 0 Jan 10 13:23:58.945: INFO: Container calico-node ready: true, restart count 0 Jan 10 13:23:58.945: INFO: metrics-server-c9574f845-ms7kj started at 2023-01-10 13:12:19 +0000 UTC (0+1 container statuses recorded) Jan 10 13:23:58.945: INFO: Container metrics-server ready: true, restart count 0 Jan 10 13:23:58.945: INFO: calico-kube-controllers-657b584867-pchk6 started at 2023-01-10 13:12:19 +0000 UTC (0+1 container statuses recorded) Jan 10 13:23:58.945: INFO: Container calico-kube-controllers ready: true, restart count 0 Jan 10 13:23:58.945: INFO: kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 started at <nil> (0+0 container statuses recorded) Jan 10 13:23:58.945: INFO: kube-proxy-xjgph started at 2023-01-10 13:11:38 +0000 UTC (0+1 container statuses recorded) Jan 10 13:23:58.945: INFO: Container kube-proxy ready: true, restart count 0 Jan 10 13:23:58.945: INFO: coredns-56f4c55bf9-w6fkr started at 2023-01-10 13:12:19 +0000 UTC (0+1 container statuses recorded) Jan 10 13:23:58.945: INFO: Container coredns ready: true, restart count 0 Jan 10 13:23:58.945: INFO: coredns-56f4c55bf9-5szrq started at 2023-01-10 13:12:19 +0000 UTC (0+1 container statuses recorded) Jan 10 13:23:58.945: INFO: Container coredns ready: true, restart count 0 Jan 10 13:23:59.573: INFO: Latency metrics for node capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:23:59.573: INFO: Logging node info for node capz-conf-r48k3z-md-0-77wj5 Jan 10 13:23:59.732: INFO: Node Info: &Node{ObjectMeta:{capz-conf-r48k3z-md-0-77wj5 ddf683a1-cff2-4aab-a430-36f419d8d86e 1406 0 2023-01-10 13:13:21 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-r48k3z-md-0-77wj5 kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-r48k3z cluster.x-k8s.io/cluster-namespace:capz-conf-r48k3z cluster.x-k8s.io/machine:capz-conf-r48k3z-md-0-7cb55b4c4f-47qdt cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-r48k3z-md-0-7cb55b4c4f 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.247.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-10 13:13:21 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-10 13:13:21 +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":{}}} } {kube-controller-manager Update v1 2023-01-10 13:13:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2023-01-10 13:13:47 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2023-01-10 13:13:53 +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-10 13:19:17 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-r48k3z/providers/Microsoft.Compute/virtualMachines/capz-conf-r48k3z-md-0-77wj5,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: {{8344743936 0} {<nil>} 8149164Ki 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: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-10 13:13:52 +0000 UTC,LastTransitionTime:2023-01-10 13:13:52 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-10 13:19:17 +0000 UTC,LastTransitionTime:2023-01-10 13:13:21 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-10 13:19:17 +0000 UTC,LastTransitionTime:2023-01-10 13:13:21 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-10 13:19:17 +0000 UTC,LastTransitionTime:2023-01-10 13:13:21 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-10 13:19:17 +0000 UTC,LastTransitionTime:2023-01-10 13:13:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-r48k3z-md-0-77wj5,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:f63ea4610c6d42d7b3fcc6301aab4d75,SystemUUID:578b75a6-23e6-5742-aefb-c852d9a2ef32,BootID:13545cb6-b06e-4ddf-9918-a64a4616ecbc,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.876+182dfc973b410d,KubeProxyVersion:v1.27.0-alpha.0.876+182dfc973b410d,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},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:[capzci.azurecr.io/kube-proxy@sha256:a2ef93393caf906aef21095f9d1995f3f2e13e4f2959a412d2c33692460d97d3 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d],SizeBytes:21539924,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},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:[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 10 13:23:59.732: INFO: Logging kubelet events for node capz-conf-r48k3z-md-0-77wj5 Jan 10 13:23:59.932: INFO: Logging pods the kubelet thinks is on node capz-conf-r48k3z-md-0-77wj5 Jan 10 13:24:00.137: INFO: kube-proxy-49w5m started at 2023-01-10 13:13:28 +0000 UTC (0+1 container statuses recorded) Jan 10 13:24:00.137: INFO: Container kube-proxy ready: true, restart count 0 Jan 10 13:24:00.137: INFO: calico-node-hrhsd started at 2023-01-10 13:13:28 +0000 UTC (2+1 container statuses recorded) Jan 10 13:24:00.137: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 10 13:24:00.137: INFO: Init container install-cni ready: true, restart count 0 Jan 10 13:24:00.137: INFO: Container calico-node ready: true, restart count 0 Jan 10 13:24:00.754: INFO: Latency metrics for node capz-conf-r48k3z-md-0-77wj5 Jan 10 13:24:00.754: INFO: Logging node info for node capz-conf-r48k3z-md-0-z48wz Jan 10 13:24:00.933: INFO: Node Info: &Node{ObjectMeta:{capz-conf-r48k3z-md-0-z48wz 74dbc1d6-7225-460a-b1f1-67f847441fd1 1828 0 2023-01-10 13:13:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-r48k3z-md-0-z48wz kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-r48k3z cluster.x-k8s.io/cluster-namespace:capz-conf-r48k3z cluster.x-k8s.io/machine:capz-conf-r48k3z-md-0-7cb55b4c4f-8zd4z cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-r48k3z-md-0-7cb55b4c4f 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.224.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-10 13:13:14 +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-10 13:13:15 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {manager Update v1 2023-01-10 13:13:20 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2023-01-10 13:13:34 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-10 13:13:42 +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-10 13:23:58 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-r48k3z/providers/Microsoft.Compute/virtualMachines/capz-conf-r48k3z-md-0-z48wz,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: {{8344743936 0} {<nil>} 8149164Ki 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: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-10 13:13:42 +0000 UTC,LastTransitionTime:2023-01-10 13:13:42 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-10 13:23:58 +0000 UTC,LastTransitionTime:2023-01-10 13:13:14 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-10 13:23:58 +0000 UTC,LastTransitionTime:2023-01-10 13:13:14 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-10 13:23:58 +0000 UTC,LastTransitionTime:2023-01-10 13:13:14 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-10 13:23:58 +0000 UTC,LastTransitionTime:2023-01-10 13:13:34 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-r48k3z-md-0-z48wz,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:e39749fcc63143c798fc485facf96f49,SystemUUID:a4d07ddb-a148-854d-bf7e-9fd8a485670f,BootID:67696f21-2455-47fd-95df-a5980ab03dca,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.876+182dfc973b410d,KubeProxyVersion:v1.27.0-alpha.0.876+182dfc973b410d,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},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:[capzci.azurecr.io/kube-proxy@sha256:a2ef93393caf906aef21095f9d1995f3f2e13e4f2959a412d2c33692460d97d3 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.876_182dfc973b410d],SizeBytes:21539924,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},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:[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 10 13:24:00.933: INFO: Logging kubelet events for node capz-conf-r48k3z-md-0-z48wz Jan 10 13:24:01.132: INFO: Logging pods the kubelet thinks is on node capz-conf-r48k3z-md-0-z48wz Jan 10 13:24:01.337: INFO: calico-node-sd4jl started at 2023-01-10 13:13:15 +0000 UTC (2+1 container statuses recorded) Jan 10 13:24:01.337: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 10 13:24:01.337: INFO: Init container install-cni ready: true, restart count 0 Jan 10 13:24:01.337: INFO: Container calico-node ready: true, restart count 0 Jan 10 13:24:01.337: INFO: kube-proxy-5jkkw started at 2023-01-10 13:13:15 +0000 UTC (0+1 container statuses recorded) Jan 10 13:24:01.337: INFO: Container kube-proxy ready: true, restart count 0 Jan 10 13:24:01.956: INFO: Latency metrics for node capz-conf-r48k3z-md-0-z48wz Jan 10 13:24:02.178: INFO: Running kubectl logs on non-ready containers in kube-system Jan 10 13:24:02.533: INFO: Failed to get logs of pod kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4) Jan 10 13:24:02.533: INFO: Logs of kube-system/kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4:kube-apiserver on node capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:24:02.533: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-r48k3z-control-plane-fjfj4:kube-apiserver Jan 10 13:24:02.931: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4) Jan 10 13:24:02.931: INFO: Logs of kube-system/kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4:kube-controller-manager on node capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:24:02.931: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4:kube-controller-manager Jan 10 13:24:03.336: INFO: Failed to get logs of pod kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4) Jan 10 13:24:03.336: INFO: Logs of kube-system/kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4:kube-scheduler on node capz-conf-r48k3z-control-plane-fjfj4 Jan 10 13:24:03.336: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4: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-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] kube-controller-manager-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] kube-scheduler-capz-conf-r48k3z-control-plane-fjfj4 capz-conf-r48k3z-control-plane-fjfj4 Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:249 @ 01/10/23 13:24:03.336 < Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/10/23 13:24:03.336 (10m5.837s)
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
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 Conformance Tests conformance-tests
capz-e2e 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 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 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 Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e 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 Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e 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 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 Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e 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 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 Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e 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 [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade 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 [K8s-Upgrade] Running the workload cluster upgrade 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