PR #110981 pull-kubernetes-e2e-capz-conformance #1612857121630588928
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 | 58m6s |
| Revision | b7206f6e15e2f76356d6ca599374874e6ccdf839 |
| 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 17:54:06.887from 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 17:54:06.887
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 17:54:06.887from 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 17:54:06.887
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 17:54:06.891from 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 17:54:06.891
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 17:54:06.902from 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 17:54:06.902
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 17:54:06.923from 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 17:54:06.923
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 17:54:06.891from 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 17:54:06.891
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 17:54:06.887from 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 17:54:06.887
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 17:54:06.887from 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 17:54:06.887
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 17:54:06.887from 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 17:54:06.887
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 17:54:06.891from 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 17:54:06.891
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 17:54:06.899from 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 17:54:06.899
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 17:54:06.89from 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 17:54:06.89
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 17:54:06.888from 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 17:54:06.888
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 17:54:06.887from 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 17:54:06.887
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 17:54:06.902from 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 17:54:06.902
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 17:54:06.906from 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 17:54:06.906
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 17:54:06.9from 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 17:54:06.9
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 17:54:06.9from 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 17:54:06.9
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 17:54:06.925from 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 17:54:06.925
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 17:54:06.923from 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 17:54:06.923
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-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:249 @ 01/10/23 17:54:06.845from junit.kubetest.01.xml
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/10/23 17:44:00.255 Jan 10 17:44:00.255: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 10 17:44:00.257: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 10 17:44:00.762: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 10 17:44:01.309: INFO: The status of Pod calico-node-z7qnd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:01.309: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:01.309: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:01.309: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:01.309: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 10 17:44:01.309: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:01.309: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:01.309: INFO: calico-node-z7qnd capz-conf-0y4fvh-md-0-8r4jw Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:53 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:44:01.309: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:01.309: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:01.309: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:01.309: INFO: Jan 10 17:44:03.697: INFO: The status of Pod calico-node-z7qnd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:03.697: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:03.697: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:03.697: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:03.697: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Jan 10 17:44:03.697: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:03.697: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:03.697: INFO: calico-node-z7qnd capz-conf-0y4fvh-md-0-8r4jw Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:53 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:44:03.697: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:03.697: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:03.697: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:03.697: INFO: Jan 10 17:44:05.685: INFO: The status of Pod calico-node-z7qnd is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:05.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:05.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:05.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:05.685: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Jan 10 17:44:05.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:05.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:05.685: INFO: calico-node-z7qnd capz-conf-0y4fvh-md-0-8r4jw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:53 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:44:05.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:05.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:05.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:05.685: INFO: Jan 10 17:44:07.684: INFO: The status of Pod calico-node-z7qnd is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:07.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:07.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:07.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:07.684: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Jan 10 17:44:07.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:07.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:07.684: INFO: calico-node-z7qnd capz-conf-0y4fvh-md-0-8r4jw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:53 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:44:07.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:07.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:07.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:07.684: INFO: Jan 10 17:44:09.684: INFO: The status of Pod calico-node-z7qnd is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:09.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:09.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:09.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:09.684: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Jan 10 17:44:09.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:09.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:09.684: INFO: calico-node-z7qnd capz-conf-0y4fvh-md-0-8r4jw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:53 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:44:09.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:09.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:09.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:09.684: INFO: Jan 10 17:44:11.680: INFO: The status of Pod calico-node-z7qnd is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:11.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:11.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:11.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:11.680: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Jan 10 17:44:11.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:11.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:11.680: INFO: calico-node-z7qnd capz-conf-0y4fvh-md-0-8r4jw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:53 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:44:11.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:11.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:11.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:11.680: INFO: Jan 10 17:44:13.681: INFO: The status of Pod calico-node-z7qnd is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:13.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:13.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:13.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:13.681: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Jan 10 17:44:13.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:13.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:13.681: INFO: calico-node-z7qnd capz-conf-0y4fvh-md-0-8r4jw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:53 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:44:13.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:13.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:13.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:13.681: INFO: Jan 10 17:44:15.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:15.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:15.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:15.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Jan 10 17:44:15.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:15.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:15.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:15.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:15.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:15.680: INFO: Jan 10 17:44:17.689: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:17.689: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:17.689: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:17.689: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Jan 10 17:44:17.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:17.689: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:17.689: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:17.689: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:17.689: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:17.689: INFO: Jan 10 17:44:19.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:19.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:19.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:19.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Jan 10 17:44:19.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:19.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:19.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:19.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:19.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:19.682: INFO: Jan 10 17:44:21.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:21.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:21.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:21.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Jan 10 17:44:21.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:21.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:21.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:21.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:21.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:21.679: INFO: Jan 10 17:44:23.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:23.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:23.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:23.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Jan 10 17:44:23.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:23.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:23.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:23.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:23.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:23.680: INFO: Jan 10 17:44:25.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:25.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:25.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:25.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Jan 10 17:44:25.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:25.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:25.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:25.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:25.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:25.681: INFO: Jan 10 17:44:27.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:27.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:27.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:27.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Jan 10 17:44:27.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:27.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:27.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:27.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:27.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:27.683: INFO: Jan 10 17:44:29.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:29.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:29.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:29.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Jan 10 17:44:29.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:29.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:29.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:29.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:29.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:29.679: INFO: Jan 10 17:44:31.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:31.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:31.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:31.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Jan 10 17:44:31.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:31.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:31.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:31.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:31.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:31.691: INFO: Jan 10 17:44:33.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:33.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:33.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:33.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Jan 10 17:44:33.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:33.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:33.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:33.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:33.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:33.681: INFO: Jan 10 17:44:35.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:35.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:35.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:35.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Jan 10 17:44:35.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:35.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:35.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:35.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:35.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:35.685: INFO: Jan 10 17:44:37.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:37.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:37.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:37.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Jan 10 17:44:37.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:37.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:37.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:37.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:37.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:37.680: INFO: Jan 10 17:44:39.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:39.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:39.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:39.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Jan 10 17:44:39.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:39.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:39.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:39.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:39.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:39.681: INFO: Jan 10 17:44:41.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:41.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:41.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:41.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Jan 10 17:44:41.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:41.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:41.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:41.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:41.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:41.680: INFO: Jan 10 17:44:43.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:43.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:43.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:43.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Jan 10 17:44:43.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:43.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:43.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:43.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:43.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:43.682: INFO: Jan 10 17:44:45.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:45.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:45.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:45.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Jan 10 17:44:45.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:45.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:45.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:45.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:45.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:45.687: INFO: Jan 10 17:44:47.689: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:47.689: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:47.689: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:47.689: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Jan 10 17:44:47.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:47.689: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:47.689: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:47.689: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:47.689: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:47.689: INFO: Jan 10 17:44:49.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:49.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:49.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:49.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Jan 10 17:44:49.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:49.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:49.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:49.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:49.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:49.685: INFO: Jan 10 17:44:51.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:51.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:51.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:51.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Jan 10 17:44:51.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:51.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:51.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:51.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:51.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:51.687: INFO: Jan 10 17:44:53.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:53.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:53.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:53.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Jan 10 17:44:53.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:53.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:53.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:53.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:53.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:53.687: INFO: Jan 10 17:44:55.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:55.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:55.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:55.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Jan 10 17:44:55.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:55.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:55.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:55.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:55.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:55.691: INFO: Jan 10 17:44:57.696: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:57.696: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:57.696: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:57.696: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Jan 10 17:44:57.696: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:57.696: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:57.696: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:57.696: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:57.696: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:57.696: INFO: Jan 10 17:44:59.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:59.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:59.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:44:59.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Jan 10 17:44:59.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:44:59.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:44:59.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:59.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:59.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:44:59.684: INFO: Jan 10 17:45:01.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:01.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:01.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:01.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Jan 10 17:45:01.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:01.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:01.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:01.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:01.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:01.687: INFO: Jan 10 17:45:03.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:03.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:03.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:03.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Jan 10 17:45:03.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:03.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:03.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:03.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:03.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:03.687: INFO: Jan 10 17:45:05.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:05.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:05.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:05.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Jan 10 17:45:05.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:05.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:05.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:05.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:05.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:05.686: INFO: Jan 10 17:45:07.701: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:07.701: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:07.701: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:07.701: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Jan 10 17:45:07.701: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:07.701: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:07.701: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:07.701: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:07.701: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:07.701: INFO: Jan 10 17:45:09.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:09.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:09.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:09.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Jan 10 17:45:09.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:09.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:09.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:09.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:09.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:09.685: INFO: Jan 10 17:45:11.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:11.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:11.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:11.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Jan 10 17:45:11.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:11.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:11.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:11.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:11.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:11.685: INFO: Jan 10 17:45:13.694: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:13.694: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:13.694: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:13.694: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Jan 10 17:45:13.694: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:13.694: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:13.694: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:13.694: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:13.694: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:13.694: INFO: Jan 10 17:45:15.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:15.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:15.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:15.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Jan 10 17:45:15.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:15.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:15.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:15.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:15.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:15.688: INFO: Jan 10 17:45:17.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:17.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:17.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:17.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Jan 10 17:45:17.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:17.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:17.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:17.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:17.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:17.688: INFO: Jan 10 17:45:19.695: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:19.695: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:19.695: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:19.695: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Jan 10 17:45:19.695: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:19.695: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:19.695: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:19.695: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:19.695: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:19.695: INFO: Jan 10 17:45:21.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:21.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:21.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:21.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Jan 10 17:45:21.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:21.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:21.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:21.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:21.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:21.691: INFO: Jan 10 17:45:23.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:23.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:23.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:23.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Jan 10 17:45:23.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:23.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:23.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:23.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:23.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:23.684: INFO: Jan 10 17:45:25.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:25.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:25.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:25.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Jan 10 17:45:25.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:25.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:25.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:25.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:25.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:25.683: INFO: Jan 10 17:45:27.701: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:27.701: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:27.701: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:27.701: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Jan 10 17:45:27.701: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:27.701: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:27.701: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:27.701: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:27.701: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:27.701: INFO: Jan 10 17:45:29.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:29.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:29.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:29.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Jan 10 17:45:29.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:29.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:29.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:29.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:29.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:29.682: INFO: Jan 10 17:45:31.692: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:31.692: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:31.692: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:31.692: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Jan 10 17:45:31.692: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:31.692: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:31.692: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:31.692: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:31.692: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:31.692: INFO: Jan 10 17:45:33.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:33.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:33.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:33.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Jan 10 17:45:33.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:33.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:33.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:33.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:33.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:33.684: INFO: Jan 10 17:45:35.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:35.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:35.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:35.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Jan 10 17:45:35.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:35.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:35.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:35.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:35.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:35.684: INFO: Jan 10 17:45:37.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:37.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:37.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:37.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Jan 10 17:45:37.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:37.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:37.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:37.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:37.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:37.686: INFO: Jan 10 17:45:39.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:39.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:39.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:39.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Jan 10 17:45:39.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:39.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:39.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:39.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:39.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:39.683: INFO: Jan 10 17:45:41.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:41.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:41.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:41.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Jan 10 17:45:41.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:41.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:41.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:41.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:41.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:41.684: INFO: Jan 10 17:45:43.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:43.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:43.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:43.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Jan 10 17:45:43.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:43.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:43.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:43.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:43.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:43.684: INFO: Jan 10 17:45:45.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:45.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:45.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:45.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Jan 10 17:45:45.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:45.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:45.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:45.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:45.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:45.691: INFO: Jan 10 17:45:47.690: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:47.690: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:47.690: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:47.690: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Jan 10 17:45:47.690: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:47.690: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:47.690: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:47.690: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:47.690: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:47.690: INFO: Jan 10 17:45:49.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:49.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:49.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:49.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Jan 10 17:45:49.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:49.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:49.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:49.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:49.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:49.684: INFO: Jan 10 17:45:51.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:51.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:51.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:51.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Jan 10 17:45:51.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:51.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:51.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:51.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:51.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:51.688: INFO: Jan 10 17:45:53.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:53.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:53.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:53.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Jan 10 17:45:53.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:53.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:53.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:53.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:53.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:53.682: INFO: Jan 10 17:45:55.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:55.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:55.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:55.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Jan 10 17:45:55.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:55.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:55.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:55.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:55.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:55.684: INFO: Jan 10 17:45:57.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:57.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:57.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:57.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Jan 10 17:45:57.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:57.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:57.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:57.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:57.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:57.686: INFO: Jan 10 17:45:59.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:59.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:59.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:45:59.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Jan 10 17:45:59.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:45:59.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:45:59.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:59.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:59.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:45:59.683: INFO: Jan 10 17:46:01.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:01.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:01.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:01.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Jan 10 17:46:01.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:01.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:01.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:01.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:01.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:01.688: INFO: Jan 10 17:46:03.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:03.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:03.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:03.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Jan 10 17:46:03.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:03.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:03.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:03.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:03.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:03.685: INFO: Jan 10 17:46:05.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:05.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:05.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:05.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Jan 10 17:46:05.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:05.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:05.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:05.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:05.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:05.681: INFO: Jan 10 17:46:07.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:07.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:07.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:07.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Jan 10 17:46:07.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:07.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:07.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:07.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:07.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:07.691: INFO: Jan 10 17:46:09.689: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:09.689: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:09.689: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:09.689: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Jan 10 17:46:09.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:09.689: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:09.689: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:09.689: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:09.689: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:09.689: INFO: Jan 10 17:46:11.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:11.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:11.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:11.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Jan 10 17:46:11.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:11.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:11.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:11.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:11.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:11.685: INFO: Jan 10 17:46:13.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:13.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:13.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:13.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Jan 10 17:46:13.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:13.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:13.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:13.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:13.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:13.686: INFO: Jan 10 17:46:15.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:15.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:15.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:15.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Jan 10 17:46:15.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:15.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:15.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:15.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:15.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:15.683: INFO: Jan 10 17:46:17.716: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:17.716: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:17.716: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:17.717: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Jan 10 17:46:17.717: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:17.717: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:17.717: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:17.717: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:17.717: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:17.717: INFO: Jan 10 17:46:19.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:19.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:19.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:19.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Jan 10 17:46:19.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:19.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:19.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:19.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:19.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:19.687: INFO: Jan 10 17:46:21.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:21.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:21.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:21.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Jan 10 17:46:21.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:21.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:21.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:21.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:21.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:21.682: INFO: Jan 10 17:46:23.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:23.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:23.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:23.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Jan 10 17:46:23.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:23.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:23.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:23.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:23.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:23.685: INFO: Jan 10 17:46:25.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:25.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:25.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:25.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Jan 10 17:46:25.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:25.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:25.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:25.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:25.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:25.686: INFO: Jan 10 17:46:27.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:27.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:27.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:27.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Jan 10 17:46:27.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:27.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:27.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:27.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:27.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:27.688: INFO: Jan 10 17:46:29.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:29.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:29.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:29.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Jan 10 17:46:29.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:29.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:29.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:29.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:29.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:29.683: INFO: Jan 10 17:46:31.690: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:31.690: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:31.690: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:31.690: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Jan 10 17:46:31.690: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:31.690: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:31.690: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:31.690: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:31.690: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:31.690: INFO: Jan 10 17:46:33.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:33.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:33.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:33.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Jan 10 17:46:33.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:33.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:33.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:33.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:33.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:33.684: INFO: Jan 10 17:46:35.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:35.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:35.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:35.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Jan 10 17:46:35.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:35.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:35.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:35.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:35.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:35.685: INFO: Jan 10 17:46:37.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:37.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:37.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:37.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Jan 10 17:46:37.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:37.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:37.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:37.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:37.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:37.691: INFO: Jan 10 17:46:39.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:39.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:39.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:39.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Jan 10 17:46:39.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:39.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:39.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:39.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:39.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:39.686: INFO: Jan 10 17:46:41.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:41.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:41.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:41.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Jan 10 17:46:41.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:41.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:41.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:41.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:41.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:41.685: INFO: Jan 10 17:46:43.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:43.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:43.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:43.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Jan 10 17:46:43.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:43.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:43.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:43.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:43.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:43.686: INFO: Jan 10 17:46:45.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:45.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:45.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:45.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Jan 10 17:46:45.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:45.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:45.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:45.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:45.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:45.684: INFO: Jan 10 17:46:47.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:47.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:47.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:47.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Jan 10 17:46:47.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:47.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:47.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:47.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:47.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:47.685: INFO: Jan 10 17:46:49.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:49.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:49.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:49.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Jan 10 17:46:49.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:49.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:49.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:49.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:49.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:49.685: INFO: Jan 10 17:46:51.690: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:51.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:51.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:51.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Jan 10 17:46:51.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:51.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:51.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:51.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:51.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:51.691: INFO: Jan 10 17:46:53.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:53.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:53.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:53.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Jan 10 17:46:53.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:53.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:53.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:53.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:53.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:53.686: INFO: Jan 10 17:46:55.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:55.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:55.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:55.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Jan 10 17:46:55.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:55.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:55.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:55.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:55.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:55.685: INFO: Jan 10 17:46:57.694: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:57.694: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:57.694: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:57.694: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Jan 10 17:46:57.694: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:57.694: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:57.695: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:57.695: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:57.695: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:57.695: INFO: Jan 10 17:46:59.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:59.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:59.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:46:59.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Jan 10 17:46:59.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:46:59.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:46:59.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:59.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:59.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:46:59.687: INFO: Jan 10 17:47:01.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:01.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:01.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:01.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Jan 10 17:47:01.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:01.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:01.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:01.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:01.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:01.687: INFO: Jan 10 17:47:03.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:03.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:03.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:03.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Jan 10 17:47:03.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:03.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:03.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:03.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:03.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:03.684: INFO: Jan 10 17:47:05.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:05.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:05.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:05.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Jan 10 17:47:05.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:05.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:05.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:05.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:05.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:05.683: INFO: Jan 10 17:47:07.693: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:07.694: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:07.694: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:07.694: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Jan 10 17:47:07.694: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:07.694: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:07.694: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:07.694: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:07.694: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:07.694: INFO: Jan 10 17:47:09.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:09.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:09.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:09.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Jan 10 17:47:09.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:09.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:09.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:09.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:09.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:09.685: INFO: Jan 10 17:47:11.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:11.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:11.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:11.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Jan 10 17:47:11.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:11.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:11.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:11.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:11.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:11.683: INFO: Jan 10 17:47:13.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:13.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:13.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:13.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Jan 10 17:47:13.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:13.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:13.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:13.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:13.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:13.684: INFO: Jan 10 17:47:15.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:15.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:15.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:15.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Jan 10 17:47:15.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:15.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:15.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:15.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:15.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:15.688: INFO: Jan 10 17:47:17.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:17.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:17.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:17.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Jan 10 17:47:17.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:17.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:17.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:17.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:17.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:17.687: INFO: Jan 10 17:47:19.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:19.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:19.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:19.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Jan 10 17:47:19.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:19.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:19.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:19.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:19.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:19.684: INFO: Jan 10 17:47:21.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:21.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:21.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:21.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Jan 10 17:47:21.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:21.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:21.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:21.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:21.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:21.684: INFO: Jan 10 17:47:23.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:23.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:23.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:23.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Jan 10 17:47:23.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:23.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:23.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:23.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:23.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:23.686: INFO: Jan 10 17:47:25.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:25.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:25.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:25.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Jan 10 17:47:25.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:25.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:25.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:25.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:25.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:25.691: INFO: Jan 10 17:47:27.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:27.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:27.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:27.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Jan 10 17:47:27.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:27.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:27.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:27.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:27.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:27.691: INFO: Jan 10 17:47:29.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:29.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:29.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:29.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Jan 10 17:47:29.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:29.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:29.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:29.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:29.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:29.685: INFO: Jan 10 17:47:31.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:31.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:31.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:31.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Jan 10 17:47:31.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:31.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:31.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:31.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:31.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:31.685: INFO: Jan 10 17:47:33.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:33.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:33.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:33.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Jan 10 17:47:33.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:33.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:33.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:33.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:33.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:33.684: INFO: Jan 10 17:47:35.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:35.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:35.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:35.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Jan 10 17:47:35.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:35.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:35.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:35.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:35.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:35.687: INFO: Jan 10 17:47:37.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:37.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:37.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:37.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Jan 10 17:47:37.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:37.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:37.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:37.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:37.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:37.684: INFO: Jan 10 17:47:39.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:39.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:39.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:39.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Jan 10 17:47:39.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:39.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:39.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:39.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:39.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:39.686: INFO: Jan 10 17:47:41.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:41.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:41.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:41.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Jan 10 17:47:41.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:41.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:41.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:41.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:41.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:41.683: INFO: Jan 10 17:47:43.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:43.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:43.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:43.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Jan 10 17:47:43.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:43.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:43.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:43.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:43.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:43.687: INFO: Jan 10 17:47:45.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:45.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:45.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:45.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Jan 10 17:47:45.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:45.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:45.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:45.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:45.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:45.688: INFO: Jan 10 17:47:47.700: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:47.700: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:47.700: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:47.700: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Jan 10 17:47:47.700: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:47.700: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:47.700: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:47.700: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:47.700: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:47.700: INFO: Jan 10 17:47:49.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:49.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:49.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:49.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Jan 10 17:47:49.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:49.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:49.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:49.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:49.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:49.682: INFO: Jan 10 17:47:51.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:51.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:51.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:51.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Jan 10 17:47:51.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:51.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:51.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:51.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:51.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:51.684: INFO: Jan 10 17:47:53.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:53.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:53.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:53.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Jan 10 17:47:53.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:53.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:53.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:53.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:53.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:53.684: INFO: Jan 10 17:47:55.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:55.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:55.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:55.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Jan 10 17:47:55.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:55.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:55.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:55.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:55.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:55.688: INFO: Jan 10 17:47:57.690: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:57.690: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:57.690: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:57.690: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Jan 10 17:47:57.690: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:57.690: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:57.690: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:57.690: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:57.690: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:57.690: INFO: Jan 10 17:47:59.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:59.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:59.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:47:59.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Jan 10 17:47:59.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:47:59.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:47:59.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:59.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:59.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:47:59.683: INFO: Jan 10 17:48:01.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:01.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:01.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:01.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Jan 10 17:48:01.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:01.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:01.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:01.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:01.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:01.686: INFO: Jan 10 17:48:03.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:03.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:03.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:03.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Jan 10 17:48:03.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:03.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:03.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:03.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:03.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:03.688: INFO: Jan 10 17:48:05.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:05.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:05.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:05.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Jan 10 17:48:05.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:05.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:05.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:05.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:05.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:05.684: INFO: Jan 10 17:48:07.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:07.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:07.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:07.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Jan 10 17:48:07.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:07.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:07.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:07.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:07.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:07.688: INFO: Jan 10 17:48:09.689: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:09.689: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:09.689: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:09.689: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Jan 10 17:48:09.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:09.689: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:09.690: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:09.690: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:09.690: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:09.690: INFO: Jan 10 17:48:11.693: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:11.693: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:11.693: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:11.693: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Jan 10 17:48:11.693: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:11.693: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:11.693: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:11.693: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:11.693: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:11.693: INFO: Jan 10 17:48:13.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:13.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:13.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:13.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Jan 10 17:48:13.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:13.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:13.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:13.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:13.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:13.685: INFO: Jan 10 17:48:15.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:15.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:15.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:15.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Jan 10 17:48:15.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:15.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:15.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:15.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:15.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:15.683: INFO: Jan 10 17:48:17.689: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:17.689: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:17.689: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:17.689: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Jan 10 17:48:17.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:17.689: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:17.689: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:17.689: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:17.689: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:17.689: INFO: Jan 10 17:48:19.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:19.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:19.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:19.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Jan 10 17:48:19.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:19.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:19.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:19.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:19.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:19.683: INFO: Jan 10 17:48:21.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:21.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:21.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:21.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Jan 10 17:48:21.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:21.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:21.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:21.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:21.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:21.683: INFO: Jan 10 17:48:23.692: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:23.692: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:23.692: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:23.692: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Jan 10 17:48:23.692: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:23.692: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:23.692: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:23.692: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:23.692: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:23.692: INFO: Jan 10 17:48:25.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:25.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:25.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:25.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Jan 10 17:48:25.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:25.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:25.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:25.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:25.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:25.687: INFO: Jan 10 17:48:27.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:27.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:27.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:27.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Jan 10 17:48:27.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:27.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:27.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:27.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:27.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:27.688: INFO: Jan 10 17:48:29.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:29.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:29.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:29.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Jan 10 17:48:29.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:29.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:29.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:29.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:29.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:29.684: INFO: Jan 10 17:48:31.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:31.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:31.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:31.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Jan 10 17:48:31.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:31.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:31.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:31.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:31.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:31.680: INFO: Jan 10 17:48:33.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:33.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:33.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:33.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Jan 10 17:48:33.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:33.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:33.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:33.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:33.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:33.681: INFO: Jan 10 17:48:35.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:35.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:35.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:35.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Jan 10 17:48:35.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:35.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:35.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:35.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:35.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:35.679: INFO: Jan 10 17:48:37.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:37.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:37.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:37.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Jan 10 17:48:37.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:37.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:37.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:37.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:37.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:37.685: INFO: Jan 10 17:48:39.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:39.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:39.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:39.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Jan 10 17:48:39.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:39.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:39.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:39.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:39.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:39.680: INFO: Jan 10 17:48:41.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:41.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:41.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:41.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Jan 10 17:48:41.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:41.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:41.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:41.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:41.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:41.679: INFO: Jan 10 17:48:43.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:43.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:43.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:43.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Jan 10 17:48:43.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:43.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:43.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:43.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:43.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:43.685: INFO: Jan 10 17:48:45.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:45.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:45.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:45.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Jan 10 17:48:45.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:45.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:45.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:45.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:45.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:45.680: INFO: Jan 10 17:48:47.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:47.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:47.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:47.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Jan 10 17:48:47.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:47.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:47.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:47.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:47.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:47.682: INFO: Jan 10 17:48:49.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:49.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:49.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:49.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Jan 10 17:48:49.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:49.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:49.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:49.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:49.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:49.680: INFO: Jan 10 17:48:51.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:51.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:51.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:51.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Jan 10 17:48:51.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:51.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:51.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:51.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:51.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:51.679: INFO: Jan 10 17:48:53.685: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:53.685: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:53.685: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:53.685: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Jan 10 17:48:53.685: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:53.685: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:53.685: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:53.685: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:53.685: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:53.685: INFO: Jan 10 17:48:55.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:55.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:55.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:55.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Jan 10 17:48:55.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:55.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:55.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:55.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:55.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:55.681: INFO: Jan 10 17:48:57.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:57.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:57.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:57.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Jan 10 17:48:57.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:57.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:57.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:57.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:57.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:57.682: INFO: Jan 10 17:48:59.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:59.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:59.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:48:59.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Jan 10 17:48:59.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:48:59.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:48:59.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:59.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:59.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:48:59.682: INFO: Jan 10 17:49:01.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:01.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:01.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:01.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Jan 10 17:49:01.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:01.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:01.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:01.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:01.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:01.680: INFO: Jan 10 17:49:03.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:03.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:03.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:03.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Jan 10 17:49:03.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:03.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:03.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:03.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:03.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:03.679: INFO: Jan 10 17:49:05.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:05.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:05.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:05.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Jan 10 17:49:05.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:05.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:05.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:05.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:05.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:05.681: INFO: Jan 10 17:49:07.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:07.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:07.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:07.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Jan 10 17:49:07.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:07.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:07.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:07.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:07.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:07.682: INFO: Jan 10 17:49:09.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:09.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:09.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:09.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Jan 10 17:49:09.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:09.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:09.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:09.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:09.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:09.680: INFO: Jan 10 17:49:11.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:11.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:11.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:11.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Jan 10 17:49:11.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:11.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:11.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:11.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:11.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:11.679: INFO: Jan 10 17:49:13.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:13.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:13.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:13.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Jan 10 17:49:13.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:13.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:13.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:13.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:13.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:13.680: INFO: Jan 10 17:49:15.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:15.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:15.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:15.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Jan 10 17:49:15.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:15.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:15.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:15.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:15.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:15.679: INFO: Jan 10 17:49:17.689: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:17.689: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:17.689: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:17.689: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Jan 10 17:49:17.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:17.689: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:17.689: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:17.689: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:17.689: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:17.689: INFO: Jan 10 17:49:19.678: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:19.678: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:19.678: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:19.678: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Jan 10 17:49:19.678: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:19.678: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:19.678: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:19.678: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:19.678: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:19.678: INFO: Jan 10 17:49:21.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:21.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:21.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:21.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Jan 10 17:49:21.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:21.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:21.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:21.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:21.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:21.680: INFO: Jan 10 17:49:23.678: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:23.678: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:23.678: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:23.678: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Jan 10 17:49:23.678: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:23.678: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:23.678: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:23.678: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:23.678: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:23.678: INFO: Jan 10 17:49:25.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:25.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:25.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:25.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Jan 10 17:49:25.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:25.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:25.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:25.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:25.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:25.681: INFO: Jan 10 17:49:27.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:27.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:27.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:27.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Jan 10 17:49:27.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:27.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:27.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:27.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:27.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:27.684: INFO: Jan 10 17:49:29.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:29.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:29.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:29.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Jan 10 17:49:29.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:29.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:29.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:29.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:29.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:29.680: INFO: Jan 10 17:49:31.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:31.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:31.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:31.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Jan 10 17:49:31.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:31.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:31.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:31.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:31.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:31.680: INFO: Jan 10 17:49:33.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:33.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:33.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:33.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Jan 10 17:49:33.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:33.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:33.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:33.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:33.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:33.681: INFO: Jan 10 17:49:35.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:35.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:35.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:35.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Jan 10 17:49:35.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:35.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:35.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:35.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:35.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:35.679: INFO: Jan 10 17:49:37.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:37.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:37.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:37.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Jan 10 17:49:37.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:37.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:37.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:37.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:37.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:37.682: INFO: Jan 10 17:49:39.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:39.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:39.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:39.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Jan 10 17:49:39.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:39.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:39.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:39.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:39.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:39.681: INFO: Jan 10 17:49:41.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:41.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:41.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:41.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Jan 10 17:49:41.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:41.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:41.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:41.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:41.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:41.679: INFO: Jan 10 17:49:43.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:43.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:43.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:43.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Jan 10 17:49:43.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:43.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:43.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:43.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:43.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:43.679: INFO: Jan 10 17:49:45.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:45.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:45.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:45.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Jan 10 17:49:45.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:45.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:45.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:45.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:45.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:45.679: INFO: Jan 10 17:49:47.689: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:47.689: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:47.689: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:47.689: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Jan 10 17:49:47.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:47.689: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:47.689: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:47.689: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:47.689: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:47.689: INFO: Jan 10 17:49:49.678: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:49.678: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:49.678: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:49.678: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Jan 10 17:49:49.678: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:49.678: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:49.678: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:49.678: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:49.678: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:49.678: INFO: Jan 10 17:49:51.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:51.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:51.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:51.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Jan 10 17:49:51.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:51.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:51.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:51.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:51.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:51.679: INFO: Jan 10 17:49:53.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:53.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:53.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:53.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Jan 10 17:49:53.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:53.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:53.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:53.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:53.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:53.684: INFO: Jan 10 17:49:55.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:55.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:55.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:55.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Jan 10 17:49:55.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:55.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:55.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:55.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:55.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:55.680: INFO: Jan 10 17:49:57.705: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:57.705: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:57.705: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:57.705: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Jan 10 17:49:57.705: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:57.705: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:57.705: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:57.705: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:57.705: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:57.705: INFO: Jan 10 17:49:59.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:59.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:59.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:49:59.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Jan 10 17:49:59.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:49:59.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:49:59.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:59.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:59.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:49:59.680: INFO: Jan 10 17:50:01.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:01.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:01.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:01.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Jan 10 17:50:01.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:01.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:01.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:01.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:01.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:01.679: INFO: Jan 10 17:50:03.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:03.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:03.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:03.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Jan 10 17:50:03.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:03.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:03.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:03.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:03.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:03.680: INFO: Jan 10 17:50:05.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:05.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:05.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:05.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Jan 10 17:50:05.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:05.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:05.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:05.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:05.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:05.679: INFO: Jan 10 17:50:07.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:07.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:07.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:07.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Jan 10 17:50:07.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:07.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:07.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:07.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:07.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:07.682: INFO: Jan 10 17:50:09.678: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:09.678: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:09.678: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:09.678: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Jan 10 17:50:09.678: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:09.678: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:09.678: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:09.678: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:09.678: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:09.678: INFO: Jan 10 17:50:11.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:11.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:11.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:11.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Jan 10 17:50:11.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:11.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:11.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:11.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:11.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:11.681: INFO: Jan 10 17:50:13.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:13.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:13.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:13.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Jan 10 17:50:13.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:13.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:13.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:13.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:13.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:13.679: INFO: Jan 10 17:50:15.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:15.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:15.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:15.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Jan 10 17:50:15.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:15.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:15.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:15.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:15.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:15.679: INFO: Jan 10 17:50:17.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:17.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:17.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:17.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Jan 10 17:50:17.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:17.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:17.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:17.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:17.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:17.681: INFO: Jan 10 17:50:19.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:19.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:19.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:19.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Jan 10 17:50:19.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:19.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:19.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:19.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:19.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:19.680: INFO: Jan 10 17:50:21.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:21.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:21.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:21.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Jan 10 17:50:21.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:21.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:21.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:21.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:21.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:21.679: INFO: Jan 10 17:50:23.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:23.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:23.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:23.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Jan 10 17:50:23.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:23.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:23.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:23.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:23.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:23.684: INFO: Jan 10 17:50:25.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:25.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:25.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:25.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Jan 10 17:50:25.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:25.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:25.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:25.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:25.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:25.680: INFO: Jan 10 17:50:27.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:27.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:27.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:27.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Jan 10 17:50:27.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:27.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:27.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:27.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:27.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:27.682: INFO: Jan 10 17:50:29.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:29.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:29.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:29.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Jan 10 17:50:29.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:29.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:29.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:29.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:29.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:29.680: INFO: Jan 10 17:50:31.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:31.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:31.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:31.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Jan 10 17:50:31.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:31.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:31.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:31.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:31.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:31.680: INFO: Jan 10 17:50:33.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:33.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:33.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:33.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Jan 10 17:50:33.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:33.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:33.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:33.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:33.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:33.679: INFO: Jan 10 17:50:35.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:35.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:35.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:35.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Jan 10 17:50:35.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:35.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:35.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:35.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:35.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:35.679: INFO: Jan 10 17:50:37.690: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:37.690: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:37.690: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:37.690: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Jan 10 17:50:37.690: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:37.690: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:37.690: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:37.690: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:37.690: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:37.690: INFO: Jan 10 17:50:39.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:39.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:39.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:39.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Jan 10 17:50:39.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:39.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:39.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:39.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:39.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:39.680: INFO: Jan 10 17:50:41.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:41.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:41.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:41.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Jan 10 17:50:41.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:41.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:41.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:41.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:41.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:41.679: INFO: Jan 10 17:50:43.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:43.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:43.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:43.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Jan 10 17:50:43.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:43.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:43.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:43.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:43.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:43.688: INFO: Jan 10 17:50:45.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:45.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:45.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:45.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Jan 10 17:50:45.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:45.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:45.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:45.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:45.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:45.679: INFO: Jan 10 17:50:47.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:47.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:47.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:47.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Jan 10 17:50:47.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:47.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:47.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:47.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:47.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:47.683: INFO: Jan 10 17:50:49.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:49.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:49.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:49.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Jan 10 17:50:49.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:49.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:49.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:49.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:49.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:49.680: INFO: Jan 10 17:50:51.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:51.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:51.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:51.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Jan 10 17:50:51.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:51.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:51.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:51.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:51.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:51.680: INFO: Jan 10 17:50:53.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:53.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:53.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:53.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Jan 10 17:50:53.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:53.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:53.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:53.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:53.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:53.680: INFO: Jan 10 17:50:55.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:55.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:55.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:55.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Jan 10 17:50:55.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:55.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:55.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:55.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:55.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:55.680: INFO: Jan 10 17:50:57.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:57.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:57.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:57.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Jan 10 17:50:57.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:57.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:57.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:57.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:57.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:57.687: INFO: Jan 10 17:50:59.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:59.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:59.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:50:59.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Jan 10 17:50:59.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:50:59.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:50:59.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:59.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:59.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:50:59.681: INFO: Jan 10 17:51:01.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:01.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:01.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:01.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Jan 10 17:51:01.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:01.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:01.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:01.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:01.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:01.679: INFO: Jan 10 17:51:03.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:03.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:03.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:03.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Jan 10 17:51:03.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:03.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:03.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:03.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:03.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:03.680: INFO: Jan 10 17:51:05.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:05.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:05.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:05.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Jan 10 17:51:05.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:05.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:05.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:05.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:05.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:05.680: INFO: Jan 10 17:51:07.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:07.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:07.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:07.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Jan 10 17:51:07.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:07.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:07.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:07.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:07.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:07.686: INFO: Jan 10 17:51:09.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:09.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:09.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:09.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Jan 10 17:51:09.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:09.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:09.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:09.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:09.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:09.684: INFO: Jan 10 17:51:11.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:11.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:11.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:11.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Jan 10 17:51:11.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:11.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:11.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:11.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:11.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:11.680: INFO: Jan 10 17:51:13.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:13.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:13.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:13.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Jan 10 17:51:13.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:13.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:13.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:13.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:13.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:13.682: INFO: Jan 10 17:51:15.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:15.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:15.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:15.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Jan 10 17:51:15.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:15.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:15.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:15.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:15.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:15.682: INFO: Jan 10 17:51:17.686: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:17.686: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:17.686: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:17.686: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Jan 10 17:51:17.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:17.686: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:17.686: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:17.686: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:17.686: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:17.686: INFO: Jan 10 17:51:19.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:19.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:19.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:19.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Jan 10 17:51:19.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:19.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:19.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:19.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:19.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:19.680: INFO: Jan 10 17:51:21.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:21.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:21.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:21.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Jan 10 17:51:21.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:21.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:21.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:21.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:21.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:21.680: INFO: Jan 10 17:51:23.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:23.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:23.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:23.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Jan 10 17:51:23.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:23.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:23.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:23.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:23.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:23.683: INFO: Jan 10 17:51:25.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:25.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:25.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:25.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Jan 10 17:51:25.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:25.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:25.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:25.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:25.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:25.679: INFO: Jan 10 17:51:27.719: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:27.719: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:27.719: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:27.719: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Jan 10 17:51:27.719: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:27.719: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:27.719: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:27.719: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:27.719: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:27.719: INFO: Jan 10 17:51:29.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:29.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:29.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:29.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Jan 10 17:51:29.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:29.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:29.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:29.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:29.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:29.679: INFO: Jan 10 17:51:31.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:31.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:31.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:31.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Jan 10 17:51:31.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:31.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:31.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:31.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:31.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:31.680: INFO: Jan 10 17:51:33.678: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:33.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:33.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:33.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Jan 10 17:51:33.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:33.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:33.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:33.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:33.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:33.679: INFO: Jan 10 17:51:35.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:35.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:35.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:35.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Jan 10 17:51:35.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:35.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:35.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:35.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:35.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:35.679: INFO: Jan 10 17:51:37.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:37.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:37.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:37.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Jan 10 17:51:37.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:37.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:37.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:37.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:37.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:37.681: INFO: Jan 10 17:51:39.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:39.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:39.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:39.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Jan 10 17:51:39.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:39.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:39.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:39.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:39.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:39.681: INFO: Jan 10 17:51:41.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:41.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:41.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:41.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Jan 10 17:51:41.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:41.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:41.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:41.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:41.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:41.683: INFO: Jan 10 17:51:43.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:43.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:43.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:43.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Jan 10 17:51:43.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:43.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:43.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:43.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:43.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:43.683: INFO: Jan 10 17:51:45.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:45.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:45.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:45.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Jan 10 17:51:45.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:45.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:45.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:45.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:45.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:45.680: INFO: Jan 10 17:51:47.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:47.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:47.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:47.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Jan 10 17:51:47.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:47.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:47.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:47.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:47.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:47.684: INFO: Jan 10 17:51:49.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:49.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:49.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:49.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Jan 10 17:51:49.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:49.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:49.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:49.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:49.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:49.680: INFO: Jan 10 17:51:51.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:51.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:51.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:51.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Jan 10 17:51:51.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:51.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:51.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:51.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:51.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:51.682: INFO: Jan 10 17:51:53.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:53.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:53.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:53.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Jan 10 17:51:53.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:53.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:53.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:53.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:53.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:53.680: INFO: Jan 10 17:51:55.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:55.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:55.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:55.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Jan 10 17:51:55.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:55.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:55.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:55.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:55.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:55.691: INFO: Jan 10 17:51:57.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:57.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:57.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:57.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Jan 10 17:51:57.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:57.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:57.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:57.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:57.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:57.687: INFO: Jan 10 17:51:59.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:59.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:59.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:51:59.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Jan 10 17:51:59.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:51:59.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:51:59.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:59.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:59.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:51:59.679: INFO: Jan 10 17:52:01.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:01.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:01.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:01.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Jan 10 17:52:01.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:01.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:01.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:01.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:01.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:01.679: INFO: Jan 10 17:52:03.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:03.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:03.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:03.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Jan 10 17:52:03.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:03.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:03.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:03.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:03.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:03.679: INFO: Jan 10 17:52:05.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:05.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:05.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:05.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Jan 10 17:52:05.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:05.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:05.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:05.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:05.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:05.679: INFO: Jan 10 17:52:07.687: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:07.687: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:07.687: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:07.687: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Jan 10 17:52:07.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:07.687: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:07.687: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:07.687: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:07.687: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:07.687: INFO: Jan 10 17:52:09.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:09.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:09.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:09.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Jan 10 17:52:09.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:09.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:09.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:09.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:09.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:09.680: INFO: Jan 10 17:52:11.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:11.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:11.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:11.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Jan 10 17:52:11.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:11.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:11.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:11.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:11.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:11.682: INFO: Jan 10 17:52:13.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:13.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:13.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:13.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Jan 10 17:52:13.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:13.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:13.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:13.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:13.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:13.681: INFO: Jan 10 17:52:15.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:15.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:15.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:15.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Jan 10 17:52:15.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:15.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:15.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:15.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:15.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:15.679: INFO: Jan 10 17:52:17.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:17.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:17.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:17.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Jan 10 17:52:17.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:17.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:17.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:17.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:17.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:17.680: INFO: Jan 10 17:52:19.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:19.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:19.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:19.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Jan 10 17:52:19.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:19.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:19.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:19.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:19.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:19.680: INFO: Jan 10 17:52:21.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:21.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:21.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:21.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Jan 10 17:52:21.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:21.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:21.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:21.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:21.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:21.681: INFO: Jan 10 17:52:23.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:23.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:23.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:23.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Jan 10 17:52:23.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:23.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:23.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:23.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:23.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:23.681: INFO: Jan 10 17:52:25.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:25.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:25.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:25.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Jan 10 17:52:25.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:25.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:25.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:25.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:25.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:25.679: INFO: Jan 10 17:52:27.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:27.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:27.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:27.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Jan 10 17:52:27.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:27.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:27.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:27.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:27.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:27.683: INFO: Jan 10 17:52:29.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:29.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:29.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:29.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Jan 10 17:52:29.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:29.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:29.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:29.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:29.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:29.680: INFO: Jan 10 17:52:31.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:31.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:31.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:31.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Jan 10 17:52:31.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:31.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:31.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:31.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:31.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:31.679: INFO: Jan 10 17:52:33.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:33.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:33.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:33.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Jan 10 17:52:33.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:33.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:33.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:33.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:33.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:33.681: INFO: Jan 10 17:52:35.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:35.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:35.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:35.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Jan 10 17:52:35.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:35.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:35.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:35.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:35.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:35.681: INFO: Jan 10 17:52:37.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:37.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:37.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:37.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Jan 10 17:52:37.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:37.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:37.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:37.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:37.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:37.684: INFO: Jan 10 17:52:39.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:39.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:39.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:39.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Jan 10 17:52:39.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:39.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:39.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:39.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:39.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:39.681: INFO: Jan 10 17:52:41.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:41.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:41.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:41.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Jan 10 17:52:41.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:41.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:41.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:41.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:41.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:41.681: INFO: Jan 10 17:52:43.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:43.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:43.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:43.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Jan 10 17:52:43.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:43.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:43.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:43.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:43.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:43.680: INFO: Jan 10 17:52:45.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:45.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:45.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:45.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Jan 10 17:52:45.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:45.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:45.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:45.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:45.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:45.681: INFO: Jan 10 17:52:47.688: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:47.688: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:47.688: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:47.688: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Jan 10 17:52:47.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:47.688: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:47.688: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:47.688: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:47.688: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:47.688: INFO: Jan 10 17:52:49.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:49.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:49.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:49.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Jan 10 17:52:49.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:49.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:49.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:49.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:49.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:49.679: INFO: Jan 10 17:52:51.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:51.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:51.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:51.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Jan 10 17:52:51.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:51.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:51.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:51.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:51.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:51.680: INFO: Jan 10 17:52:53.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:53.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:53.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:53.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Jan 10 17:52:53.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:53.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:53.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:53.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:53.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:53.684: INFO: Jan 10 17:52:55.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:55.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:55.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:55.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Jan 10 17:52:55.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:55.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:55.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:55.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:55.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:55.680: INFO: Jan 10 17:52:57.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:57.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:57.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:57.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Jan 10 17:52:57.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:57.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:57.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:57.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:57.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:57.681: INFO: Jan 10 17:52:59.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:59.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:59.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:52:59.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Jan 10 17:52:59.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:52:59.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:52:59.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:59.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:59.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:52:59.680: INFO: Jan 10 17:53:01.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:01.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:01.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:01.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Jan 10 17:53:01.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:01.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:01.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:01.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:01.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:01.680: INFO: Jan 10 17:53:03.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:03.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:03.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:03.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Jan 10 17:53:03.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:03.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:03.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:03.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:03.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:03.680: INFO: Jan 10 17:53:05.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:05.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:05.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:05.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Jan 10 17:53:05.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:05.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:05.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:05.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:05.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:05.681: INFO: Jan 10 17:53:07.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:07.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:07.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:07.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Jan 10 17:53:07.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:07.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:07.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:07.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:07.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:07.681: INFO: Jan 10 17:53:09.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:09.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:09.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:09.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Jan 10 17:53:09.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:09.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:09.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:09.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:09.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:09.679: INFO: Jan 10 17:53:11.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:11.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:11.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:11.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Jan 10 17:53:11.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:11.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:11.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:11.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:11.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:11.679: INFO: Jan 10 17:53:13.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:13.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:13.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:13.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Jan 10 17:53:13.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:13.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:13.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:13.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:13.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:13.679: INFO: Jan 10 17:53:15.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:15.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:15.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:15.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Jan 10 17:53:15.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:15.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:15.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:15.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:15.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:15.679: INFO: Jan 10 17:53:17.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:17.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:17.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:17.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Jan 10 17:53:17.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:17.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:17.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:17.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:17.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:17.680: INFO: Jan 10 17:53:19.689: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:19.689: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:19.689: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:19.689: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Jan 10 17:53:19.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:19.689: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:19.689: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:19.689: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:19.689: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:19.689: INFO: Jan 10 17:53:21.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:21.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:21.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:21.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Jan 10 17:53:21.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:21.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:21.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:21.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:21.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:21.679: INFO: Jan 10 17:53:23.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:23.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:23.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:23.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Jan 10 17:53:23.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:23.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:23.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:23.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:23.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:23.679: INFO: Jan 10 17:53:25.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:25.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:25.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:25.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Jan 10 17:53:25.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:25.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:25.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:25.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:25.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:25.680: INFO: Jan 10 17:53:27.684: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:27.684: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:27.684: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:27.684: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Jan 10 17:53:27.684: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:27.684: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:27.684: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:27.684: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:27.684: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:27.684: INFO: Jan 10 17:53:29.678: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:29.678: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:29.678: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:29.678: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Jan 10 17:53:29.678: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:29.678: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:29.678: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:29.678: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:29.678: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:29.678: INFO: Jan 10 17:53:31.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:31.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:31.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:31.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Jan 10 17:53:31.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:31.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:31.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:31.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:31.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:31.681: INFO: Jan 10 17:53:33.683: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:33.683: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:33.683: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:33.683: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Jan 10 17:53:33.683: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:33.683: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:33.683: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:33.683: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:33.683: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:33.683: INFO: Jan 10 17:53:35.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:35.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:35.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:35.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Jan 10 17:53:35.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:35.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:35.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:35.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:35.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:35.681: INFO: Jan 10 17:53:37.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:37.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:37.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:37.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Jan 10 17:53:37.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:37.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:37.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:37.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:37.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:37.681: INFO: Jan 10 17:53:39.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:39.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:39.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:39.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Jan 10 17:53:39.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:39.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:39.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:39.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:39.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:39.679: INFO: Jan 10 17:53:41.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:41.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:41.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:41.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Jan 10 17:53:41.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:41.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:41.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:41.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:41.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:41.679: INFO: Jan 10 17:53:43.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:43.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:43.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:43.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Jan 10 17:53:43.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:43.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:43.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:43.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:43.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:43.680: INFO: Jan 10 17:53:45.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:45.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:45.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:45.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Jan 10 17:53:45.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:45.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:45.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:45.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:45.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:45.679: INFO: Jan 10 17:53:47.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:47.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:47.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:47.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Jan 10 17:53:47.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:47.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:47.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:47.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:47.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:47.681: INFO: Jan 10 17:53:49.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:49.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:49.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:49.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Jan 10 17:53:49.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:49.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:49.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:49.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:49.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:49.679: INFO: Jan 10 17:53:51.682: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:51.682: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:51.682: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:51.682: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Jan 10 17:53:51.682: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:51.682: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:51.682: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:51.682: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:51.682: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:51.682: INFO: Jan 10 17:53:53.680: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:53.680: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:53.680: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:53.680: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Jan 10 17:53:53.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:53.680: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:53.680: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:53.680: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:53.680: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:53.680: INFO: Jan 10 17:53:55.679: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:55.679: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:55.679: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:55.679: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Jan 10 17:53:55.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:55.679: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:55.679: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:55.679: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:55.679: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:55.679: INFO: Jan 10 17:53:57.691: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:57.691: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:57.691: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:57.691: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Jan 10 17:53:57.691: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:57.691: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:57.691: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:57.691: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:57.691: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:57.691: INFO: Jan 10 17:53:59.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:59.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:59.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:53:59.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Jan 10 17:53:59.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:53:59.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:53:59.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:59.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:59.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:53:59.681: INFO: Jan 10 17:54:01.681: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:54:01.681: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:54:01.681: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:54:01.681: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 10 17:54:01.681: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:54:01.681: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:54:01.681: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:01.681: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:01.681: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:01.681: INFO: Jan 10 17:54:02.099: INFO: The status of Pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:54:02.099: INFO: The status of Pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:54:02.099: INFO: The status of Pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 10 17:54:02.099: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (601 seconds elapsed) Jan 10 17:54:02.099: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 10 17:54:02.099: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:54:02.099: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:02.099: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:02.099: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:02.099: INFO: STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/10/23 17:54:02.099 STEP: Found 96 events. - test/e2e/framework/debug/dump.go:46 @ 01/10/23 17:54:02.257 Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:08 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-0y4fvh-control-plane-ngkpc_effcd19f-b46e-4929-bf1d-843c98265f8d became leader Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:08 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-0y4fvh-control-plane-ngkpc_19b1e9cb-2302-4cca-bf88-b09c9d53401a became leader Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:13 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2 Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:13 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-8xnpq Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:13 +0000 UTC - event for kube-proxy-8xnpq: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-8xnpq to capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:14 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-m8l5b Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:14 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-d6mp9 Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:14 +0000 UTC - event for coredns-56f4c55bf9-d6mp9: {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 17:54:02.257: INFO: At 2023-01-10 17:41:14 +0000 UTC - event for coredns-56f4c55bf9-m8l5b: {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 17:54:02.257: INFO: At 2023-01-10 17:41:14 +0000 UTC - event for kube-proxy-8xnpq: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:18 +0000 UTC - event for kube-proxy-8xnpq: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Created: Created container kube-proxy Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:18 +0000 UTC - event for kube-proxy-8xnpq: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844" in 4.383385336s (4.383400536s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:19 +0000 UTC - event for kube-proxy-8xnpq: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Started: Started container kube-proxy Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:24 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:24 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-dqm4l Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:24 +0000 UTC - event for metrics-server-c9574f845-dqm4l: {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 17:54:02.257: INFO: At 2023-01-10 17:41:26 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1 Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:26 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-vlkgz Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:26 +0000 UTC - event for calico-kube-controllers-657b584867-vlkgz: {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 17:54:02.257: INFO: At 2023-01-10 17:41:27 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-7rndv Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:27 +0000 UTC - event for calico-node-7rndv: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-7rndv to capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:27 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:34 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Created: Created container upgrade-ipam Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:34 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.93825096s (6.938260061s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:34 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Started: Started container upgrade-ipam Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:37 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:37 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Created: Created container install-cni Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:37 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Started: Started container install-cni Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:39 +0000 UTC - event for calico-kube-controllers-657b584867-vlkgz: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-vlkgz to capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:39 +0000 UTC - event for coredns-56f4c55bf9-d6mp9: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-d6mp9 to capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:39 +0000 UTC - event for coredns-56f4c55bf9-m8l5b: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-m8l5b to capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:39 +0000 UTC - event for metrics-server-c9574f845-dqm4l: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-dqm4l to capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:40 +0000 UTC - event for calico-kube-controllers-657b584867-vlkgz: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "29d23791d52733cda14fc57b0c0ee42a4e11e288445ad7843eb0917f2c436467": 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 17:54:02.257: INFO: At 2023-01-10 17:41:40 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:40 +0000 UTC - event for coredns-56f4c55bf9-d6mp9: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "837329498e541cfd68f36a0592e1d5f7b6f89a306ae76a8d71f7a480ad2266f5": 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 17:54:02.257: INFO: At 2023-01-10 17:41:40 +0000 UTC - event for coredns-56f4c55bf9-m8l5b: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "67283030daf01c6a7caad8442feb2f64a8d122001a17e667129b1b3e0d0d15ba": 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 17:54:02.257: INFO: At 2023-01-10 17:41:40 +0000 UTC - event for metrics-server-c9574f845-dqm4l: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "f44eb28db3e15321ef4ed9dde21522531d6671930a61b4c9201550c128c7e3f1": 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 17:54:02.257: INFO: At 2023-01-10 17:41:47 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Created: Created container calico-node Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:47 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.766545754s (7.766550654s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:48 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Started: Started container calico-node Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:50 +0000 UTC - event for calico-node-7rndv: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} 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 17:54:02.257: INFO: At 2023-01-10 17:41:51 +0000 UTC - event for calico-kube-controllers-657b584867-vlkgz: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:52 +0000 UTC - event for coredns-56f4c55bf9-d6mp9: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:52 +0000 UTC - event for coredns-56f4c55bf9-d6mp9: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Started: Started container coredns Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:52 +0000 UTC - event for coredns-56f4c55bf9-d6mp9: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Created: Created container coredns Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:53 +0000 UTC - event for metrics-server-c9574f845-dqm4l: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:56 +0000 UTC - event for coredns-56f4c55bf9-m8l5b: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Created: Created container coredns Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:56 +0000 UTC - event for coredns-56f4c55bf9-m8l5b: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Started: Started container coredns Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:56 +0000 UTC - event for coredns-56f4c55bf9-m8l5b: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:57 +0000 UTC - event for calico-kube-controllers-657b584867-vlkgz: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 6.282507831s (6.282593332s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:57 +0000 UTC - event for calico-kube-controllers-657b584867-vlkgz: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Started: Started container calico-kube-controllers Jan 10 17:54:02.257: INFO: At 2023-01-10 17:41:57 +0000 UTC - event for calico-kube-controllers-657b584867-vlkgz: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Created: Created container calico-kube-controllers Jan 10 17:54:02.257: INFO: At 2023-01-10 17:42:01 +0000 UTC - event for metrics-server-c9574f845-dqm4l: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Started: Started container metrics-server Jan 10 17:54:02.257: INFO: At 2023-01-10 17:42:01 +0000 UTC - event for metrics-server-c9574f845-dqm4l: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.673170209s (7.767400247s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:42:01 +0000 UTC - event for metrics-server-c9574f845-dqm4l: {kubelet capz-conf-0y4fvh-control-plane-ngkpc} Created: Created container metrics-server Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:11 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-4rsq5 Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:11 +0000 UTC - event for calico-node-4rsq5: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-4rsq5 to capz-conf-0y4fvh-md-0-vk2xn Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:11 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-599bz Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:11 +0000 UTC - event for kube-proxy-599bz: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-599bz to capz-conf-0y4fvh-md-0-vk2xn Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:19 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:19 +0000 UTC - event for kube-proxy-599bz: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:29 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-z7qnd Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:29 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Started: Started container upgrade-ipam Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:29 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 9.205993166s (9.206179374s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:29 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Created: Created container upgrade-ipam Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:29 +0000 UTC - event for calico-node-z7qnd: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-z7qnd to capz-conf-0y4fvh-md-0-8r4jw Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:29 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-88889 Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:29 +0000 UTC - event for kube-proxy-88889: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-88889 to capz-conf-0y4fvh-md-0-8r4jw Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:31 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:31 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Created: Created container install-cni Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:31 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Started: Started container install-cni Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:35 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:36 +0000 UTC - event for kube-proxy-599bz: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Created: Created container kube-proxy Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:36 +0000 UTC - event for kube-proxy-599bz: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Started: Started container kube-proxy Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:36 +0000 UTC - event for kube-proxy-599bz: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844" in 7.051560052s (16.241861494s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:38 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:38 +0000 UTC - event for kube-proxy-88889: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:45 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.5548657s (10.197135329s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:45 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Created: Created container calico-node Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:45 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} Started: Started container calico-node Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:46 +0000 UTC - event for calico-node-4rsq5: {kubelet capz-conf-0y4fvh-md-0-vk2xn} 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 17:54:02.257: INFO: At 2023-01-10 17:43:46 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Started: Started container upgrade-ipam Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:46 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Created: Created container upgrade-ipam Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:46 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 8.651437644s (8.651640346s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:49 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Started: Started container install-cni Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:49 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Created: Created container install-cni Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:49 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:53 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:53 +0000 UTC - event for kube-proxy-88889: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Started: Started container kube-proxy Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:53 +0000 UTC - event for kube-proxy-88889: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844" in 6.717368509s (15.35929558s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:43:53 +0000 UTC - event for kube-proxy-88889: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Created: Created container kube-proxy Jan 10 17:54:02.257: INFO: At 2023-01-10 17:44:03 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Started: Started container calico-node Jan 10 17:54:02.257: INFO: At 2023-01-10 17:44:03 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Created: Created container calico-node Jan 10 17:54:02.257: INFO: At 2023-01-10 17:44:03 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.968945057s (9.968962159s including waiting) Jan 10 17:54:02.257: INFO: At 2023-01-10 17:44:04 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} 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 17:54:02.257: INFO: At 2023-01-10 17:44:05 +0000 UTC - event for calico-node-z7qnd: {kubelet capz-conf-0y4fvh-md-0-8r4jw} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Jan 10 17:54:02.416: INFO: POD NODE PHASE GRACE CONDITIONS Jan 10 17:54:02.416: INFO: calico-kube-controllers-657b584867-vlkgz capz-conf-0y4fvh-control-plane-ngkpc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:58 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:58 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:39 +0000 UTC }] Jan 10 17:54:02.416: INFO: calico-node-4rsq5 capz-conf-0y4fvh-md-0-vk2xn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:35 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:11 +0000 UTC }] Jan 10 17:54:02.416: INFO: calico-node-7rndv capz-conf-0y4fvh-control-plane-ngkpc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:40 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:57 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:57 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:27 +0000 UTC }] Jan 10 17:54:02.416: INFO: calico-node-z7qnd capz-conf-0y4fvh-md-0-8r4jw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:44:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:44:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:54:02.416: INFO: coredns-56f4c55bf9-d6mp9 capz-conf-0y4fvh-control-plane-ngkpc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:53 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:39 +0000 UTC }] Jan 10 17:54:02.416: INFO: coredns-56f4c55bf9-m8l5b capz-conf-0y4fvh-control-plane-ngkpc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:57 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:57 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:39 +0000 UTC }] Jan 10 17:54:02.416: INFO: etcd-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:40:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:15 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:15 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:40:43 +0000 UTC }] Jan 10 17:54:02.416: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:02.416: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:02.416: INFO: kube-proxy-599bz capz-conf-0y4fvh-md-0-vk2xn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:36 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:36 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:11 +0000 UTC }] Jan 10 17:54:02.416: INFO: kube-proxy-88889 capz-conf-0y4fvh-md-0-8r4jw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:33 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:54 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:43:29 +0000 UTC }] Jan 10 17:54:02.416: INFO: kube-proxy-8xnpq capz-conf-0y4fvh-control-plane-ngkpc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:13 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:19 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:13 +0000 UTC }] Jan 10 17:54:02.416: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] Jan 10 17:54:02.416: INFO: metrics-server-c9574f845-dqm4l capz-conf-0y4fvh-control-plane-ngkpc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:42:30 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:42:30 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-10 17:41:39 +0000 UTC }] Jan 10 17:54:02.416: INFO: Jan 10 17:54:03.097: INFO: Logging node info for node capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:03.204: INFO: Node Info: &Node{ObjectMeta:{capz-conf-0y4fvh-control-plane-ngkpc 9d9cafad-54b3-41e0-9cbe-b1bbaf65c78d 1698 0 2023-01-10 17:41:04 +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:uksouth failure-domain.beta.kubernetes.io/zone:uksouth-2 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-0y4fvh-control-plane-ngkpc 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:uksouth topology.kubernetes.io/zone:uksouth-2] map[cluster.x-k8s.io/cluster-name:capz-conf-0y4fvh cluster.x-k8s.io/cluster-namespace:capz-conf-0y4fvh cluster.x-k8s.io/machine:capz-conf-0y4fvh-control-plane-lpd5b cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-0y4fvh-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.86.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-10 17:41:04 +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 17:41:07 +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 17:41:21 +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 17:41:39 +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 17:41:50 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-10 17:52:21 +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-0y4fvh/providers/Microsoft.Compute/virtualMachines/capz-conf-0y4fvh-control-plane-ngkpc,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: {{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 17:41:50 +0000 UTC,LastTransitionTime:2023-01-10 17:41:50 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-10 17:52:21 +0000 UTC,LastTransitionTime:2023-01-10 17:40:43 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-10 17:52:21 +0000 UTC,LastTransitionTime:2023-01-10 17:40:43 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-10 17:52:21 +0000 UTC,LastTransitionTime:2023-01-10 17:40:43 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-10 17:52:21 +0000 UTC,LastTransitionTime:2023-01-10 17:41:39 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-0y4fvh-control-plane-ngkpc,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:f1b1dd2626574f5a9a715caa9706a54f,SystemUUID:151f3987-ff20-f14b-9fda-0dd82e1210f7,BootID:6e768dbe-eb49-4fc7-b683-b777cdf03664,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.883+3cefa8b8fb0844,KubeProxyVersion:v1.27.0-alpha.0.883+3cefa8b8fb0844,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:ec5cbf89d26d45dea7d4e40136e9d29609cd6dee0a068d917e812396fbb3168f gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.865_5cbd6960c805c2],SizeBytes:35424145,},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:a3179b48135987411a68607a8fb9b8f62dd820a50bd0dde5bccd87b9d905b601 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.865_5cbd6960c805c2],SizeBytes:32318956,},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:bf976e816cfe7daa5eeda1008fde17e1a4c4ad96c6d7fd3a356b27afbf4cb72a gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.865_5cbd6960c805c2],SizeBytes:21541820,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:7f506fbb984ed99115e327fafcbe1644ad4c330c365464012252634a622ecf7c capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844],SizeBytes:21539928,},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:83e8d72ff8d33013b094a0c7435f5abaa8d79618b96e2cc95ede05573b6d8896 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.865_5cbd6960c805c2],SizeBytes:17522516,},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 17:54:03.205: INFO: Logging kubelet events for node capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:03.308: INFO: Logging pods the kubelet thinks is on node capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:03.449: INFO: kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc started at <nil> (0+0 container statuses recorded) Jan 10 17:54:03.449: INFO: kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc started at <nil> (0+0 container statuses recorded) Jan 10 17:54:03.449: INFO: kube-proxy-8xnpq started at 2023-01-10 17:41:13 +0000 UTC (0+1 container statuses recorded) Jan 10 17:54:03.449: INFO: Container kube-proxy ready: true, restart count 0 Jan 10 17:54:03.449: INFO: coredns-56f4c55bf9-d6mp9 started at 2023-01-10 17:41:39 +0000 UTC (0+1 container statuses recorded) Jan 10 17:54:03.449: INFO: Container coredns ready: true, restart count 0 Jan 10 17:54:03.449: INFO: coredns-56f4c55bf9-m8l5b started at 2023-01-10 17:41:39 +0000 UTC (0+1 container statuses recorded) Jan 10 17:54:03.449: INFO: Container coredns ready: true, restart count 0 Jan 10 17:54:03.449: INFO: etcd-capz-conf-0y4fvh-control-plane-ngkpc started at 2023-01-10 17:40:43 +0000 UTC (0+1 container statuses recorded) Jan 10 17:54:03.449: INFO: Container etcd ready: true, restart count 0 Jan 10 17:54:03.449: INFO: kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc started at <nil> (0+0 container statuses recorded) Jan 10 17:54:03.449: INFO: calico-node-7rndv started at 2023-01-10 17:41:27 +0000 UTC (2+1 container statuses recorded) Jan 10 17:54:03.449: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 10 17:54:03.449: INFO: Init container install-cni ready: true, restart count 0 Jan 10 17:54:03.449: INFO: Container calico-node ready: true, restart count 0 Jan 10 17:54:03.449: INFO: metrics-server-c9574f845-dqm4l started at 2023-01-10 17:41:39 +0000 UTC (0+1 container statuses recorded) Jan 10 17:54:03.449: INFO: Container metrics-server ready: true, restart count 0 Jan 10 17:54:03.449: INFO: calico-kube-controllers-657b584867-vlkgz started at 2023-01-10 17:41:39 +0000 UTC (0+1 container statuses recorded) Jan 10 17:54:03.449: INFO: Container calico-kube-controllers ready: true, restart count 0 Jan 10 17:54:03.856: INFO: Latency metrics for node capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:03.856: INFO: Logging node info for node capz-conf-0y4fvh-md-0-8r4jw Jan 10 17:54:03.961: INFO: Node Info: &Node{ObjectMeta:{capz-conf-0y4fvh-md-0-8r4jw c3dc4324-b0d9-4c16-9c56-4ca4bb6d9281 1436 0 2023-01-10 17:43:29 +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:uksouth failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-0y4fvh-md-0-8r4jw kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:uksouth topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-0y4fvh cluster.x-k8s.io/cluster-namespace:capz-conf-0y4fvh cluster.x-k8s.io/machine:capz-conf-0y4fvh-md-0-7d48dcf995-q5lbv cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-0y4fvh-md-0-7d48dcf995 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.167.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-10 17:43:29 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-10 17:43:29 +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":{}}} } {manager Update v1 2023-01-10 17:43:51 +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 17:43:52 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-10 17:44:04 +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 17:49:26 +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-0y4fvh/providers/Microsoft.Compute/virtualMachines/capz-conf-0y4fvh-md-0-8r4jw,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 17:44:04 +0000 UTC,LastTransitionTime:2023-01-10 17:44:04 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-10 17:49:26 +0000 UTC,LastTransitionTime:2023-01-10 17:43:29 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-10 17:49:26 +0000 UTC,LastTransitionTime:2023-01-10 17:43:29 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-10 17:49:26 +0000 UTC,LastTransitionTime:2023-01-10 17:43:29 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-10 17:49:26 +0000 UTC,LastTransitionTime:2023-01-10 17:43:52 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-0y4fvh-md-0-8r4jw,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:72979f59bf684c6daff3aa172536f0d9,SystemUUID:824d5119-3294-1f40-bfe0-a6726c109e81,BootID:ad9bd1f6-f651-49ce-9820-31d79b670c5c,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.883+3cefa8b8fb0844,KubeProxyVersion:v1.27.0-alpha.0.883+3cefa8b8fb0844,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:7f506fbb984ed99115e327fafcbe1644ad4c330c365464012252634a622ecf7c capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844],SizeBytes:21539928,},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 17:54:03.961: INFO: Logging kubelet events for node capz-conf-0y4fvh-md-0-8r4jw Jan 10 17:54:04.066: INFO: Logging pods the kubelet thinks is on node capz-conf-0y4fvh-md-0-8r4jw Jan 10 17:54:04.178: INFO: calico-node-z7qnd started at 2023-01-10 17:43:33 +0000 UTC (2+1 container statuses recorded) Jan 10 17:54:04.178: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 10 17:54:04.178: INFO: Init container install-cni ready: true, restart count 0 Jan 10 17:54:04.178: INFO: Container calico-node ready: true, restart count 0 Jan 10 17:54:04.178: INFO: kube-proxy-88889 started at 2023-01-10 17:43:33 +0000 UTC (0+1 container statuses recorded) Jan 10 17:54:04.178: INFO: Container kube-proxy ready: true, restart count 0 Jan 10 17:54:04.576: INFO: Latency metrics for node capz-conf-0y4fvh-md-0-8r4jw Jan 10 17:54:04.576: INFO: Logging node info for node capz-conf-0y4fvh-md-0-vk2xn Jan 10 17:54:04.681: INFO: Node Info: &Node{ObjectMeta:{capz-conf-0y4fvh-md-0-vk2xn b9f9eda6-abd5-4cb2-a827-6db2d19bd99c 1409 0 2023-01-10 17:43:11 +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:uksouth failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-0y4fvh-md-0-vk2xn kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:uksouth topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-0y4fvh cluster.x-k8s.io/cluster-namespace:capz-conf-0y4fvh cluster.x-k8s.io/machine:capz-conf-0y4fvh-md-0-7d48dcf995-tqtpd cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-0y4fvh-md-0-7d48dcf995 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.116.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-10 17:43:11 +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 17:43:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {manager Update v1 2023-01-10 17:43:26 +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 17:43:34 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-10 17:43:46 +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 17:49:09 +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-0y4fvh/providers/Microsoft.Compute/virtualMachines/capz-conf-0y4fvh-md-0-vk2xn,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 17:43:46 +0000 UTC,LastTransitionTime:2023-01-10 17:43:46 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-10 17:49:09 +0000 UTC,LastTransitionTime:2023-01-10 17:43:11 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-10 17:49:09 +0000 UTC,LastTransitionTime:2023-01-10 17:43:11 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-10 17:49:09 +0000 UTC,LastTransitionTime:2023-01-10 17:43:11 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-10 17:49:09 +0000 UTC,LastTransitionTime:2023-01-10 17:43:34 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-0y4fvh-md-0-vk2xn,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:0b24378a5fbf4bfaaddb7e0b2afa7aa5,SystemUUID:a0d8e463-31e0-e642-89ee-a037dafe150e,BootID:13c2c012-8d57-42e7-8417-99c20ca1c0f9,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.883+3cefa8b8fb0844,KubeProxyVersion:v1.27.0-alpha.0.883+3cefa8b8fb0844,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:7f506fbb984ed99115e327fafcbe1644ad4c330c365464012252634a622ecf7c capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.883_3cefa8b8fb0844],SizeBytes:21539928,},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 17:54:04.682: INFO: Logging kubelet events for node capz-conf-0y4fvh-md-0-vk2xn Jan 10 17:54:04.785: INFO: Logging pods the kubelet thinks is on node capz-conf-0y4fvh-md-0-vk2xn Jan 10 17:54:04.898: INFO: calico-node-4rsq5 started at 2023-01-10 17:43:15 +0000 UTC (2+1 container statuses recorded) Jan 10 17:54:04.898: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 10 17:54:04.898: INFO: Init container install-cni ready: true, restart count 0 Jan 10 17:54:04.898: INFO: Container calico-node ready: true, restart count 0 Jan 10 17:54:04.898: INFO: kube-proxy-599bz started at 2023-01-10 17:43:15 +0000 UTC (0+1 container statuses recorded) Jan 10 17:54:04.898: INFO: Container kube-proxy ready: true, restart count 0 Jan 10 17:54:05.474: INFO: Latency metrics for node capz-conf-0y4fvh-md-0-vk2xn Jan 10 17:54:05.700: INFO: Running kubectl logs on non-ready containers in kube-system Jan 10 17:54:06.045: INFO: Failed to get logs of pod kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc) Jan 10 17:54:06.045: INFO: Logs of kube-system/kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc:kube-apiserver on node capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:06.045: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-0y4fvh-control-plane-ngkpc:kube-apiserver Jan 10 17:54:06.444: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc) Jan 10 17:54:06.444: INFO: Logs of kube-system/kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc:kube-controller-manager on node capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:06.444: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc:kube-controller-manager Jan 10 17:54:06.845: INFO: Failed to get logs of pod kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc) Jan 10 17:54:06.845: INFO: Logs of kube-system/kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc:kube-scheduler on node capz-conf-0y4fvh-control-plane-ngkpc Jan 10 17:54:06.845: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc: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-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] kube-controller-manager-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] kube-scheduler-capz-conf-0y4fvh-control-plane-ngkpc capz-conf-0y4fvh-control-plane-ngkpc Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:249 @ 01/10/23 17:54:06.845 < Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/10/23 17:54:06.845 (10m6.59s)
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 17:54:06.902from 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 17:54:06.902
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 17:54:06.901from 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 17:54:06.901
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 17:54:06.888from 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 17:54:06.888
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 17:54:06.9from 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 17:54:06.9
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