PR #114764 pull-kubernetes-e2e-capz-conformance #1618248203533029376
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | claudiubelu: unittests: Fixes unit tests for Windows (part 7) |
| Result | SUCCESS |
| Tests | 25 failed / 28 succeeded |
| Started | |
| Elapsed | 54m39s |
| Revision | d8b01e332c17d4c1fe4cbc9ef3928eaa5c93557d |
| Refs |
114764 |
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/25/23 14:52:15.034from 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/25/23 14:52:15.034
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/25/23 14:52:15.017from 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/25/23 14:52:15.017
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/25/23 14:52:15.017from 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/25/23 14:52:15.017
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/25/23 14:52:15.035from 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/25/23 14:52:15.035
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/25/23 14:52:15.016from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/25/23 14:52:15.016
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/25/23 14:52:15.011from 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/25/23 14:52:15.011
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/25/23 14:52:15.036from 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/25/23 14:52:15.036
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/25/23 14:52:15.046from 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/25/23 14:52:15.046
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/25/23 14:52:15.016from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/25/23 14:52:15.016
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/25/23 14:52:15.021from 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/25/23 14:52:15.021
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/25/23 14:52:15.035from 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/25/23 14:52:15.035
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/25/23 14:52:15.017from 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/25/23 14:52:15.017
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/25/23 14:52:15.043from 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/25/23 14:52:15.043
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/25/23 14:52:15.029from 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/25/23 14:52:15.029
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/25/23 14:52:15.007from 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/25/23 14:52:15.007
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/25/23 14:52:15.012from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/25/23 14:52:15.012
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/25/23 14:52:15.02from 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/25/23 14:52:15.02
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/25/23 14:52:15.008from 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/25/23 14:52:15.008
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-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/25/23 14:52:14.971from junit.kubetest.01.xml
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/25/23 14:42:08.396 Jan 25 14:42:08.396: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 25 14:42:08.398: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 25 14:42:08.876: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 25 14:42:09.424: INFO: The status of Pod calico-node-4cp9p is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:09.425: INFO: The status of Pod calico-node-k988f is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:09.425: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:09.425: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:09.425: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:09.425: INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 25 14:42:09.425: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:09.425: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:09.425: INFO: calico-node-4cp9p capz-conf-r52y03-md-0-hb5td Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:42:02 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:36 +0000 UTC }] Jan 25 14:42:09.425: INFO: calico-node-k988f capz-conf-r52y03-md-0-4zbgs Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC }] Jan 25 14:42:09.425: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:09.425: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:09.425: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:09.425: INFO: Jan 25 14:42:11.818: INFO: The status of Pod calico-node-4cp9p is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:11.818: INFO: The status of Pod calico-node-k988f is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:11.818: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:11.818: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:11.818: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:11.818: INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Jan 25 14:42:11.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:11.818: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:11.818: INFO: calico-node-4cp9p capz-conf-r52y03-md-0-hb5td Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:42:02 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:36 +0000 UTC }] Jan 25 14:42:11.818: INFO: calico-node-k988f capz-conf-r52y03-md-0-4zbgs Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC }] Jan 25 14:42:11.818: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:11.818: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:11.818: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:11.818: INFO: Jan 25 14:42:13.804: INFO: The status of Pod calico-node-4cp9p is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:13.804: INFO: The status of Pod calico-node-k988f is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:13.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:13.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:13.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:13.804: INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Jan 25 14:42:13.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:13.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:13.804: INFO: calico-node-4cp9p capz-conf-r52y03-md-0-hb5td Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:42:02 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:36 +0000 UTC }] Jan 25 14:42:13.805: INFO: calico-node-k988f capz-conf-r52y03-md-0-4zbgs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC }] Jan 25 14:42:13.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:13.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:13.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:13.805: INFO: Jan 25 14:42:15.801: INFO: The status of Pod calico-node-k988f is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:15.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:15.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:15.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:15.801: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Jan 25 14:42:15.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:15.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:15.801: INFO: calico-node-k988f capz-conf-r52y03-md-0-4zbgs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC }] Jan 25 14:42:15.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:15.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:15.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:15.801: INFO: Jan 25 14:42:17.800: INFO: The status of Pod calico-node-k988f is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:17.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:17.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:17.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:17.800: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Jan 25 14:42:17.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:17.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:17.800: INFO: calico-node-k988f capz-conf-r52y03-md-0-4zbgs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC }] Jan 25 14:42:17.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:17.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:17.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:17.800: INFO: Jan 25 14:42:19.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:19.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:19.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:19.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Jan 25 14:42:19.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:19.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:19.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:19.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:19.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:19.800: INFO: Jan 25 14:42:21.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:21.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:21.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:21.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Jan 25 14:42:21.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:21.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:21.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:21.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:21.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:21.797: INFO: Jan 25 14:42:23.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:23.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:23.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:23.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Jan 25 14:42:23.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:23.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:23.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:23.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:23.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:23.797: INFO: Jan 25 14:42:25.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:25.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:25.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:25.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Jan 25 14:42:25.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:25.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:25.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:25.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:25.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:25.796: INFO: Jan 25 14:42:27.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:27.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:27.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:27.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Jan 25 14:42:27.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:27.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:27.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:27.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:27.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:27.799: INFO: Jan 25 14:42:29.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:29.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:29.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:29.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Jan 25 14:42:29.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:29.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:29.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:29.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:29.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:29.801: INFO: Jan 25 14:42:31.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:31.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:31.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:31.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Jan 25 14:42:31.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:31.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:31.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:31.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:31.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:31.797: INFO: Jan 25 14:42:33.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:33.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:33.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:33.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Jan 25 14:42:33.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:33.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:33.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:33.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:33.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:33.798: INFO: Jan 25 14:42:35.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:35.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:35.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:35.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Jan 25 14:42:35.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:35.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:35.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:35.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:35.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:35.796: INFO: Jan 25 14:42:37.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:37.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:37.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:37.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Jan 25 14:42:37.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:37.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:37.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:37.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:37.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:37.796: INFO: Jan 25 14:42:39.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:39.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:39.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:39.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Jan 25 14:42:39.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:39.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:39.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:39.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:39.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:39.802: INFO: Jan 25 14:42:41.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:41.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:41.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:41.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Jan 25 14:42:41.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:41.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:41.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:41.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:41.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:41.800: INFO: Jan 25 14:42:43.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:43.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:43.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:43.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Jan 25 14:42:43.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:43.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:43.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:43.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:43.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:43.801: INFO: Jan 25 14:42:45.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:45.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:45.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:45.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Jan 25 14:42:45.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:45.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:45.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:45.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:45.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:45.798: INFO: Jan 25 14:42:47.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:47.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:47.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:47.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Jan 25 14:42:47.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:47.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:47.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:47.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:47.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:47.797: INFO: Jan 25 14:42:49.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:49.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:49.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:49.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Jan 25 14:42:49.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:49.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:49.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:49.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:49.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:49.806: INFO: Jan 25 14:42:51.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:51.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:51.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:51.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Jan 25 14:42:51.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:51.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:51.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:51.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:51.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:51.802: INFO: Jan 25 14:42:53.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:53.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:53.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:53.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Jan 25 14:42:53.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:53.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:53.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:53.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:53.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:53.798: INFO: Jan 25 14:42:55.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:55.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:55.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:55.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Jan 25 14:42:55.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:55.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:55.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:55.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:55.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:55.799: INFO: Jan 25 14:42:57.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:57.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:57.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:57.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Jan 25 14:42:57.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:57.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:57.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:57.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:57.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:57.797: INFO: Jan 25 14:42:59.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:59.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:59.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:42:59.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Jan 25 14:42:59.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:42:59.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:42:59.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:59.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:59.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:42:59.798: INFO: Jan 25 14:43:01.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:01.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:01.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:01.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Jan 25 14:43:01.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:01.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:01.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:01.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:01.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:01.796: INFO: Jan 25 14:43:03.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:03.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:03.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:03.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Jan 25 14:43:03.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:03.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:03.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:03.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:03.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:03.800: INFO: Jan 25 14:43:05.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:05.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:05.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:05.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Jan 25 14:43:05.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:05.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:05.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:05.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:05.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:05.797: INFO: Jan 25 14:43:07.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:07.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:07.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:07.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Jan 25 14:43:07.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:07.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:07.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:07.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:07.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:07.796: INFO: Jan 25 14:43:09.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:09.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:09.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:09.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Jan 25 14:43:09.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:09.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:09.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:09.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:09.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:09.801: INFO: Jan 25 14:43:11.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:11.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:11.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:11.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Jan 25 14:43:11.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:11.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:11.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:11.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:11.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:11.804: INFO: Jan 25 14:43:13.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:13.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:13.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:13.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Jan 25 14:43:13.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:13.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:13.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:13.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:13.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:13.802: INFO: Jan 25 14:43:15.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:15.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:15.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:15.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Jan 25 14:43:15.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:15.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:15.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:15.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:15.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:15.796: INFO: Jan 25 14:43:17.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:17.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:17.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:17.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Jan 25 14:43:17.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:17.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:17.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:17.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:17.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:17.798: INFO: Jan 25 14:43:19.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:19.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:19.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:19.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Jan 25 14:43:19.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:19.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:19.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:19.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:19.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:19.800: INFO: Jan 25 14:43:21.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:21.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:21.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:21.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Jan 25 14:43:21.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:21.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:21.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:21.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:21.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:21.798: INFO: Jan 25 14:43:23.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:23.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:23.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:23.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Jan 25 14:43:23.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:23.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:23.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:23.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:23.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:23.795: INFO: Jan 25 14:43:25.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:25.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:25.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:25.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Jan 25 14:43:25.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:25.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:25.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:25.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:25.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:25.797: INFO: Jan 25 14:43:27.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:27.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:27.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:27.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Jan 25 14:43:27.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:27.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:27.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:27.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:27.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:27.800: INFO: Jan 25 14:43:29.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:29.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:29.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:29.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Jan 25 14:43:29.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:29.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:29.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:29.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:29.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:29.798: INFO: Jan 25 14:43:31.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:31.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:31.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:31.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Jan 25 14:43:31.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:31.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:31.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:31.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:31.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:31.795: INFO: Jan 25 14:43:33.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:33.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:33.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:33.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Jan 25 14:43:33.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:33.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:33.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:33.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:33.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:33.801: INFO: Jan 25 14:43:35.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:35.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:35.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:35.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Jan 25 14:43:35.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:35.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:35.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:35.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:35.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:35.797: INFO: Jan 25 14:43:37.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:37.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:37.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:37.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Jan 25 14:43:37.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:37.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:37.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:37.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:37.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:37.796: INFO: Jan 25 14:43:39.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:39.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:39.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:39.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Jan 25 14:43:39.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:39.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:39.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:39.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:39.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:39.796: INFO: Jan 25 14:43:41.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:41.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:41.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:41.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Jan 25 14:43:41.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:41.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:41.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:41.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:41.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:41.796: INFO: Jan 25 14:43:43.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:43.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:43.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:43.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Jan 25 14:43:43.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:43.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:43.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:43.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:43.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:43.799: INFO: Jan 25 14:43:45.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:45.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:45.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:45.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Jan 25 14:43:45.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:45.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:45.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:45.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:45.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:45.798: INFO: Jan 25 14:43:47.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:47.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:47.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:47.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Jan 25 14:43:47.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:47.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:47.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:47.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:47.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:47.797: INFO: Jan 25 14:43:49.794: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:49.794: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:49.794: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:49.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Jan 25 14:43:49.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:49.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:49.794: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:49.794: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:49.794: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:49.794: INFO: Jan 25 14:43:51.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:51.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:51.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:51.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Jan 25 14:43:51.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:51.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:51.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:51.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:51.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:51.802: INFO: Jan 25 14:43:53.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:53.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:53.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:53.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Jan 25 14:43:53.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:53.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:53.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:53.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:53.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:53.797: INFO: Jan 25 14:43:55.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:55.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:55.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:55.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Jan 25 14:43:55.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:55.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:55.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:55.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:55.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:55.798: INFO: Jan 25 14:43:57.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:57.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:57.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:57.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Jan 25 14:43:57.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:57.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:57.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:57.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:57.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:57.796: INFO: Jan 25 14:43:59.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:59.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:59.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:43:59.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Jan 25 14:43:59.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:43:59.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:43:59.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:59.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:59.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:43:59.796: INFO: Jan 25 14:44:01.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:01.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:01.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:01.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Jan 25 14:44:01.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:01.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:01.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:01.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:01.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:01.797: INFO: Jan 25 14:44:03.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:03.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:03.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:03.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Jan 25 14:44:03.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:03.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:03.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:03.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:03.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:03.798: INFO: Jan 25 14:44:05.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:05.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:05.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:05.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Jan 25 14:44:05.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:05.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:05.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:05.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:05.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:05.803: INFO: Jan 25 14:44:07.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:07.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:07.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:07.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Jan 25 14:44:07.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:07.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:07.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:07.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:07.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:07.798: INFO: Jan 25 14:44:09.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:09.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:09.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:09.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Jan 25 14:44:09.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:09.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:09.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:09.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:09.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:09.801: INFO: Jan 25 14:44:11.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:11.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:11.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:11.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Jan 25 14:44:11.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:11.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:11.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:11.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:11.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:11.797: INFO: Jan 25 14:44:13.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:13.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:13.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:13.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Jan 25 14:44:13.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:13.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:13.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:13.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:13.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:13.799: INFO: Jan 25 14:44:15.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:15.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:15.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:15.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Jan 25 14:44:15.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:15.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:15.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:15.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:15.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:15.802: INFO: Jan 25 14:44:17.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:17.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:17.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:17.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Jan 25 14:44:17.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:17.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:17.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:17.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:17.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:17.801: INFO: Jan 25 14:44:19.824: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:19.824: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:19.824: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:19.824: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Jan 25 14:44:19.824: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:19.824: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:19.824: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:19.824: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:19.824: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:19.824: INFO: Jan 25 14:44:21.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:21.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:21.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:21.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Jan 25 14:44:21.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:21.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:21.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:21.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:21.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:21.806: INFO: Jan 25 14:44:23.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:23.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:23.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:23.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Jan 25 14:44:23.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:23.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:23.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:23.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:23.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:23.801: INFO: Jan 25 14:44:25.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:25.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:25.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:25.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Jan 25 14:44:25.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:25.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:25.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:25.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:25.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:25.796: INFO: Jan 25 14:44:27.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:27.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:27.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:27.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Jan 25 14:44:27.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:27.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:27.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:27.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:27.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:27.799: INFO: Jan 25 14:44:29.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:29.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:29.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:29.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Jan 25 14:44:29.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:29.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:29.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:29.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:29.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:29.799: INFO: Jan 25 14:44:31.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:31.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:31.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:31.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Jan 25 14:44:31.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:31.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:31.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:31.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:31.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:31.796: INFO: Jan 25 14:44:33.814: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:33.814: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:33.814: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:33.814: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Jan 25 14:44:33.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:33.814: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:33.814: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:33.814: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:33.814: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:33.814: INFO: Jan 25 14:44:35.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:35.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:35.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:35.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Jan 25 14:44:35.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:35.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:35.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:35.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:35.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:35.796: INFO: Jan 25 14:44:37.811: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:37.811: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:37.811: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:37.811: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Jan 25 14:44:37.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:37.811: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:37.811: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:37.811: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:37.811: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:37.811: INFO: Jan 25 14:44:39.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:39.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:39.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:39.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Jan 25 14:44:39.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:39.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:39.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:39.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:39.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:39.795: INFO: Jan 25 14:44:41.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:41.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:41.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:41.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Jan 25 14:44:41.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:41.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:41.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:41.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:41.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:41.795: INFO: Jan 25 14:44:43.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:43.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:43.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:43.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Jan 25 14:44:43.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:43.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:43.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:43.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:43.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:43.798: INFO: Jan 25 14:44:45.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:45.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:45.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:45.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Jan 25 14:44:45.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:45.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:45.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:45.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:45.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:45.796: INFO: Jan 25 14:44:47.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:47.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:47.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:47.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Jan 25 14:44:47.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:47.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:47.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:47.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:47.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:47.796: INFO: Jan 25 14:44:49.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:49.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:49.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:49.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Jan 25 14:44:49.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:49.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:49.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:49.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:49.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:49.799: INFO: Jan 25 14:44:51.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:51.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:51.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:51.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Jan 25 14:44:51.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:51.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:51.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:51.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:51.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:51.798: INFO: Jan 25 14:44:53.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:53.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:53.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:53.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Jan 25 14:44:53.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:53.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:53.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:53.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:53.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:53.796: INFO: Jan 25 14:44:55.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:55.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:55.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:55.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Jan 25 14:44:55.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:55.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:55.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:55.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:55.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:55.802: INFO: Jan 25 14:44:57.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:57.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:57.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:57.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Jan 25 14:44:57.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:57.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:57.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:57.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:57.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:57.801: INFO: Jan 25 14:44:59.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:59.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:59.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:44:59.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Jan 25 14:44:59.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:44:59.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:44:59.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:59.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:59.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:44:59.797: INFO: Jan 25 14:45:01.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:01.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:01.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:01.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Jan 25 14:45:01.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:01.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:01.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:01.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:01.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:01.803: INFO: Jan 25 14:45:03.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:03.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:03.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:03.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Jan 25 14:45:03.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:03.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:03.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:03.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:03.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:03.796: INFO: Jan 25 14:45:05.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:05.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:05.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:05.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Jan 25 14:45:05.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:05.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:05.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:05.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:05.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:05.797: INFO: Jan 25 14:45:07.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:07.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:07.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:07.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Jan 25 14:45:07.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:07.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:07.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:07.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:07.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:07.797: INFO: Jan 25 14:45:09.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:09.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:09.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:09.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Jan 25 14:45:09.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:09.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:09.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:09.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:09.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:09.802: INFO: Jan 25 14:45:11.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:11.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:11.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:11.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Jan 25 14:45:11.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:11.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:11.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:11.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:11.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:11.796: INFO: Jan 25 14:45:13.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:13.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:13.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:13.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Jan 25 14:45:13.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:13.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:13.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:13.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:13.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:13.802: INFO: Jan 25 14:45:15.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:15.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:15.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:15.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Jan 25 14:45:15.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:15.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:15.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:15.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:15.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:15.798: INFO: Jan 25 14:45:17.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:17.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:17.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:17.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Jan 25 14:45:17.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:17.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:17.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:17.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:17.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:17.797: INFO: Jan 25 14:45:19.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:19.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:19.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:19.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Jan 25 14:45:19.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:19.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:19.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:19.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:19.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:19.805: INFO: Jan 25 14:45:21.810: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:21.810: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:21.810: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:21.810: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Jan 25 14:45:21.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:21.810: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:21.810: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:21.810: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:21.810: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:21.810: INFO: Jan 25 14:45:23.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:23.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:23.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:23.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Jan 25 14:45:23.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:23.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:23.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:23.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:23.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:23.796: INFO: Jan 25 14:45:25.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:25.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:25.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:25.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Jan 25 14:45:25.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:25.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:25.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:25.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:25.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:25.797: INFO: Jan 25 14:45:27.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:27.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:27.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:27.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Jan 25 14:45:27.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:27.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:27.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:27.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:27.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:27.796: INFO: Jan 25 14:45:29.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:29.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:29.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:29.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Jan 25 14:45:29.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:29.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:29.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:29.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:29.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:29.796: INFO: Jan 25 14:45:31.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:31.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:31.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:31.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Jan 25 14:45:31.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:31.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:31.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:31.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:31.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:31.796: INFO: Jan 25 14:45:33.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:33.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:33.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:33.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Jan 25 14:45:33.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:33.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:33.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:33.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:33.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:33.796: INFO: Jan 25 14:45:35.812: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:35.812: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:35.812: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:35.812: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Jan 25 14:45:35.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:35.812: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:35.812: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:35.812: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:35.812: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:35.812: INFO: Jan 25 14:45:37.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:37.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:37.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:37.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Jan 25 14:45:37.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:37.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:37.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:37.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:37.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:37.801: INFO: Jan 25 14:45:39.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:39.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:39.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:39.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Jan 25 14:45:39.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:39.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:39.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:39.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:39.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:39.799: INFO: Jan 25 14:45:41.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:41.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:41.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:41.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Jan 25 14:45:41.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:41.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:41.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:41.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:41.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:41.805: INFO: Jan 25 14:45:43.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:43.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:43.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:43.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Jan 25 14:45:43.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:43.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:43.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:43.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:43.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:43.796: INFO: Jan 25 14:45:45.807: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:45.807: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:45.807: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:45.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Jan 25 14:45:45.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:45.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:45.807: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:45.807: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:45.807: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:45.807: INFO: Jan 25 14:45:47.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:47.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:47.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:47.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Jan 25 14:45:47.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:47.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:47.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:47.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:47.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:47.796: INFO: Jan 25 14:45:49.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:49.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:49.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:49.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Jan 25 14:45:49.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:49.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:49.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:49.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:49.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:49.798: INFO: Jan 25 14:45:51.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:51.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:51.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:51.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Jan 25 14:45:51.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:51.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:51.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:51.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:51.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:51.796: INFO: Jan 25 14:45:53.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:53.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:53.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:53.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Jan 25 14:45:53.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:53.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:53.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:53.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:53.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:53.796: INFO: Jan 25 14:45:55.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:55.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:55.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:55.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Jan 25 14:45:55.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:55.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:55.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:55.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:55.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:55.797: INFO: Jan 25 14:45:57.814: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:57.814: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:57.814: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:57.814: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Jan 25 14:45:57.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:57.814: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:57.814: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:57.814: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:57.814: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:57.814: INFO: Jan 25 14:45:59.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:59.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:59.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:45:59.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Jan 25 14:45:59.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:45:59.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:45:59.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:59.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:59.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:45:59.798: INFO: Jan 25 14:46:01.817: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:01.817: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:01.817: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:01.817: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Jan 25 14:46:01.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:01.817: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:01.817: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:01.817: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:01.817: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:01.817: INFO: Jan 25 14:46:03.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:03.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:03.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:03.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Jan 25 14:46:03.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:03.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:03.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:03.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:03.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:03.796: INFO: Jan 25 14:46:05.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:05.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:05.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:05.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Jan 25 14:46:05.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:05.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:05.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:05.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:05.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:05.798: INFO: Jan 25 14:46:07.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:07.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:07.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:07.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Jan 25 14:46:07.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:07.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:07.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:07.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:07.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:07.799: INFO: Jan 25 14:46:09.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:09.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:09.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:09.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Jan 25 14:46:09.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:09.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:09.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:09.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:09.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:09.797: INFO: Jan 25 14:46:11.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:11.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:11.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:11.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Jan 25 14:46:11.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:11.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:11.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:11.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:11.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:11.798: INFO: Jan 25 14:46:13.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:13.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:13.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:13.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Jan 25 14:46:13.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:13.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:13.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:13.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:13.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:13.799: INFO: Jan 25 14:46:15.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:15.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:15.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:15.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Jan 25 14:46:15.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:15.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:15.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:15.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:15.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:15.798: INFO: Jan 25 14:46:17.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:17.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:17.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:17.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Jan 25 14:46:17.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:17.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:17.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:17.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:17.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:17.796: INFO: Jan 25 14:46:19.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:19.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:19.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:19.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Jan 25 14:46:19.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:19.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:19.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:19.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:19.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:19.804: INFO: Jan 25 14:46:21.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:21.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:21.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:21.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Jan 25 14:46:21.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:21.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:21.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:21.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:21.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:21.795: INFO: Jan 25 14:46:23.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:23.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:23.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:23.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Jan 25 14:46:23.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:23.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:23.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:23.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:23.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:23.799: INFO: Jan 25 14:46:25.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:25.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:25.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:25.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Jan 25 14:46:25.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:25.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:25.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:25.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:25.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:25.801: INFO: Jan 25 14:46:27.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:27.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:27.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:27.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Jan 25 14:46:27.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:27.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:27.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:27.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:27.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:27.797: INFO: Jan 25 14:46:29.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:29.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:29.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:29.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Jan 25 14:46:29.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:29.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:29.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:29.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:29.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:29.799: INFO: Jan 25 14:46:31.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:31.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:31.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:31.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Jan 25 14:46:31.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:31.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:31.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:31.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:31.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:31.804: INFO: Jan 25 14:46:33.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:33.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:33.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:33.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Jan 25 14:46:33.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:33.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:33.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:33.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:33.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:33.796: INFO: Jan 25 14:46:35.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:35.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:35.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:35.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Jan 25 14:46:35.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:35.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:35.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:35.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:35.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:35.796: INFO: Jan 25 14:46:37.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:37.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:37.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:37.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Jan 25 14:46:37.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:37.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:37.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:37.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:37.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:37.798: INFO: Jan 25 14:46:39.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:39.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:39.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:39.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Jan 25 14:46:39.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:39.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:39.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:39.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:39.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:39.797: INFO: Jan 25 14:46:41.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:41.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:41.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:41.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Jan 25 14:46:41.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:41.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:41.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:41.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:41.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:41.798: INFO: Jan 25 14:46:43.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:43.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:43.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:43.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Jan 25 14:46:43.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:43.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:43.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:43.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:43.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:43.802: INFO: Jan 25 14:46:45.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:45.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:45.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:45.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Jan 25 14:46:45.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:45.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:45.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:45.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:45.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:45.809: INFO: Jan 25 14:46:47.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:47.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:47.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:47.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Jan 25 14:46:47.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:47.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:47.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:47.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:47.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:47.795: INFO: Jan 25 14:46:49.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:49.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:49.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:49.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Jan 25 14:46:49.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:49.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:49.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:49.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:49.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:49.799: INFO: Jan 25 14:46:51.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:51.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:51.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:51.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Jan 25 14:46:51.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:51.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:51.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:51.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:51.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:51.796: INFO: Jan 25 14:46:53.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:53.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:53.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:53.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Jan 25 14:46:53.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:53.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:53.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:53.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:53.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:53.796: INFO: Jan 25 14:46:55.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:55.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:55.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:55.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Jan 25 14:46:55.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:55.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:55.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:55.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:55.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:55.798: INFO: Jan 25 14:46:57.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:57.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:57.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:57.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Jan 25 14:46:57.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:57.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:57.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:57.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:57.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:57.802: INFO: Jan 25 14:46:59.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:59.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:59.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:46:59.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Jan 25 14:46:59.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:46:59.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:46:59.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:59.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:59.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:46:59.799: INFO: Jan 25 14:47:01.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:01.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:01.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:01.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Jan 25 14:47:01.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:01.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:01.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:01.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:01.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:01.795: INFO: Jan 25 14:47:03.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:03.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:03.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:03.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Jan 25 14:47:03.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:03.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:03.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:03.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:03.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:03.804: INFO: Jan 25 14:47:05.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:05.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:05.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:05.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Jan 25 14:47:05.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:05.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:05.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:05.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:05.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:05.798: INFO: Jan 25 14:47:07.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:07.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:07.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:07.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Jan 25 14:47:07.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:07.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:07.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:07.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:07.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:07.796: INFO: Jan 25 14:47:09.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:09.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:09.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:09.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Jan 25 14:47:09.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:09.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:09.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:09.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:09.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:09.799: INFO: Jan 25 14:47:11.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:11.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:11.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:11.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Jan 25 14:47:11.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:11.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:11.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:11.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:11.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:11.796: INFO: Jan 25 14:47:13.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:13.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:13.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:13.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Jan 25 14:47:13.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:13.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:13.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:13.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:13.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:13.795: INFO: Jan 25 14:47:15.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:15.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:15.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:15.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Jan 25 14:47:15.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:15.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:15.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:15.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:15.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:15.803: INFO: Jan 25 14:47:17.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:17.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:17.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:17.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Jan 25 14:47:17.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:17.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:17.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:17.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:17.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:17.798: INFO: Jan 25 14:47:19.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:19.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:19.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:19.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Jan 25 14:47:19.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:19.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:19.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:19.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:19.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:19.798: INFO: Jan 25 14:47:21.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:21.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:21.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:21.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Jan 25 14:47:21.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:21.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:21.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:21.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:21.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:21.797: INFO: Jan 25 14:47:23.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:23.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:23.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:23.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Jan 25 14:47:23.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:23.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:23.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:23.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:23.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:23.795: INFO: Jan 25 14:47:25.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:25.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:25.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:25.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Jan 25 14:47:25.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:25.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:25.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:25.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:25.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:25.797: INFO: Jan 25 14:47:27.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:27.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:27.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:27.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Jan 25 14:47:27.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:27.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:27.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:27.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:27.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:27.796: INFO: Jan 25 14:47:29.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:29.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:29.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:29.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Jan 25 14:47:29.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:29.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:29.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:29.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:29.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:29.802: INFO: Jan 25 14:47:31.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:31.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:31.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:31.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Jan 25 14:47:31.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:31.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:31.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:31.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:31.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:31.797: INFO: Jan 25 14:47:33.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:33.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:33.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:33.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Jan 25 14:47:33.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:33.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:33.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:33.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:33.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:33.798: INFO: Jan 25 14:47:35.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:35.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:35.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:35.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Jan 25 14:47:35.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:35.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:35.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:35.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:35.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:35.798: INFO: Jan 25 14:47:37.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:37.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:37.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:37.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Jan 25 14:47:37.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:37.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:37.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:37.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:37.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:37.798: INFO: Jan 25 14:47:39.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:39.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:39.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:39.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Jan 25 14:47:39.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:39.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:39.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:39.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:39.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:39.795: INFO: Jan 25 14:47:41.794: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:41.794: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:41.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:41.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Jan 25 14:47:41.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:41.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:41.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:41.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:41.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:41.795: INFO: Jan 25 14:47:43.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:43.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:43.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:43.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Jan 25 14:47:43.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:43.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:43.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:43.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:43.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:43.796: INFO: Jan 25 14:47:45.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:45.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:45.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:45.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Jan 25 14:47:45.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:45.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:45.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:45.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:45.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:45.797: INFO: Jan 25 14:47:47.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:47.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:47.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:47.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Jan 25 14:47:47.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:47.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:47.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:47.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:47.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:47.800: INFO: Jan 25 14:47:49.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:49.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:49.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:49.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Jan 25 14:47:49.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:49.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:49.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:49.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:49.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:49.799: INFO: Jan 25 14:47:51.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:51.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:51.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:51.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Jan 25 14:47:51.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:51.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:51.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:51.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:51.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:51.797: INFO: Jan 25 14:47:53.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:53.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:53.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:53.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Jan 25 14:47:53.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:53.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:53.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:53.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:53.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:53.806: INFO: Jan 25 14:47:55.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:55.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:55.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:55.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Jan 25 14:47:55.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:55.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:55.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:55.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:55.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:55.797: INFO: Jan 25 14:47:57.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:57.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:57.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:57.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Jan 25 14:47:57.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:57.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:57.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:57.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:57.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:57.797: INFO: Jan 25 14:47:59.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:59.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:59.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:47:59.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Jan 25 14:47:59.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:47:59.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:47:59.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:59.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:59.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:47:59.799: INFO: Jan 25 14:48:01.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:01.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:01.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:01.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Jan 25 14:48:01.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:01.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:01.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:01.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:01.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:01.798: INFO: Jan 25 14:48:03.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:03.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:03.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:03.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Jan 25 14:48:03.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:03.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:03.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:03.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:03.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:03.800: INFO: Jan 25 14:48:05.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:05.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:05.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:05.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Jan 25 14:48:05.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:05.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:05.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:05.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:05.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:05.797: INFO: Jan 25 14:48:07.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:07.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:07.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:07.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Jan 25 14:48:07.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:07.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:07.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:07.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:07.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:07.796: INFO: Jan 25 14:48:09.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:09.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:09.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:09.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Jan 25 14:48:09.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:09.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:09.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:09.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:09.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:09.806: INFO: Jan 25 14:48:11.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:11.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:11.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:11.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Jan 25 14:48:11.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:11.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:11.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:11.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:11.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:11.796: INFO: Jan 25 14:48:13.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:13.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:13.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:13.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Jan 25 14:48:13.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:13.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:13.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:13.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:13.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:13.796: INFO: Jan 25 14:48:15.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:15.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:15.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:15.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Jan 25 14:48:15.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:15.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:15.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:15.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:15.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:15.796: INFO: Jan 25 14:48:17.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:17.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:17.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:17.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Jan 25 14:48:17.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:17.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:17.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:17.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:17.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:17.796: INFO: Jan 25 14:48:19.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:19.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:19.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:19.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Jan 25 14:48:19.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:19.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:19.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:19.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:19.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:19.803: INFO: Jan 25 14:48:21.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:21.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:21.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:21.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Jan 25 14:48:21.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:21.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:21.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:21.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:21.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:21.796: INFO: Jan 25 14:48:23.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:23.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:23.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:23.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Jan 25 14:48:23.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:23.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:23.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:23.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:23.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:23.799: INFO: Jan 25 14:48:25.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:25.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:25.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:25.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Jan 25 14:48:25.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:25.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:25.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:25.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:25.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:25.799: INFO: Jan 25 14:48:27.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:27.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:27.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:27.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Jan 25 14:48:27.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:27.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:27.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:27.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:27.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:27.798: INFO: Jan 25 14:48:29.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:29.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:29.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:29.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Jan 25 14:48:29.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:29.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:29.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:29.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:29.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:29.798: INFO: Jan 25 14:48:31.797: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:31.797: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:31.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:31.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Jan 25 14:48:31.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:31.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:31.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:31.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:31.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:31.798: INFO: Jan 25 14:48:33.795: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:33.795: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:33.795: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:33.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Jan 25 14:48:33.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:33.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:33.795: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:33.795: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:33.795: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:33.795: INFO: Jan 25 14:48:35.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:35.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:35.797: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:35.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Jan 25 14:48:35.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:35.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:35.797: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:35.797: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:35.797: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:35.797: INFO: Jan 25 14:48:37.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:37.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:37.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:37.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Jan 25 14:48:37.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:37.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:37.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:37.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:37.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:37.799: INFO: Jan 25 14:48:39.798: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:39.798: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:39.798: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:39.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Jan 25 14:48:39.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:39.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:39.798: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:39.798: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:39.798: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:39.798: INFO: Jan 25 14:48:41.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:41.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:41.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:41.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Jan 25 14:48:41.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:41.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:41.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:41.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:41.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:41.796: INFO: Jan 25 14:48:43.796: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:43.796: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:43.796: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:43.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Jan 25 14:48:43.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:43.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:43.796: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:43.796: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:43.796: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:43.796: INFO: Jan 25 14:48:45.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:45.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:45.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:45.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Jan 25 14:48:45.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:45.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:45.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:45.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:45.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:45.799: INFO: Jan 25 14:48:47.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:47.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:47.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:47.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Jan 25 14:48:47.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:47.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:47.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:47.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:47.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:47.799: INFO: Jan 25 14:48:49.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:49.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:49.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:49.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Jan 25 14:48:49.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:49.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:49.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:49.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:49.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:49.799: INFO: Jan 25 14:48:51.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:51.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:51.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:51.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Jan 25 14:48:51.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:51.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:51.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:51.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:51.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:51.800: INFO: Jan 25 14:48:53.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:53.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:53.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:53.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Jan 25 14:48:53.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:53.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:53.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:53.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:53.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:53.802: INFO: Jan 25 14:48:55.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:55.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:55.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:55.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Jan 25 14:48:55.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:55.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:55.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:55.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:55.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:55.809: INFO: Jan 25 14:48:57.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:57.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:57.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:57.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Jan 25 14:48:57.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:57.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:57.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:57.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:57.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:57.802: INFO: Jan 25 14:48:59.800: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:59.800: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:59.800: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:48:59.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Jan 25 14:48:59.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:48:59.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:48:59.800: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:59.800: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:59.800: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:48:59.800: INFO: Jan 25 14:49:01.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:01.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:01.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:01.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Jan 25 14:49:01.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:01.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:01.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:01.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:01.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:01.802: INFO: Jan 25 14:49:03.799: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:03.799: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:03.799: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:03.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Jan 25 14:49:03.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:03.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:03.799: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:03.799: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:03.799: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:03.799: INFO: Jan 25 14:49:05.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:05.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:05.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:05.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Jan 25 14:49:05.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:05.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:05.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:05.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:05.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:05.803: INFO: Jan 25 14:49:07.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:07.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:07.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:07.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Jan 25 14:49:07.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:07.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:07.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:07.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:07.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:07.801: INFO: Jan 25 14:49:09.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:09.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:09.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:09.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Jan 25 14:49:09.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:09.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:09.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:09.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:09.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:09.805: INFO: Jan 25 14:49:11.808: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:11.808: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:11.808: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:11.808: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Jan 25 14:49:11.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:11.808: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:11.808: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:11.808: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:11.808: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:11.808: INFO: Jan 25 14:49:13.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:13.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:13.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:13.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Jan 25 14:49:13.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:13.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:13.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:13.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:13.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:13.806: INFO: Jan 25 14:49:15.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:15.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:15.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:15.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Jan 25 14:49:15.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:15.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:15.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:15.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:15.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:15.806: INFO: Jan 25 14:49:17.807: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:17.807: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:17.807: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:17.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Jan 25 14:49:17.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:17.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:17.807: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:17.807: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:17.807: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:17.807: INFO: Jan 25 14:49:19.811: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:19.811: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:19.811: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:19.811: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Jan 25 14:49:19.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:19.811: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:19.811: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:19.811: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:19.811: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:19.811: INFO: Jan 25 14:49:21.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:21.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:21.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:21.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Jan 25 14:49:21.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:21.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:21.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:21.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:21.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:21.804: INFO: Jan 25 14:49:23.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:23.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:23.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:23.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Jan 25 14:49:23.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:23.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:23.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:23.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:23.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:23.803: INFO: Jan 25 14:49:25.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:25.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:25.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:25.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Jan 25 14:49:25.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:25.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:25.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:25.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:25.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:25.806: INFO: Jan 25 14:49:27.807: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:27.807: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:27.807: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:27.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Jan 25 14:49:27.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:27.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:27.807: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:27.807: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:27.807: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:27.807: INFO: Jan 25 14:49:29.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:29.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:29.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:29.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Jan 25 14:49:29.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:29.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:29.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:29.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:29.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:29.805: INFO: Jan 25 14:49:31.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:31.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:31.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:31.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Jan 25 14:49:31.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:31.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:31.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:31.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:31.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:31.806: INFO: Jan 25 14:49:33.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:33.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:33.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:33.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Jan 25 14:49:33.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:33.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:33.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:33.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:33.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:33.804: INFO: Jan 25 14:49:35.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:35.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:35.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:35.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Jan 25 14:49:35.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:35.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:35.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:35.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:35.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:35.804: INFO: Jan 25 14:49:37.822: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:37.822: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:37.822: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:37.822: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Jan 25 14:49:37.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:37.822: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:37.822: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:37.822: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:37.822: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:37.822: INFO: Jan 25 14:49:39.808: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:39.808: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:39.808: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:39.808: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Jan 25 14:49:39.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:39.808: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:39.808: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:39.808: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:39.808: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:39.808: INFO: Jan 25 14:49:41.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:41.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:41.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:41.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Jan 25 14:49:41.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:41.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:41.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:41.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:41.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:41.804: INFO: Jan 25 14:49:43.807: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:43.807: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:43.807: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:43.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Jan 25 14:49:43.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:43.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:43.807: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:43.807: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:43.807: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:43.807: INFO: Jan 25 14:49:45.810: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:45.810: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:45.810: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:45.810: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Jan 25 14:49:45.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:45.810: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:45.810: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:45.810: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:45.810: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:45.810: INFO: Jan 25 14:49:47.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:47.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:47.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:47.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Jan 25 14:49:47.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:47.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:47.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:47.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:47.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:47.805: INFO: Jan 25 14:49:49.807: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:49.807: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:49.807: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:49.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Jan 25 14:49:49.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:49.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:49.807: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:49.807: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:49.807: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:49.807: INFO: Jan 25 14:49:51.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:51.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:51.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:51.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Jan 25 14:49:51.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:51.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:51.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:51.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:51.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:51.803: INFO: Jan 25 14:49:53.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:53.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:53.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:53.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Jan 25 14:49:53.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:53.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:53.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:53.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:53.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:53.805: INFO: Jan 25 14:49:55.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:55.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:55.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:55.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Jan 25 14:49:55.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:55.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:55.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:55.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:55.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:55.804: INFO: Jan 25 14:49:57.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:57.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:57.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:57.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Jan 25 14:49:57.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:57.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:57.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:57.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:57.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:57.804: INFO: Jan 25 14:49:59.810: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:59.810: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:59.810: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:49:59.810: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Jan 25 14:49:59.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:49:59.810: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:49:59.810: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:59.810: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:59.810: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:49:59.810: INFO: Jan 25 14:50:01.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:01.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:01.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:01.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Jan 25 14:50:01.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:01.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:01.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:01.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:01.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:01.804: INFO: Jan 25 14:50:03.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:03.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:03.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:03.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Jan 25 14:50:03.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:03.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:03.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:03.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:03.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:03.806: INFO: Jan 25 14:50:05.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:05.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:05.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:05.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Jan 25 14:50:05.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:05.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:05.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:05.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:05.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:05.809: INFO: Jan 25 14:50:07.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:07.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:07.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:07.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Jan 25 14:50:07.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:07.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:07.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:07.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:07.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:07.805: INFO: Jan 25 14:50:09.820: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:09.820: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:09.820: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:09.820: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Jan 25 14:50:09.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:09.820: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:09.820: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:09.820: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:09.820: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:09.820: INFO: Jan 25 14:50:11.824: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:11.824: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:11.824: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:11.824: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Jan 25 14:50:11.824: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:11.824: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:11.824: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:11.824: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:11.824: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:11.824: INFO: Jan 25 14:50:13.818: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:13.818: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:13.818: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:13.818: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Jan 25 14:50:13.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:13.818: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:13.818: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:13.818: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:13.818: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:13.818: INFO: Jan 25 14:50:15.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:15.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:15.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:15.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Jan 25 14:50:15.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:15.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:15.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:15.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:15.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:15.803: INFO: Jan 25 14:50:17.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:17.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:17.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:17.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Jan 25 14:50:17.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:17.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:17.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:17.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:17.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:17.805: INFO: Jan 25 14:50:19.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:19.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:19.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:19.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Jan 25 14:50:19.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:19.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:19.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:19.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:19.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:19.803: INFO: Jan 25 14:50:21.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:21.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:21.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:21.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Jan 25 14:50:21.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:21.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:21.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:21.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:21.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:21.802: INFO: Jan 25 14:50:23.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:23.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:23.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:23.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Jan 25 14:50:23.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:23.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:23.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:23.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:23.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:23.805: INFO: Jan 25 14:50:25.808: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:25.808: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:25.808: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:25.808: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Jan 25 14:50:25.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:25.808: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:25.808: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:25.808: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:25.808: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:25.808: INFO: Jan 25 14:50:27.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:27.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:27.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:27.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Jan 25 14:50:27.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:27.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:27.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:27.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:27.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:27.802: INFO: Jan 25 14:50:29.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:29.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:29.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:29.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Jan 25 14:50:29.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:29.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:29.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:29.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:29.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:29.806: INFO: Jan 25 14:50:31.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:31.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:31.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:31.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Jan 25 14:50:31.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:31.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:31.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:31.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:31.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:31.804: INFO: Jan 25 14:50:33.808: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:33.808: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:33.808: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:33.808: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Jan 25 14:50:33.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:33.808: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:33.808: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:33.808: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:33.808: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:33.808: INFO: Jan 25 14:50:35.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:35.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:35.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:35.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Jan 25 14:50:35.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:35.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:35.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:35.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:35.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:35.802: INFO: Jan 25 14:50:37.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:37.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:37.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:37.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Jan 25 14:50:37.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:37.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:37.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:37.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:37.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:37.806: INFO: Jan 25 14:50:39.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:39.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:39.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:39.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Jan 25 14:50:39.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:39.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:39.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:39.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:39.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:39.804: INFO: Jan 25 14:50:41.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:41.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:41.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:41.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Jan 25 14:50:41.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:41.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:41.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:41.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:41.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:41.809: INFO: Jan 25 14:50:43.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:43.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:43.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:43.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Jan 25 14:50:43.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:43.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:43.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:43.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:43.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:43.809: INFO: Jan 25 14:50:45.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:45.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:45.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:45.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Jan 25 14:50:45.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:45.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:45.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:45.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:45.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:45.804: INFO: Jan 25 14:50:47.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:47.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:47.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:47.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Jan 25 14:50:47.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:47.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:47.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:47.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:47.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:47.805: INFO: Jan 25 14:50:49.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:49.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:49.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:49.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Jan 25 14:50:49.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:49.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:49.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:49.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:49.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:49.805: INFO: Jan 25 14:50:51.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:51.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:51.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:51.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Jan 25 14:50:51.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:51.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:51.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:51.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:51.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:51.802: INFO: Jan 25 14:50:53.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:53.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:53.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:53.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Jan 25 14:50:53.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:53.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:53.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:53.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:53.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:53.803: INFO: Jan 25 14:50:55.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:55.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:55.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:55.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Jan 25 14:50:55.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:55.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:55.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:55.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:55.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:55.802: INFO: Jan 25 14:50:57.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:57.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:57.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:57.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Jan 25 14:50:57.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:57.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:57.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:57.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:57.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:57.803: INFO: Jan 25 14:50:59.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:59.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:59.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:50:59.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Jan 25 14:50:59.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:50:59.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:50:59.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:59.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:59.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:50:59.806: INFO: Jan 25 14:51:01.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:01.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:01.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:01.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Jan 25 14:51:01.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:01.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:01.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:01.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:01.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:01.801: INFO: Jan 25 14:51:03.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:03.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:03.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:03.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Jan 25 14:51:03.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:03.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:03.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:03.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:03.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:03.805: INFO: Jan 25 14:51:05.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:05.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:05.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:05.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Jan 25 14:51:05.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:05.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:05.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:05.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:05.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:05.802: INFO: Jan 25 14:51:07.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:07.801: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:07.801: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:07.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Jan 25 14:51:07.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:07.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:07.801: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:07.801: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:07.801: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:07.801: INFO: Jan 25 14:51:09.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:09.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:09.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:09.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Jan 25 14:51:09.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:09.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:09.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:09.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:09.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:09.806: INFO: Jan 25 14:51:11.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:11.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:11.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:11.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Jan 25 14:51:11.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:11.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:11.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:11.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:11.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:11.805: INFO: Jan 25 14:51:13.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:13.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:13.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:13.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Jan 25 14:51:13.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:13.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:13.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:13.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:13.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:13.806: INFO: Jan 25 14:51:15.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:15.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:15.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:15.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Jan 25 14:51:15.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:15.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:15.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:15.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:15.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:15.802: INFO: Jan 25 14:51:17.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:17.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:17.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:17.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Jan 25 14:51:17.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:17.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:17.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:17.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:17.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:17.803: INFO: Jan 25 14:51:19.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:19.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:19.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:19.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Jan 25 14:51:19.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:19.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:19.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:19.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:19.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:19.806: INFO: Jan 25 14:51:21.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:21.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:21.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:21.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Jan 25 14:51:21.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:21.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:21.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:21.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:21.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:21.806: INFO: Jan 25 14:51:23.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:23.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:23.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:23.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Jan 25 14:51:23.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:23.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:23.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:23.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:23.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:23.802: INFO: Jan 25 14:51:25.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:25.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:25.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:25.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Jan 25 14:51:25.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:25.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:25.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:25.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:25.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:25.805: INFO: Jan 25 14:51:27.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:27.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:27.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:27.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Jan 25 14:51:27.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:27.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:27.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:27.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:27.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:27.805: INFO: Jan 25 14:51:29.810: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:29.810: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:29.810: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:29.810: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Jan 25 14:51:29.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:29.810: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:29.810: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:29.810: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:29.810: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:29.810: INFO: Jan 25 14:51:31.801: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:31.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:31.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:31.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Jan 25 14:51:31.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:31.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:31.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:31.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:31.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:31.802: INFO: Jan 25 14:51:33.808: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:33.808: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:33.808: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:33.808: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Jan 25 14:51:33.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:33.808: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:33.808: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:33.808: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:33.808: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:33.808: INFO: Jan 25 14:51:35.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:35.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:35.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:35.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Jan 25 14:51:35.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:35.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:35.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:35.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:35.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:35.806: INFO: Jan 25 14:51:37.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:37.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:37.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:37.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Jan 25 14:51:37.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:37.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:37.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:37.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:37.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:37.805: INFO: Jan 25 14:51:39.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:39.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:39.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:39.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Jan 25 14:51:39.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:39.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:39.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:39.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:39.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:39.809: INFO: Jan 25 14:51:41.804: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:41.804: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:41.804: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:41.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Jan 25 14:51:41.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:41.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:41.804: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:41.804: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:41.804: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:41.804: INFO: Jan 25 14:51:43.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:43.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:43.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:43.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Jan 25 14:51:43.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:43.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:43.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:43.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:43.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:43.809: INFO: Jan 25 14:51:45.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:45.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:45.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:45.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Jan 25 14:51:45.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:45.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:45.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:45.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:45.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:45.805: INFO: Jan 25 14:51:47.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:47.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:47.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:47.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Jan 25 14:51:47.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:47.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:47.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:47.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:47.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:47.802: INFO: Jan 25 14:51:49.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:49.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:49.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:49.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Jan 25 14:51:49.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:49.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:49.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:49.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:49.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:49.809: INFO: Jan 25 14:51:51.809: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:51.809: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:51.809: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:51.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Jan 25 14:51:51.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:51.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:51.809: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:51.809: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:51.809: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:51.809: INFO: Jan 25 14:51:53.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:53.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:53.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:53.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Jan 25 14:51:53.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:53.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:53.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:53.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:53.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:53.805: INFO: Jan 25 14:51:55.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:55.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:55.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:55.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Jan 25 14:51:55.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:55.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:55.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:55.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:55.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:55.803: INFO: Jan 25 14:51:57.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:57.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:57.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:57.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Jan 25 14:51:57.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:57.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:57.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:57.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:57.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:57.803: INFO: Jan 25 14:51:59.802: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:59.802: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:59.802: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:51:59.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Jan 25 14:51:59.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:51:59.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:51:59.802: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:59.802: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:59.802: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:51:59.802: INFO: Jan 25 14:52:01.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:01.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:01.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:01.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Jan 25 14:52:01.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:52:01.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:52:01.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:01.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:01.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:01.805: INFO: Jan 25 14:52:03.806: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:03.806: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:03.806: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:03.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Jan 25 14:52:03.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:52:03.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:52:03.806: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:03.806: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:03.806: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:03.806: INFO: Jan 25 14:52:05.805: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:05.805: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:05.805: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:05.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Jan 25 14:52:05.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:52:05.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:52:05.805: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:05.805: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:05.805: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:05.805: INFO: Jan 25 14:52:07.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:07.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:07.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:07.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Jan 25 14:52:07.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:52:07.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:52:07.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:07.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:07.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:07.803: INFO: Jan 25 14:52:09.803: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:09.803: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:09.803: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:09.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 25 14:52:09.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:52:09.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:52:09.803: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:09.803: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:09.803: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:09.803: INFO: Jan 25 14:52:10.237: INFO: The status of Pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:10.237: INFO: The status of Pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:10.237: INFO: The status of Pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 25 14:52:10.237: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (601 seconds elapsed) Jan 25 14:52:10.237: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 25 14:52:10.237: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:52:10.237: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:10.237: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:10.237: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:10.237: INFO: STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/25/23 14:52:10.237 STEP: Found 106 events. - test/e2e/framework/debug/dump.go:46 @ 01/25/23 14:52:10.395 Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:36 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-r52y03-control-plane-gxlsw_54ad4ba2-1f9b-4c33-8b90-b062b114725a became leader Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:37 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-r52y03-control-plane-gxlsw_a58d5023-b6ea-4bc4-9b95-147aa4d14b53 became leader Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:46 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2 Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:46 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-xvf2w Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:46 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-tp9hd Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:46 +0000 UTC - event for coredns-56f4c55bf9-tp9hd: {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 25 14:52:10.395: INFO: At 2023-01-25 14:39:46 +0000 UTC - event for coredns-56f4c55bf9-xvf2w: {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 25 14:52:10.395: INFO: At 2023-01-25 14:39:46 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-85n2k Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:46 +0000 UTC - event for kube-proxy-85n2k: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-85n2k to capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:47 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-85n2k Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:48 +0000 UTC - event for kube-proxy-85n2k: {kubelet capz-conf-r52y03-control-plane-gxlsw} FailedMount: MountVolume.SetUp failed for volume "kube-api-access-drdb5" : object "kube-system"/"kube-root-ca.crt" not registered Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:48 +0000 UTC - event for kube-proxy-85n2k: {kubelet capz-conf-r52y03-control-plane-gxlsw} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : object "kube-system"/"kube-proxy" not registered Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:50 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-kz6w8 Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:50 +0000 UTC - event for kube-proxy-kz6w8: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-kz6w8 to capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:51 +0000 UTC - event for kube-proxy-kz6w8: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca" Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:56 +0000 UTC - event for kube-proxy-kz6w8: {kubelet capz-conf-r52y03-control-plane-gxlsw} Created: Created container kube-proxy Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:56 +0000 UTC - event for kube-proxy-kz6w8: {kubelet capz-conf-r52y03-control-plane-gxlsw} Started: Started container kube-proxy Jan 25 14:52:10.395: INFO: At 2023-01-25 14:39:56 +0000 UTC - event for kube-proxy-kz6w8: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca" in 4.305715272s (4.305737071s including waiting) Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:08 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:08 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-gwh9p Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:08 +0000 UTC - event for metrics-server-c9574f845-gwh9p: {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 25 14:52:10.395: INFO: At 2023-01-25 14:40:11 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1 Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:11 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-fxltc Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:11 +0000 UTC - event for calico-kube-controllers-657b584867-fxltc: {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 25 14:52:10.395: INFO: At 2023-01-25 14:40:11 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-xkzqk Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:11 +0000 UTC - event for calico-node-xkzqk: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-xkzqk to capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:12 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:20 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 8.270071252s (8.270079052s including waiting) Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:20 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Started: Started container upgrade-ipam Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:20 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Created: Created container upgrade-ipam Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:23 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:23 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Started: Started container install-cni Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:23 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Created: Created container install-cni Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:25 +0000 UTC - event for calico-kube-controllers-657b584867-fxltc: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-fxltc to capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:25 +0000 UTC - event for coredns-56f4c55bf9-tp9hd: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-tp9hd to capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:25 +0000 UTC - event for coredns-56f4c55bf9-xvf2w: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-xvf2w to capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:25 +0000 UTC - event for metrics-server-c9574f845-gwh9p: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-gwh9p to capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:26 +0000 UTC - event for calico-kube-controllers-657b584867-fxltc: {kubelet capz-conf-r52y03-control-plane-gxlsw} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "daae7312ee493cacd5d89e7e4ff48be590571556916ef018b0b19748145d98a0": 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 25 14:52:10.395: INFO: At 2023-01-25 14:40:26 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:26 +0000 UTC - event for coredns-56f4c55bf9-tp9hd: {kubelet capz-conf-r52y03-control-plane-gxlsw} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "fa82a6695099828a5ec4091742662f64dd4cd54894bef96e086544934635ee5f": 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 25 14:52:10.395: INFO: At 2023-01-25 14:40:26 +0000 UTC - event for coredns-56f4c55bf9-xvf2w: {kubelet capz-conf-r52y03-control-plane-gxlsw} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "16b5aeb9e69685d98a68bda88225346e907ed3df8501e0019dc8afc4499a20f8": 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 25 14:52:10.395: INFO: At 2023-01-25 14:40:26 +0000 UTC - event for metrics-server-c9574f845-gwh9p: {kubelet capz-conf-r52y03-control-plane-gxlsw} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "b42e49814f5ffeb947eea6966d5e5a71f8064f6a1e91d7604d6f9c49abc252d0": 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 25 14:52:10.395: INFO: At 2023-01-25 14:40:27 +0000 UTC - event for calico-kube-controllers-657b584867-fxltc: {kubelet capz-conf-r52y03-control-plane-gxlsw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:27 +0000 UTC - event for coredns-56f4c55bf9-tp9hd: {kubelet capz-conf-r52y03-control-plane-gxlsw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:27 +0000 UTC - event for coredns-56f4c55bf9-xvf2w: {kubelet capz-conf-r52y03-control-plane-gxlsw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:27 +0000 UTC - event for metrics-server-c9574f845-gwh9p: {kubelet capz-conf-r52y03-control-plane-gxlsw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 25 14:52:10.395: INFO: At 2023-01-25 14:40:36 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.953419862s (9.953434363s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:36 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Created: Created container calico-node Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:36 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Started: Started container calico-node Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:37 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} 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 25 14:52:10.396: INFO: At 2023-01-25 14:40:38 +0000 UTC - event for calico-node-xkzqk: {kubelet capz-conf-r52y03-control-plane-gxlsw} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:39 +0000 UTC - event for coredns-56f4c55bf9-tp9hd: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:39 +0000 UTC - event for coredns-56f4c55bf9-tp9hd: {kubelet capz-conf-r52y03-control-plane-gxlsw} Created: Created container coredns Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:39 +0000 UTC - event for coredns-56f4c55bf9-tp9hd: {kubelet capz-conf-r52y03-control-plane-gxlsw} Started: Started container coredns Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:41 +0000 UTC - event for metrics-server-c9574f845-gwh9p: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:43 +0000 UTC - event for calico-kube-controllers-657b584867-fxltc: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0" Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:44 +0000 UTC - event for coredns-56f4c55bf9-xvf2w: {kubelet capz-conf-r52y03-control-plane-gxlsw} Started: Started container coredns Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:44 +0000 UTC - event for coredns-56f4c55bf9-xvf2w: {kubelet capz-conf-r52y03-control-plane-gxlsw} Created: Created container coredns Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:44 +0000 UTC - event for coredns-56f4c55bf9-xvf2w: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:47 +0000 UTC - event for metrics-server-c9574f845-gwh9p: {kubelet capz-conf-r52y03-control-plane-gxlsw} Created: Created container metrics-server Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:47 +0000 UTC - event for metrics-server-c9574f845-gwh9p: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 6.250625036s (6.250762432s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:48 +0000 UTC - event for metrics-server-c9574f845-gwh9p: {kubelet capz-conf-r52y03-control-plane-gxlsw} Started: Started container metrics-server Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:54 +0000 UTC - event for calico-kube-controllers-657b584867-fxltc: {kubelet capz-conf-r52y03-control-plane-gxlsw} Started: Started container calico-kube-controllers Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:54 +0000 UTC - event for calico-kube-controllers-657b584867-fxltc: {kubelet capz-conf-r52y03-control-plane-gxlsw} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 7.045090487s (10.785699795s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:40:54 +0000 UTC - event for calico-kube-controllers-657b584867-fxltc: {kubelet capz-conf-r52y03-control-plane-gxlsw} Created: Created container calico-kube-controllers Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:36 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-4cp9p Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:36 +0000 UTC - event for calico-node-4cp9p: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-4cp9p to capz-conf-r52y03-md-0-hb5td Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:36 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-gsb5t Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:36 +0000 UTC - event for kube-proxy-gsb5t: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-gsb5t to capz-conf-r52y03-md-0-hb5td Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:37 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-k988f Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:37 +0000 UTC - event for calico-node-k988f: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-k988f to capz-conf-r52y03-md-0-4zbgs Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:37 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-b5d4p Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:37 +0000 UTC - event for kube-proxy-b5d4p: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-b5d4p to capz-conf-r52y03-md-0-4zbgs Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:40 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:40 +0000 UTC - event for kube-proxy-b5d4p: {kubelet capz-conf-r52y03-md-0-4zbgs} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca" Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:46 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:46 +0000 UTC - event for kube-proxy-gsb5t: {kubelet capz-conf-r52y03-md-0-hb5td} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca" Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:48 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.284829261s (7.284930365s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:48 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Created: Created container upgrade-ipam Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:48 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Started: Started container upgrade-ipam Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:50 +0000 UTC - event for kube-proxy-gsb5t: {kubelet capz-conf-r52y03-md-0-hb5td} Created: Created container kube-proxy Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:50 +0000 UTC - event for kube-proxy-gsb5t: {kubelet capz-conf-r52y03-md-0-hb5td} Started: Started container kube-proxy Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:50 +0000 UTC - event for kube-proxy-gsb5t: {kubelet capz-conf-r52y03-md-0-hb5td} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca" in 3.976473787s (3.976570277s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:51 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Created: Created container install-cni Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:51 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Started: Started container install-cni Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:51 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:54 +0000 UTC - event for kube-proxy-b5d4p: {kubelet capz-conf-r52y03-md-0-4zbgs} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca" in 5.951091528s (13.226697291s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:55 +0000 UTC - event for kube-proxy-b5d4p: {kubelet capz-conf-r52y03-md-0-4zbgs} Created: Created container kube-proxy Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:55 +0000 UTC - event for kube-proxy-b5d4p: {kubelet capz-conf-r52y03-md-0-4zbgs} Started: Started container kube-proxy Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:57 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.987355501s (10.952389337s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:57 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Created: Created container upgrade-ipam Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:57 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Started: Started container upgrade-ipam Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:58 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 25 14:52:10.396: INFO: At 2023-01-25 14:41:59 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:00 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Created: Created container install-cni Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:00 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Started: Started container install-cni Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:02 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:10 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Created: Created container calico-node Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:10 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.243010757s (7.243026257s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:10 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Started: Started container calico-node Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:11 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} 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 25 14:52:10.396: INFO: At 2023-01-25 14:42:11 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 12.577073099s (12.577077599s including waiting) Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:11 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Created: Created container calico-node Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:11 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} Started: Started container calico-node Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:12 +0000 UTC - event for calico-node-4cp9p: {kubelet capz-conf-r52y03-md-0-hb5td} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Jan 25 14:52:10.396: INFO: At 2023-01-25 14:42:12 +0000 UTC - event for calico-node-k988f: {kubelet capz-conf-r52y03-md-0-4zbgs} 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 25 14:52:10.563: INFO: POD NODE PHASE GRACE CONDITIONS Jan 25 14:52:10.563: INFO: calico-kube-controllers-657b584867-fxltc capz-conf-r52y03-control-plane-gxlsw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:25 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:55 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:55 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:25 +0000 UTC }] Jan 25 14:52:10.563: INFO: calico-node-4cp9p capz-conf-r52y03-md-0-hb5td Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:42:02 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:42:14 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:42:14 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:36 +0000 UTC }] Jan 25 14:52:10.563: INFO: calico-node-k988f capz-conf-r52y03-md-0-4zbgs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:58 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:42:19 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:42:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC }] Jan 25 14:52:10.563: INFO: calico-node-xkzqk capz-conf-r52y03-control-plane-gxlsw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:26 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:41 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:41 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:11 +0000 UTC }] Jan 25 14:52:10.563: INFO: coredns-56f4c55bf9-tp9hd capz-conf-r52y03-control-plane-gxlsw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:25 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:40 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:40 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:25 +0000 UTC }] Jan 25 14:52:10.563: INFO: coredns-56f4c55bf9-xvf2w capz-conf-r52y03-control-plane-gxlsw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:25 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:25 +0000 UTC }] Jan 25 14:52:10.563: INFO: etcd-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:39:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:39:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:39:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:39:47 +0000 UTC }] Jan 25 14:52:10.563: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:10.563: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:10.563: INFO: kube-proxy-b5d4p capz-conf-r52y03-md-0-4zbgs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:37 +0000 UTC }] Jan 25 14:52:10.563: INFO: kube-proxy-gsb5t capz-conf-r52y03-md-0-hb5td Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:50 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:36 +0000 UTC }] Jan 25 14:52:10.563: INFO: kube-proxy-kz6w8 capz-conf-r52y03-control-plane-gxlsw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:39:50 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:39:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:39:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:39:50 +0000 UTC }] Jan 25 14:52:10.563: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] Jan 25 14:52:10.563: INFO: metrics-server-c9574f845-gwh9p capz-conf-r52y03-control-plane-gxlsw Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:25 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:16 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:41:16 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-25 14:40:25 +0000 UTC }] Jan 25 14:52:10.563: INFO: Jan 25 14:52:11.263: INFO: Logging node info for node capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:11.371: INFO: Node Info: &Node{ObjectMeta:{capz-conf-r52y03-control-plane-gxlsw 253f0c28-54ab-4a13-9d2f-a44300969249 1803 0 2023-01-25 14:39:43 +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:northeurope failure-domain.beta.kubernetes.io/zone:northeurope-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-r52y03-control-plane-gxlsw 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:northeurope topology.kubernetes.io/zone:northeurope-1] map[cluster.x-k8s.io/cluster-name:capz-conf-r52y03 cluster.x-k8s.io/cluster-namespace:capz-conf-r52y03 cluster.x-k8s.io/machine:capz-conf-r52y03-control-plane-w295t cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-r52y03-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.203.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-25 14:39:43 +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-25 14:39:45 +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-25 14:40:05 +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-25 14:40:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2023-01-25 14:40:36 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-25 14:51:29 +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-r52y03/providers/Microsoft.Compute/virtualMachines/capz-conf-r52y03-control-plane-gxlsw,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/control-plane,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8344739840 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239882240 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-25 14:40:36 +0000 UTC,LastTransitionTime:2023-01-25 14:40:36 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-25 14:51:29 +0000 UTC,LastTransitionTime:2023-01-25 14:39:23 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-25 14:51:29 +0000 UTC,LastTransitionTime:2023-01-25 14:39:23 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-25 14:51:29 +0000 UTC,LastTransitionTime:2023-01-25 14:39:23 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-25 14:51:29 +0000 UTC,LastTransitionTime:2023-01-25 14:40:25 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-r52y03-control-plane-gxlsw,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:d9bfb466cd50405ea01d6b4ad6aa297c,SystemUUID:c653e9c9-c5d6-a04f-9f7a-67640e319246,BootID:c5857196-8893-4ba1-99c8-a53708e7f2b4,KernelVersion:5.4.0-1100-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.15,KubeletVersion:v1.27.0-alpha.1.12+c0d6888174f3ca,KubeProxyVersion:v1.27.0-alpha.1.12+c0d6888174f3ca,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:e1081b3ad06a77cf78c6b6731dfcc34db03124d6d0b82aaf30127b47ee81b33f gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.1.10_d29e3bd7aa4978],SizeBytes:35462561,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:99e1ed9fbc8a8d36a70f148f25130c02e0e366875249906be0bcb2c2d9df0c26 registry.k8s.io/kube-apiserver:v1.26.1],SizeBytes:35320235,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:17c185f563e18a09a9f6a3c90d4aedd44ccd844b4d6bb30c9ced2decb7b3d3b3 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.1.10_d29e3bd7aa4978],SizeBytes:32316146,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:40adecbe3a40aa147c7d6e9a1f5fbd99b3f6d42d5222483ed3a47337d4f9a10b registry.k8s.io/kube-controller-manager:v1.26.1],SizeBytes:32245960,},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:[registry.k8s.io/kube-proxy@sha256:85f705e7d98158a67432c53885b0d470c673b0fad3693440b45d07efebcda1c3 registry.k8s.io/kube-proxy:v1.26.1],SizeBytes:21536169,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:90321fc0f0b4d1eb33b8b1fee228ca36c5a5adddd692aad9c8eee05c5c5638b4 gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.1.10_d29e3bd7aa4978],SizeBytes:21487487,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:fdb9687c9b056bb3be8443afbb2a14c56c5a43691b549bd90e64c073abc637b3 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca],SizeBytes:21485445,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:af0292c2c4fa6d09ee8544445eef373c1c280113cb6c968398a37da3744c41e4 registry.k8s.io/kube-scheduler:v1.26.1],SizeBytes:17486267,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:b511dfbf646bcb921951527b4f9e6ece5b5b5ed60c7e51f66600f74ce13e3a77 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.1.10_d29e3bd7aa4978],SizeBytes:17471642,},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 25 14:52:11.372: INFO: Logging kubelet events for node capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:11.477: INFO: Logging pods the kubelet thinks is on node capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:11.612: INFO: calico-node-xkzqk started at 2023-01-25 14:40:11 +0000 UTC (2+1 container statuses recorded) Jan 25 14:52:11.612: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 25 14:52:11.612: INFO: Init container install-cni ready: true, restart count 0 Jan 25 14:52:11.612: INFO: Container calico-node ready: true, restart count 0 Jan 25 14:52:11.612: INFO: coredns-56f4c55bf9-tp9hd started at 2023-01-25 14:40:25 +0000 UTC (0+1 container statuses recorded) Jan 25 14:52:11.612: INFO: Container coredns ready: true, restart count 0 Jan 25 14:52:11.612: INFO: metrics-server-c9574f845-gwh9p started at 2023-01-25 14:40:25 +0000 UTC (0+1 container statuses recorded) Jan 25 14:52:11.612: INFO: Container metrics-server ready: true, restart count 0 Jan 25 14:52:11.612: INFO: calico-kube-controllers-657b584867-fxltc started at 2023-01-25 14:40:25 +0000 UTC (0+1 container statuses recorded) Jan 25 14:52:11.612: INFO: Container calico-kube-controllers ready: true, restart count 0 Jan 25 14:52:11.612: INFO: etcd-capz-conf-r52y03-control-plane-gxlsw started at 2023-01-25 14:39:47 +0000 UTC (0+1 container statuses recorded) Jan 25 14:52:11.612: INFO: Container etcd ready: true, restart count 0 Jan 25 14:52:11.612: INFO: kube-proxy-kz6w8 started at 2023-01-25 14:39:50 +0000 UTC (0+1 container statuses recorded) Jan 25 14:52:11.612: INFO: Container kube-proxy ready: true, restart count 0 Jan 25 14:52:11.612: INFO: kube-scheduler-capz-conf-r52y03-control-plane-gxlsw started at <nil> (0+0 container statuses recorded) Jan 25 14:52:11.612: INFO: coredns-56f4c55bf9-xvf2w started at 2023-01-25 14:40:25 +0000 UTC (0+1 container statuses recorded) Jan 25 14:52:11.612: INFO: Container coredns ready: true, restart count 0 Jan 25 14:52:11.612: INFO: kube-apiserver-capz-conf-r52y03-control-plane-gxlsw started at <nil> (0+0 container statuses recorded) Jan 25 14:52:11.612: INFO: kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw started at <nil> (0+0 container statuses recorded) Jan 25 14:52:12.103: INFO: Latency metrics for node capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:12.103: INFO: Logging node info for node capz-conf-r52y03-md-0-4zbgs Jan 25 14:52:12.211: INFO: Node Info: &Node{ObjectMeta:{capz-conf-r52y03-md-0-4zbgs 2fd1fd1b-8ad0-43ad-9b66-8a71f89fdb26 1450 0 2023-01-25 14:41:37 +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:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-r52y03-md-0-4zbgs kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-r52y03 cluster.x-k8s.io/cluster-namespace:capz-conf-r52y03 cluster.x-k8s.io/machine:capz-conf-r52y03-md-0-6bcbf9946-ncz4r cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-r52y03-md-0-6bcbf9946 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.216.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-25 14:41:37 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-25 14:41:37 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-25 14:41:56 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2023-01-25 14:41:56 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2023-01-25 14:42:11 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-25 14:47:33 +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-r52y03/providers/Microsoft.Compute/virtualMachines/capz-conf-r52y03-md-0-4zbgs,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: {{8344739840 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239882240 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-25 14:42:11 +0000 UTC,LastTransitionTime:2023-01-25 14:42:11 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-25 14:47:33 +0000 UTC,LastTransitionTime:2023-01-25 14:41:36 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-25 14:47:33 +0000 UTC,LastTransitionTime:2023-01-25 14:41:36 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-25 14:47:33 +0000 UTC,LastTransitionTime:2023-01-25 14:41:36 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-25 14:47:33 +0000 UTC,LastTransitionTime:2023-01-25 14:41:56 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-r52y03-md-0-4zbgs,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:5e84bb1a35ba4facb4d97a28aca94724,SystemUUID:e2e52fab-3c05-a34f-901c-0cd19ae53613,BootID:0fe614ee-64d2-4e10-9568-4553ec43b529,KernelVersion:5.4.0-1100-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.15,KubeletVersion:v1.27.0-alpha.1.12+c0d6888174f3ca,KubeProxyVersion:v1.27.0-alpha.1.12+c0d6888174f3ca,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:99e1ed9fbc8a8d36a70f148f25130c02e0e366875249906be0bcb2c2d9df0c26 registry.k8s.io/kube-apiserver:v1.26.1],SizeBytes:35320235,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:40adecbe3a40aa147c7d6e9a1f5fbd99b3f6d42d5222483ed3a47337d4f9a10b registry.k8s.io/kube-controller-manager:v1.26.1],SizeBytes:32245960,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:85f705e7d98158a67432c53885b0d470c673b0fad3693440b45d07efebcda1c3 registry.k8s.io/kube-proxy:v1.26.1],SizeBytes:21536169,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:fdb9687c9b056bb3be8443afbb2a14c56c5a43691b549bd90e64c073abc637b3 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca],SizeBytes:21485445,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:af0292c2c4fa6d09ee8544445eef373c1c280113cb6c968398a37da3744c41e4 registry.k8s.io/kube-scheduler:v1.26.1],SizeBytes:17486267,},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 25 14:52:12.211: INFO: Logging kubelet events for node capz-conf-r52y03-md-0-4zbgs Jan 25 14:52:12.317: INFO: Logging pods the kubelet thinks is on node capz-conf-r52y03-md-0-4zbgs Jan 25 14:52:12.431: INFO: calico-node-k988f started at 2023-01-25 14:41:37 +0000 UTC (2+1 container statuses recorded) Jan 25 14:52:12.431: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 25 14:52:12.431: INFO: Init container install-cni ready: true, restart count 0 Jan 25 14:52:12.431: INFO: Container calico-node ready: true, restart count 0 Jan 25 14:52:12.431: INFO: kube-proxy-b5d4p started at 2023-01-25 14:41:37 +0000 UTC (0+1 container statuses recorded) Jan 25 14:52:12.431: INFO: Container kube-proxy ready: true, restart count 0 Jan 25 14:52:12.851: INFO: Latency metrics for node capz-conf-r52y03-md-0-4zbgs Jan 25 14:52:12.851: INFO: Logging node info for node capz-conf-r52y03-md-0-hb5td Jan 25 14:52:12.958: INFO: Node Info: &Node{ObjectMeta:{capz-conf-r52y03-md-0-hb5td 27c510ac-204c-4be5-91f8-a9e8b37c32e0 1455 0 2023-01-25 14:41:36 +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:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-r52y03-md-0-hb5td kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-r52y03 cluster.x-k8s.io/cluster-namespace:capz-conf-r52y03 cluster.x-k8s.io/machine:capz-conf-r52y03-md-0-6bcbf9946-fbht6 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-r52y03-md-0-6bcbf9946 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.175.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-25 14:41:36 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-25 14:41:36 +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-25 14:41:55 +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-25 14:42:02 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-25 14:42:10 +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-25 14:47:35 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-r52y03/providers/Microsoft.Compute/virtualMachines/capz-conf-r52y03-md-0-hb5td,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: {{8344739840 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239882240 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-25 14:42:10 +0000 UTC,LastTransitionTime:2023-01-25 14:42:10 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-25 14:47:35 +0000 UTC,LastTransitionTime:2023-01-25 14:41:36 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-25 14:47:35 +0000 UTC,LastTransitionTime:2023-01-25 14:41:36 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-25 14:47:35 +0000 UTC,LastTransitionTime:2023-01-25 14:41:36 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-25 14:47:35 +0000 UTC,LastTransitionTime:2023-01-25 14:42:02 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-r52y03-md-0-hb5td,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:1d806ea3c9e64338985244702822139e,SystemUUID:6fa3165f-d2e2-d045-b9fd-434c32f79082,BootID:969bd457-ebce-4ae9-a74c-406b9d84d56c,KernelVersion:5.4.0-1100-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.15,KubeletVersion:v1.27.0-alpha.1.12+c0d6888174f3ca,KubeProxyVersion:v1.27.0-alpha.1.12+c0d6888174f3ca,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:99e1ed9fbc8a8d36a70f148f25130c02e0e366875249906be0bcb2c2d9df0c26 registry.k8s.io/kube-apiserver:v1.26.1],SizeBytes:35320235,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:40adecbe3a40aa147c7d6e9a1f5fbd99b3f6d42d5222483ed3a47337d4f9a10b registry.k8s.io/kube-controller-manager:v1.26.1],SizeBytes:32245960,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:85f705e7d98158a67432c53885b0d470c673b0fad3693440b45d07efebcda1c3 registry.k8s.io/kube-proxy:v1.26.1],SizeBytes:21536169,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:fdb9687c9b056bb3be8443afbb2a14c56c5a43691b549bd90e64c073abc637b3 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.1.12_c0d6888174f3ca],SizeBytes:21485445,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:af0292c2c4fa6d09ee8544445eef373c1c280113cb6c968398a37da3744c41e4 registry.k8s.io/kube-scheduler:v1.26.1],SizeBytes:17486267,},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 25 14:52:12.958: INFO: Logging kubelet events for node capz-conf-r52y03-md-0-hb5td Jan 25 14:52:13.069: INFO: Logging pods the kubelet thinks is on node capz-conf-r52y03-md-0-hb5td Jan 25 14:52:13.184: INFO: calico-node-4cp9p started at 2023-01-25 14:41:43 +0000 UTC (2+1 container statuses recorded) Jan 25 14:52:13.184: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 25 14:52:13.184: INFO: Init container install-cni ready: true, restart count 0 Jan 25 14:52:13.184: INFO: Container calico-node ready: true, restart count 0 Jan 25 14:52:13.184: INFO: kube-proxy-gsb5t started at 2023-01-25 14:41:43 +0000 UTC (0+1 container statuses recorded) Jan 25 14:52:13.184: INFO: Container kube-proxy ready: true, restart count 0 Jan 25 14:52:13.610: INFO: Latency metrics for node capz-conf-r52y03-md-0-hb5td Jan 25 14:52:13.826: INFO: Running kubectl logs on non-ready containers in kube-system Jan 25 14:52:14.170: INFO: Failed to get logs of pod kube-apiserver-capz-conf-r52y03-control-plane-gxlsw, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-r52y03-control-plane-gxlsw) Jan 25 14:52:14.170: INFO: Logs of kube-system/kube-apiserver-capz-conf-r52y03-control-plane-gxlsw:kube-apiserver on node capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:14.170: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-r52y03-control-plane-gxlsw:kube-apiserver Jan 25 14:52:14.570: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw) Jan 25 14:52:14.570: INFO: Logs of kube-system/kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw:kube-controller-manager on node capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:14.570: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw:kube-controller-manager Jan 25 14:52:14.971: INFO: Failed to get logs of pod kube-scheduler-capz-conf-r52y03-control-plane-gxlsw, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-r52y03-control-plane-gxlsw) Jan 25 14:52:14.971: INFO: Logs of kube-system/kube-scheduler-capz-conf-r52y03-control-plane-gxlsw:kube-scheduler on node capz-conf-r52y03-control-plane-gxlsw Jan 25 14:52:14.971: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-r52y03-control-plane-gxlsw: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-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] kube-controller-manager-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] kube-scheduler-capz-conf-r52y03-control-plane-gxlsw capz-conf-r52y03-control-plane-gxlsw Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/25/23 14:52:14.971 < Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/25/23 14:52:14.971 (10m6.576s)
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/25/23 14:52:15.017from 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/25/23 14:52:15.017
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/25/23 14:52:15.011from 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/25/23 14:52:15.011
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/25/23 14:52:15.04from 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/25/23 14:52:15.04
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/25/23 14:52:15.026from 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/25/23 14:52:15.026
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/25/23 14:52:15.039from 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/25/23 14:52:15.039
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/25/23 14:52:15.044from 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/25/23 14:52:15.044
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [ReportBeforeSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
capz-e2e 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