PR #107826 pull-kubernetes-e2e-capz-conformance #1616119201041223680
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | smarterclayton: wait: Introduce new methods that allow detection of context cancellation |
| Result | SUCCESS |
| Tests | 25 failed / 28 succeeded |
| Started | |
| Elapsed | 58m3s |
| Revision | 9527d41c12d5909eba589a5c2c2275a10200526f |
| Refs |
107826 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.453from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.453
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.452from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.452
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.474from 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/19/23 17:55:45.474
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/19/23 17:55:45.452from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.452
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.476from 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/19/23 17:55:45.476
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/19/23 17:55:45.453from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.453
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.461from 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/19/23 17:55:45.461
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/19/23 17:55:45.452from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.452
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.462from 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/19/23 17:55:45.462
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/19/23 17:55:45.456from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.456
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.452from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.452
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.462from 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/19/23 17:55:45.462
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/19/23 17:55:45.461from 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/19/23 17:55:45.461
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/19/23 17:55:45.461from 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/19/23 17:55:45.461
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/19/23 17:55:45.456from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.456
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.461from 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/19/23 17:55:45.461
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/19/23 17:55:45.4from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.4
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.453from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.453
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] Error waiting for all pods to be running and ready: 2 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s POD NODE PHASE GRACE CONDITIONS kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/19/23 17:55:45.398from junit.kubetest.01.xml
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/19/23 17:45:38.953 Jan 19 17:45:38.954: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 19 17:45:39.005: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 19 17:45:39.622: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 19 17:45:40.253: INFO: The status of Pod calico-node-5fj2p is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:40.253: INFO: The status of Pod calico-node-l2rd6 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:40.253: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:40.253: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:40.253: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 19 17:45:40.253: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:40.253: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:40.253: INFO: calico-node-5fj2p capz-conf-b9w8m3-md-0-xfjrf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:28 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:09 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:09 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:01 +0000 UTC }] Jan 19 17:45:40.253: INFO: calico-node-l2rd6 capz-conf-b9w8m3-md-0-p2z5x Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:29 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:10 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:10 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:06 +0000 UTC }] Jan 19 17:45:40.253: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:40.253: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:40.253: INFO: Jan 19 17:45:42.650: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:42.650: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:42.650: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (3 seconds elapsed) Jan 19 17:45:42.650: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:42.650: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:42.650: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:42.650: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:42.650: INFO: Jan 19 17:45:44.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:44.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:44.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (5 seconds elapsed) Jan 19 17:45:44.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:44.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:44.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:44.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:44.638: INFO: Jan 19 17:45:46.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:46.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:46.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (7 seconds elapsed) Jan 19 17:45:46.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:46.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:46.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:46.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:46.632: INFO: Jan 19 17:45:48.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:48.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:48.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (9 seconds elapsed) Jan 19 17:45:48.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:48.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:48.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:48.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:48.634: INFO: Jan 19 17:45:50.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:50.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:50.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (11 seconds elapsed) Jan 19 17:45:50.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:50.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:50.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:50.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:50.632: INFO: Jan 19 17:45:52.644: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:52.644: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:52.644: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (13 seconds elapsed) Jan 19 17:45:52.644: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:52.644: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:52.644: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:52.644: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:52.644: INFO: Jan 19 17:45:54.677: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:54.677: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:54.677: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (15 seconds elapsed) Jan 19 17:45:54.677: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:54.677: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:54.677: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:54.677: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:54.677: INFO: Jan 19 17:45:56.698: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:56.698: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:56.698: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (17 seconds elapsed) Jan 19 17:45:56.698: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:56.698: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:56.698: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:56.698: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:56.698: INFO: Jan 19 17:45:58.643: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:58.643: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:45:58.643: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (19 seconds elapsed) Jan 19 17:45:58.643: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:45:58.643: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:45:58.643: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:58.643: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:45:58.643: INFO: Jan 19 17:46:00.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:00.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:00.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (21 seconds elapsed) Jan 19 17:46:00.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:00.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:00.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:00.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:00.631: INFO: Jan 19 17:46:02.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:02.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:02.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (23 seconds elapsed) Jan 19 17:46:02.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:02.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:02.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:02.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:02.634: INFO: Jan 19 17:46:04.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:04.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:04.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (25 seconds elapsed) Jan 19 17:46:04.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:04.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:04.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:04.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:04.630: INFO: Jan 19 17:46:06.628: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:06.628: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:06.628: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (27 seconds elapsed) Jan 19 17:46:06.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:06.628: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:06.628: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:06.628: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:06.628: INFO: Jan 19 17:46:08.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:08.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:08.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (29 seconds elapsed) Jan 19 17:46:08.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:08.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:08.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:08.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:08.633: INFO: Jan 19 17:46:10.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:10.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:10.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (31 seconds elapsed) Jan 19 17:46:10.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:10.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:10.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:10.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:10.630: INFO: Jan 19 17:46:12.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:12.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:12.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (33 seconds elapsed) Jan 19 17:46:12.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:12.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:12.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:12.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:12.634: INFO: Jan 19 17:46:14.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:14.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:14.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (35 seconds elapsed) Jan 19 17:46:14.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:14.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:14.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:14.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:14.641: INFO: Jan 19 17:46:16.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:16.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:16.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (37 seconds elapsed) Jan 19 17:46:16.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:16.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:16.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:16.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:16.637: INFO: Jan 19 17:46:18.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:18.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:18.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (39 seconds elapsed) Jan 19 17:46:18.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:18.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:18.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:18.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:18.641: INFO: Jan 19 17:46:20.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:20.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:20.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (41 seconds elapsed) Jan 19 17:46:20.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:20.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:20.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:20.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:20.640: INFO: Jan 19 17:46:22.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:22.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:22.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (43 seconds elapsed) Jan 19 17:46:22.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:22.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:22.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:22.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:22.637: INFO: Jan 19 17:46:24.669: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:24.669: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:24.669: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (45 seconds elapsed) Jan 19 17:46:24.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:24.669: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:24.669: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:24.669: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:24.669: INFO: Jan 19 17:46:26.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:26.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:26.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (47 seconds elapsed) Jan 19 17:46:26.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:26.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:26.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:26.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:26.636: INFO: Jan 19 17:46:28.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:28.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:28.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (49 seconds elapsed) Jan 19 17:46:28.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:28.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:28.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:28.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:28.638: INFO: Jan 19 17:46:30.647: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:30.647: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:30.647: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (51 seconds elapsed) Jan 19 17:46:30.647: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:30.647: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:30.647: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:30.647: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:30.647: INFO: Jan 19 17:46:32.646: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:32.646: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:32.646: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (53 seconds elapsed) Jan 19 17:46:32.646: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:32.646: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:32.646: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:32.646: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:32.646: INFO: Jan 19 17:46:34.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:34.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:34.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (55 seconds elapsed) Jan 19 17:46:34.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:34.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:34.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:34.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:34.640: INFO: Jan 19 17:46:36.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:36.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:36.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (57 seconds elapsed) Jan 19 17:46:36.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:36.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:36.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:36.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:36.638: INFO: Jan 19 17:46:38.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:38.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:38.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (59 seconds elapsed) Jan 19 17:46:38.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:38.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:38.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:38.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:38.635: INFO: Jan 19 17:46:40.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:40.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:40.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (61 seconds elapsed) Jan 19 17:46:40.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:40.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:40.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:40.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:40.637: INFO: Jan 19 17:46:42.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:42.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:42.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (63 seconds elapsed) Jan 19 17:46:42.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:42.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:42.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:42.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:42.639: INFO: Jan 19 17:46:44.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:44.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:44.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (65 seconds elapsed) Jan 19 17:46:44.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:44.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:44.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:44.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:44.639: INFO: Jan 19 17:46:46.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:46.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:46.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (67 seconds elapsed) Jan 19 17:46:46.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:46.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:46.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:46.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:46.635: INFO: Jan 19 17:46:48.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:48.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:48.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (69 seconds elapsed) Jan 19 17:46:48.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:48.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:48.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:48.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:48.637: INFO: Jan 19 17:46:50.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:50.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:50.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (71 seconds elapsed) Jan 19 17:46:50.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:50.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:50.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:50.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:50.637: INFO: Jan 19 17:46:52.644: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:52.644: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:52.644: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (73 seconds elapsed) Jan 19 17:46:52.644: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:52.644: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:52.644: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:52.644: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:52.644: INFO: Jan 19 17:46:54.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:54.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:54.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (75 seconds elapsed) Jan 19 17:46:54.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:54.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:54.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:54.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:54.636: INFO: Jan 19 17:46:56.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:56.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:56.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (77 seconds elapsed) Jan 19 17:46:56.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:56.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:56.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:56.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:56.638: INFO: Jan 19 17:46:58.648: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:58.648: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:46:58.648: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (79 seconds elapsed) Jan 19 17:46:58.648: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:46:58.648: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:46:58.648: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:58.648: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:46:58.648: INFO: Jan 19 17:47:00.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:00.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:00.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (81 seconds elapsed) Jan 19 17:47:00.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:00.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:00.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:00.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:00.638: INFO: Jan 19 17:47:02.653: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:02.653: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:02.653: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (83 seconds elapsed) Jan 19 17:47:02.653: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:02.653: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:02.653: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:02.653: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:02.653: INFO: Jan 19 17:47:04.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:04.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:04.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (85 seconds elapsed) Jan 19 17:47:04.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:04.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:04.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:04.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:04.638: INFO: Jan 19 17:47:06.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:06.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:06.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (87 seconds elapsed) Jan 19 17:47:06.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:06.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:06.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:06.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:06.635: INFO: Jan 19 17:47:08.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:08.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:08.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (89 seconds elapsed) Jan 19 17:47:08.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:08.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:08.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:08.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:08.635: INFO: Jan 19 17:47:10.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:10.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:10.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (91 seconds elapsed) Jan 19 17:47:10.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:10.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:10.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:10.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:10.635: INFO: Jan 19 17:47:12.644: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:12.644: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:12.644: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (93 seconds elapsed) Jan 19 17:47:12.644: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:12.644: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:12.644: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:12.644: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:12.644: INFO: Jan 19 17:47:14.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:14.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:14.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (95 seconds elapsed) Jan 19 17:47:14.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:14.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:14.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:14.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:14.635: INFO: Jan 19 17:47:16.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:16.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:16.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (97 seconds elapsed) Jan 19 17:47:16.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:16.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:16.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:16.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:16.633: INFO: Jan 19 17:47:18.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:18.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:18.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (99 seconds elapsed) Jan 19 17:47:18.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:18.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:18.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:18.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:18.637: INFO: Jan 19 17:47:20.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:20.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:20.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (101 seconds elapsed) Jan 19 17:47:20.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:20.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:20.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:20.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:20.636: INFO: Jan 19 17:47:22.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:22.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:22.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (103 seconds elapsed) Jan 19 17:47:22.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:22.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:22.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:22.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:22.635: INFO: Jan 19 17:47:24.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:24.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:24.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (105 seconds elapsed) Jan 19 17:47:24.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:24.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:24.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:24.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:24.639: INFO: Jan 19 17:47:26.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:26.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:26.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (107 seconds elapsed) Jan 19 17:47:26.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:26.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:26.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:26.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:26.641: INFO: Jan 19 17:47:28.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:28.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:28.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (109 seconds elapsed) Jan 19 17:47:28.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:28.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:28.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:28.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:28.635: INFO: Jan 19 17:47:30.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:30.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:30.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (111 seconds elapsed) Jan 19 17:47:30.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:30.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:30.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:30.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:30.638: INFO: Jan 19 17:47:32.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:32.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:32.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (113 seconds elapsed) Jan 19 17:47:32.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:32.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:32.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:32.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:32.639: INFO: Jan 19 17:47:34.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:34.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:34.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (115 seconds elapsed) Jan 19 17:47:34.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:34.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:34.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:34.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:34.636: INFO: Jan 19 17:47:36.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:36.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:36.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (117 seconds elapsed) Jan 19 17:47:36.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:36.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:36.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:36.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:36.636: INFO: Jan 19 17:47:38.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:38.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:38.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (119 seconds elapsed) Jan 19 17:47:38.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:38.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:38.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:38.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:38.639: INFO: Jan 19 17:47:40.642: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:40.642: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:40.642: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (121 seconds elapsed) Jan 19 17:47:40.642: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:40.642: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:40.642: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:40.642: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:40.642: INFO: Jan 19 17:47:42.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:42.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:42.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (123 seconds elapsed) Jan 19 17:47:42.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:42.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:42.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:42.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:42.635: INFO: Jan 19 17:47:44.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:44.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:44.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (125 seconds elapsed) Jan 19 17:47:44.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:44.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:44.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:44.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:44.630: INFO: Jan 19 17:47:46.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:46.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:46.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (127 seconds elapsed) Jan 19 17:47:46.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:46.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:46.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:46.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:46.630: INFO: Jan 19 17:47:48.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:48.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:48.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (129 seconds elapsed) Jan 19 17:47:48.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:48.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:48.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:48.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:48.635: INFO: Jan 19 17:47:50.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:50.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:50.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (131 seconds elapsed) Jan 19 17:47:50.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:50.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:50.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:50.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:50.629: INFO: Jan 19 17:47:52.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:52.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:52.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (133 seconds elapsed) Jan 19 17:47:52.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:52.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:52.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:52.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:52.634: INFO: Jan 19 17:47:54.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:54.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:54.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (135 seconds elapsed) Jan 19 17:47:54.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:54.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:54.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:54.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:54.631: INFO: Jan 19 17:47:56.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:56.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:56.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (137 seconds elapsed) Jan 19 17:47:56.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:56.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:56.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:56.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:56.630: INFO: Jan 19 17:47:58.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:58.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:47:58.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (139 seconds elapsed) Jan 19 17:47:58.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:47:58.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:47:58.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:58.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:47:58.633: INFO: Jan 19 17:48:00.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:00.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:00.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (141 seconds elapsed) Jan 19 17:48:00.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:00.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:00.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:00.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:00.630: INFO: Jan 19 17:48:02.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:02.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:02.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (143 seconds elapsed) Jan 19 17:48:02.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:02.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:02.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:02.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:02.640: INFO: Jan 19 17:48:04.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:04.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:04.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (145 seconds elapsed) Jan 19 17:48:04.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:04.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:04.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:04.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:04.633: INFO: Jan 19 17:48:06.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:06.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:06.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (147 seconds elapsed) Jan 19 17:48:06.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:06.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:06.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:06.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:06.634: INFO: Jan 19 17:48:08.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:08.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:08.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (149 seconds elapsed) Jan 19 17:48:08.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:08.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:08.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:08.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:08.632: INFO: Jan 19 17:48:10.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:10.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:10.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (151 seconds elapsed) Jan 19 17:48:10.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:10.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:10.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:10.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:10.632: INFO: Jan 19 17:48:12.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:12.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:12.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (153 seconds elapsed) Jan 19 17:48:12.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:12.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:12.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:12.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:12.630: INFO: Jan 19 17:48:14.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:14.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:14.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (155 seconds elapsed) Jan 19 17:48:14.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:14.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:14.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:14.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:14.631: INFO: Jan 19 17:48:16.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:16.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:16.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (157 seconds elapsed) Jan 19 17:48:16.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:16.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:16.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:16.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:16.634: INFO: Jan 19 17:48:18.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:18.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:18.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (159 seconds elapsed) Jan 19 17:48:18.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:18.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:18.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:18.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:18.632: INFO: Jan 19 17:48:20.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:20.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:20.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (161 seconds elapsed) Jan 19 17:48:20.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:20.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:20.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:20.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:20.635: INFO: Jan 19 17:48:22.834: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:22.834: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:22.834: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (163 seconds elapsed) Jan 19 17:48:22.834: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:22.834: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:22.834: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:22.834: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:22.834: INFO: Jan 19 17:48:24.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:24.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:24.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (165 seconds elapsed) Jan 19 17:48:24.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:24.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:24.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:24.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:24.635: INFO: Jan 19 17:48:26.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:26.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:26.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (167 seconds elapsed) Jan 19 17:48:26.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:26.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:26.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:26.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:26.636: INFO: Jan 19 17:48:28.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:28.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:28.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (169 seconds elapsed) Jan 19 17:48:28.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:28.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:28.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:28.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:28.640: INFO: Jan 19 17:48:30.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:30.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:30.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (171 seconds elapsed) Jan 19 17:48:30.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:30.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:30.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:30.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:30.639: INFO: Jan 19 17:48:32.642: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:32.642: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:32.642: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (173 seconds elapsed) Jan 19 17:48:32.642: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:32.642: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:32.642: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:32.642: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:32.642: INFO: Jan 19 17:48:34.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:34.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:34.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (175 seconds elapsed) Jan 19 17:48:34.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:34.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:34.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:34.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:34.639: INFO: Jan 19 17:48:36.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:36.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:36.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (177 seconds elapsed) Jan 19 17:48:36.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:36.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:36.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:36.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:36.633: INFO: Jan 19 17:48:38.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:38.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:38.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (179 seconds elapsed) Jan 19 17:48:38.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:38.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:38.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:38.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:38.636: INFO: Jan 19 17:48:40.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:40.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:40.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (181 seconds elapsed) Jan 19 17:48:40.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:40.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:40.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:40.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:40.637: INFO: Jan 19 17:48:42.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:42.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:42.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (183 seconds elapsed) Jan 19 17:48:42.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:42.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:42.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:42.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:42.638: INFO: Jan 19 17:48:44.648: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:44.648: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:44.648: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (185 seconds elapsed) Jan 19 17:48:44.648: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:44.648: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:44.648: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:44.648: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:44.648: INFO: Jan 19 17:48:46.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:46.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:46.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (187 seconds elapsed) Jan 19 17:48:46.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:46.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:46.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:46.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:46.636: INFO: Jan 19 17:48:48.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:48.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:48.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (189 seconds elapsed) Jan 19 17:48:48.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:48.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:48.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:48.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:48.635: INFO: Jan 19 17:48:50.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:50.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:50.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (191 seconds elapsed) Jan 19 17:48:50.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:50.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:50.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:50.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:50.635: INFO: Jan 19 17:48:52.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:52.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:52.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (193 seconds elapsed) Jan 19 17:48:52.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:52.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:52.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:52.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:52.634: INFO: Jan 19 17:48:54.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:54.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:54.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (195 seconds elapsed) Jan 19 17:48:54.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:54.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:54.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:54.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:54.636: INFO: Jan 19 17:48:56.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:56.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:56.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (197 seconds elapsed) Jan 19 17:48:56.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:56.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:56.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:56.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:56.637: INFO: Jan 19 17:48:58.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:58.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:48:58.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (199 seconds elapsed) Jan 19 17:48:58.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:48:58.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:48:58.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:58.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:48:58.638: INFO: Jan 19 17:49:00.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:00.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:00.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (201 seconds elapsed) Jan 19 17:49:00.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:00.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:00.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:00.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:00.639: INFO: Jan 19 17:49:02.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:02.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:02.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (203 seconds elapsed) Jan 19 17:49:02.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:02.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:02.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:02.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:02.635: INFO: Jan 19 17:49:04.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:04.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:04.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (205 seconds elapsed) Jan 19 17:49:04.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:04.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:04.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:04.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:04.639: INFO: Jan 19 17:49:06.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:06.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:06.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (207 seconds elapsed) Jan 19 17:49:06.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:06.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:06.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:06.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:06.634: INFO: Jan 19 17:49:08.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:08.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:08.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (209 seconds elapsed) Jan 19 17:49:08.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:08.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:08.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:08.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:08.641: INFO: Jan 19 17:49:10.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:10.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:10.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (211 seconds elapsed) Jan 19 17:49:10.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:10.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:10.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:10.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:10.640: INFO: Jan 19 17:49:12.646: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:12.646: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:12.646: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (213 seconds elapsed) Jan 19 17:49:12.646: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:12.646: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:12.646: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:12.646: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:12.646: INFO: Jan 19 17:49:14.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:14.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:14.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (215 seconds elapsed) Jan 19 17:49:14.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:14.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:14.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:14.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:14.634: INFO: Jan 19 17:49:16.655: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:16.655: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:16.655: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (217 seconds elapsed) Jan 19 17:49:16.655: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:16.655: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:16.655: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:16.655: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:16.655: INFO: Jan 19 17:49:18.835: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:18.835: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:18.835: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (219 seconds elapsed) Jan 19 17:49:18.835: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:18.835: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:18.835: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:18.835: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:18.835: INFO: Jan 19 17:49:20.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:20.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:20.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (221 seconds elapsed) Jan 19 17:49:20.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:20.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:20.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:20.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:20.634: INFO: Jan 19 17:49:22.653: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:22.653: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:22.653: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (223 seconds elapsed) Jan 19 17:49:22.653: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:22.653: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:22.653: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:22.653: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:22.653: INFO: Jan 19 17:49:24.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:24.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:24.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (225 seconds elapsed) Jan 19 17:49:24.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:24.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:24.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:24.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:24.635: INFO: Jan 19 17:49:26.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:26.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:26.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (227 seconds elapsed) Jan 19 17:49:26.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:26.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:26.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:26.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:26.633: INFO: Jan 19 17:49:28.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:28.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:28.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (229 seconds elapsed) Jan 19 17:49:28.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:28.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:28.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:28.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:28.634: INFO: Jan 19 17:49:30.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:30.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:30.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (231 seconds elapsed) Jan 19 17:49:30.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:30.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:30.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:30.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:30.634: INFO: Jan 19 17:49:32.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:32.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:32.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (233 seconds elapsed) Jan 19 17:49:32.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:32.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:32.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:32.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:32.635: INFO: Jan 19 17:49:34.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:34.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:34.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (235 seconds elapsed) Jan 19 17:49:34.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:34.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:34.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:34.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:34.635: INFO: Jan 19 17:49:36.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:36.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:36.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (237 seconds elapsed) Jan 19 17:49:36.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:36.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:36.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:36.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:36.634: INFO: Jan 19 17:49:38.658: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:38.658: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:38.658: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (239 seconds elapsed) Jan 19 17:49:38.658: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:38.658: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:38.658: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:38.658: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:38.658: INFO: Jan 19 17:49:40.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:40.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:40.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (241 seconds elapsed) Jan 19 17:49:40.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:40.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:40.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:40.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:40.635: INFO: Jan 19 17:49:42.644: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:42.644: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:42.644: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (243 seconds elapsed) Jan 19 17:49:42.644: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:42.644: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:42.644: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:42.644: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:42.644: INFO: Jan 19 17:49:44.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:44.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:44.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (245 seconds elapsed) Jan 19 17:49:44.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:44.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:44.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:44.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:44.632: INFO: Jan 19 17:49:46.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:46.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:46.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (247 seconds elapsed) Jan 19 17:49:46.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:46.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:46.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:46.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:46.634: INFO: Jan 19 17:49:48.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:48.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:48.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (249 seconds elapsed) Jan 19 17:49:48.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:48.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:48.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:48.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:48.634: INFO: Jan 19 17:49:50.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:50.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:50.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (251 seconds elapsed) Jan 19 17:49:50.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:50.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:50.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:50.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:50.630: INFO: Jan 19 17:49:52.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:52.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:52.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (253 seconds elapsed) Jan 19 17:49:52.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:52.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:52.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:52.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:52.631: INFO: Jan 19 17:49:54.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:54.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:54.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (255 seconds elapsed) Jan 19 17:49:54.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:54.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:54.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:54.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:54.632: INFO: Jan 19 17:49:56.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:56.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:56.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (257 seconds elapsed) Jan 19 17:49:56.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:56.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:56.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:56.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:56.633: INFO: Jan 19 17:49:58.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:58.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:49:58.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (259 seconds elapsed) Jan 19 17:49:58.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:49:58.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:49:58.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:58.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:49:58.635: INFO: Jan 19 17:50:00.644: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:00.644: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:00.644: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (261 seconds elapsed) Jan 19 17:50:00.644: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:00.644: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:00.644: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:00.644: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:00.644: INFO: Jan 19 17:50:02.654: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:02.654: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:02.654: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (263 seconds elapsed) Jan 19 17:50:02.654: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:02.654: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:02.654: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:02.654: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:02.654: INFO: Jan 19 17:50:04.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:04.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:04.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (265 seconds elapsed) Jan 19 17:50:04.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:04.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:04.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:04.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:04.638: INFO: Jan 19 17:50:06.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:06.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:06.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (267 seconds elapsed) Jan 19 17:50:06.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:06.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:06.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:06.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:06.638: INFO: Jan 19 17:50:08.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:08.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:08.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (269 seconds elapsed) Jan 19 17:50:08.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:08.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:08.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:08.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:08.632: INFO: Jan 19 17:50:10.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:10.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:10.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (271 seconds elapsed) Jan 19 17:50:10.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:10.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:10.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:10.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:10.630: INFO: Jan 19 17:50:12.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:12.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:12.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (273 seconds elapsed) Jan 19 17:50:12.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:12.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:12.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:12.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:12.634: INFO: Jan 19 17:50:14.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:14.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:14.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (275 seconds elapsed) Jan 19 17:50:14.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:14.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:14.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:14.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:14.632: INFO: Jan 19 17:50:16.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:16.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:16.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (277 seconds elapsed) Jan 19 17:50:16.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:16.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:16.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:16.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:16.635: INFO: Jan 19 17:50:18.628: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:18.628: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:18.628: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (279 seconds elapsed) Jan 19 17:50:18.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:18.628: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:18.628: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:18.628: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:18.628: INFO: Jan 19 17:50:20.628: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:20.628: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:20.628: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (281 seconds elapsed) Jan 19 17:50:20.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:20.628: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:20.628: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:20.628: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:20.628: INFO: Jan 19 17:50:22.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:22.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:22.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (283 seconds elapsed) Jan 19 17:50:22.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:22.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:22.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:22.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:22.632: INFO: Jan 19 17:50:24.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:24.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:24.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (285 seconds elapsed) Jan 19 17:50:24.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:24.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:24.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:24.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:24.637: INFO: Jan 19 17:50:26.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:26.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:26.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (287 seconds elapsed) Jan 19 17:50:26.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:26.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:26.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:26.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:26.633: INFO: Jan 19 17:50:28.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:28.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:28.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (289 seconds elapsed) Jan 19 17:50:28.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:28.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:28.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:28.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:28.630: INFO: Jan 19 17:50:30.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:30.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:30.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (291 seconds elapsed) Jan 19 17:50:30.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:30.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:30.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:30.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:30.630: INFO: Jan 19 17:50:32.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:32.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:32.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (293 seconds elapsed) Jan 19 17:50:32.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:32.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:32.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:32.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:32.635: INFO: Jan 19 17:50:34.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:34.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:34.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (295 seconds elapsed) Jan 19 17:50:34.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:34.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:34.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:34.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:34.635: INFO: Jan 19 17:50:36.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:36.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:36.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (297 seconds elapsed) Jan 19 17:50:36.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:36.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:36.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:36.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:36.635: INFO: Jan 19 17:50:38.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:38.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:38.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (299 seconds elapsed) Jan 19 17:50:38.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:38.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:38.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:38.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:38.630: INFO: Jan 19 17:50:40.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:40.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:40.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (301 seconds elapsed) Jan 19 17:50:40.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:40.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:40.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:40.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:40.630: INFO: Jan 19 17:50:42.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:42.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:42.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (303 seconds elapsed) Jan 19 17:50:42.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:42.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:42.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:42.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:42.631: INFO: Jan 19 17:50:44.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:44.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:44.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (305 seconds elapsed) Jan 19 17:50:44.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:44.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:44.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:44.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:44.629: INFO: Jan 19 17:50:46.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:46.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:46.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (307 seconds elapsed) Jan 19 17:50:46.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:46.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:46.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:46.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:46.639: INFO: Jan 19 17:50:48.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:48.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:48.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (309 seconds elapsed) Jan 19 17:50:48.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:48.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:48.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:48.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:48.637: INFO: Jan 19 17:50:50.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:50.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:50.649: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (311 seconds elapsed) Jan 19 17:50:50.649: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:50.649: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:50.649: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:50.649: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:50.649: INFO: Jan 19 17:50:52.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:52.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:52.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (313 seconds elapsed) Jan 19 17:50:52.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:52.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:52.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:52.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:52.630: INFO: Jan 19 17:50:54.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:54.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:54.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (315 seconds elapsed) Jan 19 17:50:54.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:54.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:54.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:54.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:54.631: INFO: Jan 19 17:50:56.628: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:56.628: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:56.628: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (317 seconds elapsed) Jan 19 17:50:56.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:56.628: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:56.628: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:56.628: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:56.628: INFO: Jan 19 17:50:58.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:58.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:50:58.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (319 seconds elapsed) Jan 19 17:50:58.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:50:58.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:50:58.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:58.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:50:58.631: INFO: Jan 19 17:51:00.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:00.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:00.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (321 seconds elapsed) Jan 19 17:51:00.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:00.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:00.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:00.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:00.631: INFO: Jan 19 17:51:02.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:02.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:02.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (323 seconds elapsed) Jan 19 17:51:02.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:02.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:02.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:02.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:02.631: INFO: Jan 19 17:51:04.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:04.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:04.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (325 seconds elapsed) Jan 19 17:51:04.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:04.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:04.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:04.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:04.633: INFO: Jan 19 17:51:06.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:06.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:06.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (327 seconds elapsed) Jan 19 17:51:06.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:06.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:06.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:06.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:06.634: INFO: Jan 19 17:51:08.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:08.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:08.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (329 seconds elapsed) Jan 19 17:51:08.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:08.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:08.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:08.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:08.632: INFO: Jan 19 17:51:10.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:10.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:10.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (331 seconds elapsed) Jan 19 17:51:10.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:10.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:10.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:10.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:10.635: INFO: Jan 19 17:51:12.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:12.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:12.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (333 seconds elapsed) Jan 19 17:51:12.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:12.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:12.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:12.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:12.632: INFO: Jan 19 17:51:14.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:14.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:14.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (335 seconds elapsed) Jan 19 17:51:14.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:14.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:14.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:14.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:14.632: INFO: Jan 19 17:51:16.647: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:16.647: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:16.647: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (337 seconds elapsed) Jan 19 17:51:16.647: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:16.647: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:16.647: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:16.647: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:16.647: INFO: Jan 19 17:51:18.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:18.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:18.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (339 seconds elapsed) Jan 19 17:51:18.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:18.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:18.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:18.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:18.629: INFO: Jan 19 17:51:20.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:20.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:20.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (341 seconds elapsed) Jan 19 17:51:20.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:20.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:20.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:20.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:20.633: INFO: Jan 19 17:51:22.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:22.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:22.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (343 seconds elapsed) Jan 19 17:51:22.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:22.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:22.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:22.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:22.631: INFO: Jan 19 17:51:24.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:24.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:24.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (345 seconds elapsed) Jan 19 17:51:24.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:24.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:24.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:24.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:24.630: INFO: Jan 19 17:51:26.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:26.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:26.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (347 seconds elapsed) Jan 19 17:51:26.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:26.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:26.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:26.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:26.633: INFO: Jan 19 17:51:28.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:28.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:28.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (349 seconds elapsed) Jan 19 17:51:28.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:28.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:28.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:28.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:28.637: INFO: Jan 19 17:51:30.642: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:30.642: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:30.642: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (351 seconds elapsed) Jan 19 17:51:30.642: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:30.642: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:30.642: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:30.642: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:30.642: INFO: Jan 19 17:51:32.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:32.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:32.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (353 seconds elapsed) Jan 19 17:51:32.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:32.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:32.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:32.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:32.634: INFO: Jan 19 17:51:34.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:34.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:34.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (355 seconds elapsed) Jan 19 17:51:34.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:34.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:34.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:34.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:34.636: INFO: Jan 19 17:51:36.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:36.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:36.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (357 seconds elapsed) Jan 19 17:51:36.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:36.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:36.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:36.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:36.636: INFO: Jan 19 17:51:38.648: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:38.648: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:38.648: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (359 seconds elapsed) Jan 19 17:51:38.648: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:38.648: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:38.648: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:38.648: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:38.648: INFO: Jan 19 17:51:40.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:40.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:40.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (361 seconds elapsed) Jan 19 17:51:40.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:40.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:40.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:40.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:40.635: INFO: Jan 19 17:51:42.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:42.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:42.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (363 seconds elapsed) Jan 19 17:51:42.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:42.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:42.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:42.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:42.637: INFO: Jan 19 17:51:44.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:44.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:44.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (365 seconds elapsed) Jan 19 17:51:44.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:44.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:44.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:44.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:44.632: INFO: Jan 19 17:51:46.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:46.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:46.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (367 seconds elapsed) Jan 19 17:51:46.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:46.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:46.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:46.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:46.639: INFO: Jan 19 17:51:48.647: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:48.647: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:48.647: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (369 seconds elapsed) Jan 19 17:51:48.647: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:48.647: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:48.647: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:48.647: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:48.647: INFO: Jan 19 17:51:50.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:50.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:50.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (371 seconds elapsed) Jan 19 17:51:50.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:50.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:50.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:50.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:50.633: INFO: Jan 19 17:51:52.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:52.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:52.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (373 seconds elapsed) Jan 19 17:51:52.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:52.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:52.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:52.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:52.639: INFO: Jan 19 17:51:54.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:54.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:54.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (375 seconds elapsed) Jan 19 17:51:54.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:54.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:54.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:54.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:54.636: INFO: Jan 19 17:51:56.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:56.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:56.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (377 seconds elapsed) Jan 19 17:51:56.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:56.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:56.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:56.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:56.636: INFO: Jan 19 17:51:58.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:58.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:51:58.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (379 seconds elapsed) Jan 19 17:51:58.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:51:58.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:51:58.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:58.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:51:58.637: INFO: Jan 19 17:52:00.643: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:00.643: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:00.643: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (381 seconds elapsed) Jan 19 17:52:00.643: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:00.643: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:00.643: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:00.643: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:00.643: INFO: Jan 19 17:52:02.644: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:02.644: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:02.644: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (383 seconds elapsed) Jan 19 17:52:02.644: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:02.644: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:02.644: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:02.644: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:02.644: INFO: Jan 19 17:52:04.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:04.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:04.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (385 seconds elapsed) Jan 19 17:52:04.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:04.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:04.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:04.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:04.641: INFO: Jan 19 17:52:06.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:06.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:06.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (387 seconds elapsed) Jan 19 17:52:06.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:06.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:06.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:06.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:06.634: INFO: Jan 19 17:52:08.642: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:08.642: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:08.642: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (389 seconds elapsed) Jan 19 17:52:08.642: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:08.642: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:08.642: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:08.642: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:08.642: INFO: Jan 19 17:52:10.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:10.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:10.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (391 seconds elapsed) Jan 19 17:52:10.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:10.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:10.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:10.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:10.641: INFO: Jan 19 17:52:12.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:12.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:12.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (393 seconds elapsed) Jan 19 17:52:12.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:12.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:12.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:12.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:12.639: INFO: Jan 19 17:52:14.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:14.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:14.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (395 seconds elapsed) Jan 19 17:52:14.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:14.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:14.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:14.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:14.638: INFO: Jan 19 17:52:16.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:16.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:16.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (397 seconds elapsed) Jan 19 17:52:16.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:16.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:16.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:16.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:16.634: INFO: Jan 19 17:52:18.642: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:18.642: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:18.642: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (399 seconds elapsed) Jan 19 17:52:18.642: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:18.642: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:18.642: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:18.642: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:18.642: INFO: Jan 19 17:52:20.646: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:20.646: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:20.646: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (401 seconds elapsed) Jan 19 17:52:20.646: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:20.646: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:20.646: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:20.646: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:20.646: INFO: Jan 19 17:52:22.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:22.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:22.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (403 seconds elapsed) Jan 19 17:52:22.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:22.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:22.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:22.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:22.639: INFO: Jan 19 17:52:24.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:24.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:24.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (405 seconds elapsed) Jan 19 17:52:24.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:24.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:24.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:24.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:24.637: INFO: Jan 19 17:52:26.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:26.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:26.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (407 seconds elapsed) Jan 19 17:52:26.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:26.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:26.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:26.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:26.640: INFO: Jan 19 17:52:28.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:28.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:28.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (409 seconds elapsed) Jan 19 17:52:28.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:28.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:28.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:28.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:28.639: INFO: Jan 19 17:52:30.649: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:30.649: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:30.649: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (411 seconds elapsed) Jan 19 17:52:30.649: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:30.649: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:30.649: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:30.649: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:30.649: INFO: Jan 19 17:52:32.653: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:32.653: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:32.653: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (413 seconds elapsed) Jan 19 17:52:32.653: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:32.653: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:32.653: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:32.653: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:32.653: INFO: Jan 19 17:52:34.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:34.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:34.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (415 seconds elapsed) Jan 19 17:52:34.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:34.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:34.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:34.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:34.636: INFO: Jan 19 17:52:36.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:36.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:36.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (417 seconds elapsed) Jan 19 17:52:36.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:36.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:36.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:36.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:36.637: INFO: Jan 19 17:52:38.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:38.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:38.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (419 seconds elapsed) Jan 19 17:52:38.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:38.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:38.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:38.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:38.635: INFO: Jan 19 17:52:40.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:40.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:40.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (421 seconds elapsed) Jan 19 17:52:40.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:40.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:40.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:40.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:40.640: INFO: Jan 19 17:52:42.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:42.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:42.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (423 seconds elapsed) Jan 19 17:52:42.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:42.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:42.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:42.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:42.635: INFO: Jan 19 17:52:44.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:44.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:44.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (425 seconds elapsed) Jan 19 17:52:44.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:44.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:44.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:44.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:44.637: INFO: Jan 19 17:52:46.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:46.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:46.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (427 seconds elapsed) Jan 19 17:52:46.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:46.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:46.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:46.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:46.636: INFO: Jan 19 17:52:48.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:48.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:48.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (429 seconds elapsed) Jan 19 17:52:48.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:48.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:48.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:48.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:48.640: INFO: Jan 19 17:52:50.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:50.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:50.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (431 seconds elapsed) Jan 19 17:52:50.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:50.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:50.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:50.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:50.631: INFO: Jan 19 17:52:52.644: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:52.644: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:52.644: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (433 seconds elapsed) Jan 19 17:52:52.644: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:52.644: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:52.644: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:52.644: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:52.644: INFO: Jan 19 17:52:54.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:54.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:54.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (435 seconds elapsed) Jan 19 17:52:54.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:54.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:54.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:54.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:54.631: INFO: Jan 19 17:52:56.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:56.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:56.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (437 seconds elapsed) Jan 19 17:52:56.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:56.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:56.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:56.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:56.632: INFO: Jan 19 17:52:58.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:58.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:52:58.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (439 seconds elapsed) Jan 19 17:52:58.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:52:58.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:52:58.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:58.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:52:58.636: INFO: Jan 19 17:53:00.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:00.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:00.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (441 seconds elapsed) Jan 19 17:53:00.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:00.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:00.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:00.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:00.631: INFO: Jan 19 17:53:02.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:02.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:02.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (443 seconds elapsed) Jan 19 17:53:02.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:02.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:02.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:02.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:02.632: INFO: Jan 19 17:53:04.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:04.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:04.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (445 seconds elapsed) Jan 19 17:53:04.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:04.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:04.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:04.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:04.635: INFO: Jan 19 17:53:06.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:06.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:06.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (447 seconds elapsed) Jan 19 17:53:06.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:06.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:06.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:06.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:06.633: INFO: Jan 19 17:53:08.643: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:08.643: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:08.643: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (449 seconds elapsed) Jan 19 17:53:08.643: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:08.643: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:08.643: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:08.643: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:08.643: INFO: Jan 19 17:53:10.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:10.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:10.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (451 seconds elapsed) Jan 19 17:53:10.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:10.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:10.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:10.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:10.630: INFO: Jan 19 17:53:12.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:12.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:12.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (453 seconds elapsed) Jan 19 17:53:12.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:12.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:12.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:12.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:12.634: INFO: Jan 19 17:53:14.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:14.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:14.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (455 seconds elapsed) Jan 19 17:53:14.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:14.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:14.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:14.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:14.635: INFO: Jan 19 17:53:16.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:16.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:16.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (457 seconds elapsed) Jan 19 17:53:16.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:16.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:16.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:16.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:16.635: INFO: Jan 19 17:53:18.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:18.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:18.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (459 seconds elapsed) Jan 19 17:53:18.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:18.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:18.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:18.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:18.636: INFO: Jan 19 17:53:20.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:20.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:20.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (461 seconds elapsed) Jan 19 17:53:20.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:20.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:20.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:20.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:20.639: INFO: Jan 19 17:53:22.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:22.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:22.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (463 seconds elapsed) Jan 19 17:53:22.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:22.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:22.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:22.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:22.637: INFO: Jan 19 17:53:24.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:24.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:24.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (465 seconds elapsed) Jan 19 17:53:24.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:24.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:24.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:24.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:24.637: INFO: Jan 19 17:53:26.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:26.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:26.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (467 seconds elapsed) Jan 19 17:53:26.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:26.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:26.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:26.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:26.640: INFO: Jan 19 17:53:28.645: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:28.645: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:28.645: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (469 seconds elapsed) Jan 19 17:53:28.645: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:28.645: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:28.645: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:28.645: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:28.645: INFO: Jan 19 17:53:30.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:30.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:30.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (471 seconds elapsed) Jan 19 17:53:30.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:30.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:30.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:30.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:30.638: INFO: Jan 19 17:53:32.652: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:32.652: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:32.652: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (473 seconds elapsed) Jan 19 17:53:32.652: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:32.652: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:32.652: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:32.652: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:32.652: INFO: Jan 19 17:53:34.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:34.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:34.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (475 seconds elapsed) Jan 19 17:53:34.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:34.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:34.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:34.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:34.637: INFO: Jan 19 17:53:36.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:36.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:36.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (477 seconds elapsed) Jan 19 17:53:36.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:36.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:36.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:36.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:36.632: INFO: Jan 19 17:53:38.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:38.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:38.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (479 seconds elapsed) Jan 19 17:53:38.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:38.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:38.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:38.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:38.636: INFO: Jan 19 17:53:40.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:40.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:40.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (481 seconds elapsed) Jan 19 17:53:40.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:40.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:40.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:40.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:40.635: INFO: Jan 19 17:53:42.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:42.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:42.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (483 seconds elapsed) Jan 19 17:53:42.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:42.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:42.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:42.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:42.641: INFO: Jan 19 17:53:44.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:44.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:44.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (485 seconds elapsed) Jan 19 17:53:44.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:44.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:44.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:44.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:44.634: INFO: Jan 19 17:53:46.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:46.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:46.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (487 seconds elapsed) Jan 19 17:53:46.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:46.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:46.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:46.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:46.641: INFO: Jan 19 17:53:48.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:48.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:48.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (489 seconds elapsed) Jan 19 17:53:48.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:48.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:48.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:48.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:48.636: INFO: Jan 19 17:53:50.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:50.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:50.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (491 seconds elapsed) Jan 19 17:53:50.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:50.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:50.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:50.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:50.637: INFO: Jan 19 17:53:52.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:52.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:52.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (493 seconds elapsed) Jan 19 17:53:52.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:52.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:52.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:52.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:52.641: INFO: Jan 19 17:53:54.647: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:54.647: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:54.647: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (495 seconds elapsed) Jan 19 17:53:54.647: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:54.647: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:54.647: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:54.647: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:54.647: INFO: Jan 19 17:53:56.640: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:56.640: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:56.640: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (497 seconds elapsed) Jan 19 17:53:56.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:56.640: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:56.640: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:56.640: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:56.640: INFO: Jan 19 17:53:58.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:58.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:53:58.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (499 seconds elapsed) Jan 19 17:53:58.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:53:58.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:53:58.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:58.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:53:58.638: INFO: Jan 19 17:54:00.636: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:00.636: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:00.636: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (501 seconds elapsed) Jan 19 17:54:00.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:00.636: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:00.636: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:00.636: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:00.636: INFO: Jan 19 17:54:02.642: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:02.642: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:02.642: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (503 seconds elapsed) Jan 19 17:54:02.642: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:02.642: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:02.642: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:02.642: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:02.642: INFO: Jan 19 17:54:04.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:04.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:04.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (505 seconds elapsed) Jan 19 17:54:04.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:04.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:04.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:04.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:04.635: INFO: Jan 19 17:54:06.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:06.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:06.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (507 seconds elapsed) Jan 19 17:54:06.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:06.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:06.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:06.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:06.635: INFO: Jan 19 17:54:08.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:08.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:08.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (509 seconds elapsed) Jan 19 17:54:08.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:08.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:08.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:08.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:08.638: INFO: Jan 19 17:54:10.639: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:10.639: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:10.639: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (511 seconds elapsed) Jan 19 17:54:10.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:10.639: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:10.639: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:10.639: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:10.639: INFO: Jan 19 17:54:12.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:12.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:12.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (513 seconds elapsed) Jan 19 17:54:12.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:12.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:12.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:12.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:12.631: INFO: Jan 19 17:54:14.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:14.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:14.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (515 seconds elapsed) Jan 19 17:54:14.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:14.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:14.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:14.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:14.630: INFO: Jan 19 17:54:16.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:16.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:16.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (517 seconds elapsed) Jan 19 17:54:16.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:16.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:16.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:16.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:16.633: INFO: Jan 19 17:54:18.641: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:18.641: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:18.641: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (519 seconds elapsed) Jan 19 17:54:18.641: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:18.641: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:18.641: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:18.641: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:18.641: INFO: Jan 19 17:54:20.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:20.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:20.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (521 seconds elapsed) Jan 19 17:54:20.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:20.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:20.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:20.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:20.635: INFO: Jan 19 17:54:22.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:22.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:22.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (523 seconds elapsed) Jan 19 17:54:22.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:22.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:22.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:22.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:22.633: INFO: Jan 19 17:54:24.827: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:24.827: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:24.827: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (525 seconds elapsed) Jan 19 17:54:24.827: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:24.827: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:24.827: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:24.827: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:24.827: INFO: Jan 19 17:54:26.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:26.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:26.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (527 seconds elapsed) Jan 19 17:54:26.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:26.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:26.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:26.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:26.631: INFO: Jan 19 17:54:28.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:28.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:28.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (529 seconds elapsed) Jan 19 17:54:28.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:28.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:28.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:28.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:28.629: INFO: Jan 19 17:54:30.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:30.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:30.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (531 seconds elapsed) Jan 19 17:54:30.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:30.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:30.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:30.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:30.631: INFO: Jan 19 17:54:32.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:32.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:32.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (533 seconds elapsed) Jan 19 17:54:32.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:32.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:32.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:32.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:32.632: INFO: Jan 19 17:54:34.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:34.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:34.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (535 seconds elapsed) Jan 19 17:54:34.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:34.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:34.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:34.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:34.629: INFO: Jan 19 17:54:36.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:36.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:36.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (537 seconds elapsed) Jan 19 17:54:36.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:36.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:36.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:36.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:36.632: INFO: Jan 19 17:54:38.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:38.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:38.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (539 seconds elapsed) Jan 19 17:54:38.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:38.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:38.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:38.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:38.631: INFO: Jan 19 17:54:40.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:40.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:40.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (541 seconds elapsed) Jan 19 17:54:40.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:40.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:40.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:40.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:40.630: INFO: Jan 19 17:54:42.628: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:42.628: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:42.628: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (543 seconds elapsed) Jan 19 17:54:42.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:42.628: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:42.628: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:42.628: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:42.628: INFO: Jan 19 17:54:44.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:44.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:44.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (545 seconds elapsed) Jan 19 17:54:44.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:44.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:44.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:44.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:44.630: INFO: Jan 19 17:54:46.635: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:46.635: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:46.635: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (547 seconds elapsed) Jan 19 17:54:46.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:46.635: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:46.635: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:46.635: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:46.635: INFO: Jan 19 17:54:48.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:48.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:48.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (549 seconds elapsed) Jan 19 17:54:48.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:48.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:48.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:48.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:48.631: INFO: Jan 19 17:54:50.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:50.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:50.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (551 seconds elapsed) Jan 19 17:54:50.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:50.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:50.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:50.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:50.633: INFO: Jan 19 17:54:52.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:52.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:52.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (553 seconds elapsed) Jan 19 17:54:52.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:52.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:52.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:52.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:52.632: INFO: Jan 19 17:54:54.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:54.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:54.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (555 seconds elapsed) Jan 19 17:54:54.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:54.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:54.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:54.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:54.630: INFO: Jan 19 17:54:56.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:56.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:56.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (557 seconds elapsed) Jan 19 17:54:56.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:56.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:56.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:56.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:56.633: INFO: Jan 19 17:54:58.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:58.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:54:58.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (559 seconds elapsed) Jan 19 17:54:58.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:54:58.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:54:58.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:58.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:54:58.629: INFO: Jan 19 17:55:00.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:00.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:00.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (561 seconds elapsed) Jan 19 17:55:00.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:00.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:00.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:00.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:00.634: INFO: Jan 19 17:55:02.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:02.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:02.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (563 seconds elapsed) Jan 19 17:55:02.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:02.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:02.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:02.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:02.632: INFO: Jan 19 17:55:04.645: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:04.645: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:04.645: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (565 seconds elapsed) Jan 19 17:55:04.645: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:04.645: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:04.645: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:04.645: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:04.645: INFO: Jan 19 17:55:06.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:06.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:06.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (567 seconds elapsed) Jan 19 17:55:06.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:06.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:06.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:06.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:06.630: INFO: Jan 19 17:55:08.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:08.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:08.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (569 seconds elapsed) Jan 19 17:55:08.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:08.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:08.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:08.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:08.629: INFO: Jan 19 17:55:10.638: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:10.638: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:10.638: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (571 seconds elapsed) Jan 19 17:55:10.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:10.638: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:10.638: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:10.638: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:10.638: INFO: Jan 19 17:55:12.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:12.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:12.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (573 seconds elapsed) Jan 19 17:55:12.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:12.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:12.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:12.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:12.629: INFO: Jan 19 17:55:14.628: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:14.628: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:14.628: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (575 seconds elapsed) Jan 19 17:55:14.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:14.628: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:14.628: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:14.628: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:14.628: INFO: Jan 19 17:55:16.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:16.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:16.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (577 seconds elapsed) Jan 19 17:55:16.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:16.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:16.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:16.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:16.633: INFO: Jan 19 17:55:18.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:18.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:18.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (579 seconds elapsed) Jan 19 17:55:18.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:18.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:18.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:18.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:18.630: INFO: Jan 19 17:55:20.633: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:20.633: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:20.633: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (581 seconds elapsed) Jan 19 17:55:20.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:20.633: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:20.633: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:20.633: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:20.633: INFO: Jan 19 17:55:22.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:22.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:22.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (583 seconds elapsed) Jan 19 17:55:22.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:22.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:22.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:22.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:22.629: INFO: Jan 19 17:55:24.634: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:24.634: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:24.634: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (585 seconds elapsed) Jan 19 17:55:24.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:24.634: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:24.634: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:24.634: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:24.634: INFO: Jan 19 17:55:26.632: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:26.632: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:26.632: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (587 seconds elapsed) Jan 19 17:55:26.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:26.632: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:26.632: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:26.632: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:26.632: INFO: Jan 19 17:55:28.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:28.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:28.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (589 seconds elapsed) Jan 19 17:55:28.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:28.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:28.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:28.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:28.629: INFO: Jan 19 17:55:30.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:30.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:30.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (591 seconds elapsed) Jan 19 17:55:30.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:30.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:30.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:30.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:30.637: INFO: Jan 19 17:55:32.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:32.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:32.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (593 seconds elapsed) Jan 19 17:55:32.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:32.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:32.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:32.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:32.629: INFO: Jan 19 17:55:34.630: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:34.630: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:34.630: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (595 seconds elapsed) Jan 19 17:55:34.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:34.630: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:34.630: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:34.630: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:34.630: INFO: Jan 19 17:55:36.631: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:36.631: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:36.631: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (597 seconds elapsed) Jan 19 17:55:36.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:36.631: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:36.631: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:36.631: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:36.631: INFO: Jan 19 17:55:38.637: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:38.637: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:38.637: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (599 seconds elapsed) Jan 19 17:55:38.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:38.637: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:38.637: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:38.637: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:38.637: INFO: Jan 19 17:55:40.629: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:40.629: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:40.629: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (601 seconds elapsed) Jan 19 17:55:40.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:40.629: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:40.629: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:40.629: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:40.629: INFO: Jan 19 17:55:41.071: INFO: The status of Pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:41.071: INFO: The status of Pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 19 17:55:41.071: INFO: 12 / 14 pods in namespace 'kube-system' are running and ready (601 seconds elapsed) Jan 19 17:55:41.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 19 17:55:41.071: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:41.071: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:41.071: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:41.071: INFO: STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/19/23 17:55:41.071 STEP: Found 97 events. - test/e2e/framework/debug/dump.go:46 @ 01/19/23 17:55:41.227 Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:12 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-b9w8m3-control-plane-p2gps_9c358dc7-f1cd-432a-82be-587dd81ed13b became leader Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:14 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-b9w8m3-control-plane-p2gps_38b55405-bf35-4c82-8bf9-cf53915f937b became leader Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:18 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2 Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:18 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-wc4dr Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:18 +0000 UTC - event for kube-proxy-wc4dr: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-wc4dr to capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:19 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-wbxsm Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:19 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-6v6j8 Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:19 +0000 UTC - event for coredns-56f4c55bf9-6v6j8: {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 19 17:55:41.227: INFO: At 2023-01-19 17:43:19 +0000 UTC - event for coredns-56f4c55bf9-wbxsm: {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 19 17:55:41.227: INFO: At 2023-01-19 17:43:19 +0000 UTC - event for kube-proxy-wc4dr: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:23 +0000 UTC - event for kube-proxy-wc4dr: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Created: Created container kube-proxy Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:23 +0000 UTC - event for kube-proxy-wc4dr: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7" in 4.215854709s (4.215861809s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:24 +0000 UTC - event for kube-proxy-wc4dr: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Started: Started container kube-proxy Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:27 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:27 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-jpdxx Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:27 +0000 UTC - event for metrics-server-c9574f845-jpdxx: {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 19 17:55:41.227: INFO: At 2023-01-19 17:43:30 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1 Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:30 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-h8qzj Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:30 +0000 UTC - event for calico-kube-controllers-657b584867-h8qzj: {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 19 17:55:41.227: INFO: At 2023-01-19 17:43:30 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-nx9bl Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:30 +0000 UTC - event for calico-node-nx9bl: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-nx9bl to capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:31 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:39 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 8.53816056s (8.53819486s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:39 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Created: Created container upgrade-ipam Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:39 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Started: Started container upgrade-ipam Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:42 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:42 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Created: Created container install-cni Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:43 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Started: Started container install-cni Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:45 +0000 UTC - event for calico-kube-controllers-657b584867-h8qzj: {kubelet capz-conf-b9w8m3-control-plane-p2gps} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0f0e54f2f251d63fb9595fede87b2d1ab7fcb05d2e139aba4e9935946bae08fe": 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 19 17:55:41.227: INFO: At 2023-01-19 17:43:45 +0000 UTC - event for calico-kube-controllers-657b584867-h8qzj: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-h8qzj to capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:45 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:45 +0000 UTC - event for coredns-56f4c55bf9-6v6j8: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-6v6j8 to capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:45 +0000 UTC - event for coredns-56f4c55bf9-wbxsm: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-wbxsm to capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:45 +0000 UTC - event for coredns-56f4c55bf9-wbxsm: {kubelet capz-conf-b9w8m3-control-plane-p2gps} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0029b1c59aabad60da1b251dd38be1329d96d416bdb5ca8fa2bc6deeb1d288e6": 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 19 17:55:41.227: INFO: At 2023-01-19 17:43:45 +0000 UTC - event for metrics-server-c9574f845-jpdxx: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-jpdxx to capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:46 +0000 UTC - event for coredns-56f4c55bf9-6v6j8: {kubelet capz-conf-b9w8m3-control-plane-p2gps} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0d3bf4137dbabfe6e4149225089cb932546ce3cc0f3b106d0b32882fb42a1c66": 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 19 17:55:41.227: INFO: At 2023-01-19 17:43:46 +0000 UTC - event for metrics-server-c9574f845-jpdxx: {kubelet capz-conf-b9w8m3-control-plane-p2gps} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "cc180589ca6508e23d125e2b27dd406f5d463b595fadf27fcf52787926e894e3": 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 19 17:55:41.227: INFO: At 2023-01-19 17:43:56 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Created: Created container calico-node Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:56 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Started: Started container calico-node Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:56 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} 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 19 17:55:41.227: INFO: At 2023-01-19 17:43:56 +0000 UTC - event for calico-node-nx9bl: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 10.246713448s (10.246726148s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:43:58 +0000 UTC - event for calico-kube-controllers-657b584867-h8qzj: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:00 +0000 UTC - event for coredns-56f4c55bf9-wbxsm: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:01 +0000 UTC - event for coredns-56f4c55bf9-6v6j8: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:01 +0000 UTC - event for coredns-56f4c55bf9-6v6j8: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Created: Created container coredns Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:01 +0000 UTC - event for coredns-56f4c55bf9-wbxsm: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Created: Created container coredns Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:01 +0000 UTC - event for coredns-56f4c55bf9-wbxsm: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Started: Started container coredns Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:01 +0000 UTC - event for metrics-server-c9574f845-jpdxx: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:02 +0000 UTC - event for coredns-56f4c55bf9-6v6j8: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Started: Started container coredns Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:07 +0000 UTC - event for calico-kube-controllers-657b584867-h8qzj: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 8.374255309s (8.374372208s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:07 +0000 UTC - event for calico-kube-controllers-657b584867-h8qzj: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Created: Created container calico-kube-controllers Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:07 +0000 UTC - event for calico-kube-controllers-657b584867-h8qzj: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Started: Started container calico-kube-controllers Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:11 +0000 UTC - event for metrics-server-c9574f845-jpdxx: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.834238055s (10.582616456s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:12 +0000 UTC - event for metrics-server-c9574f845-jpdxx: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Created: Created container metrics-server Jan 19 17:55:41.227: INFO: At 2023-01-19 17:44:12 +0000 UTC - event for metrics-server-c9574f845-jpdxx: {kubelet capz-conf-b9w8m3-control-plane-p2gps} Started: Started container metrics-server Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:01 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-5fj2p Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:01 +0000 UTC - event for calico-node-5fj2p: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-5fj2p to capz-conf-b9w8m3-md-0-xfjrf Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:01 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-76gdr Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:01 +0000 UTC - event for kube-proxy-76gdr: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-76gdr to capz-conf-b9w8m3-md-0-xfjrf Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:06 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-l2rd6 Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:06 +0000 UTC - event for calico-node-l2rd6: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-l2rd6 to capz-conf-b9w8m3-md-0-p2z5x Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:06 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-2wbqm Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:06 +0000 UTC - event for kube-proxy-2wbqm: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-2wbqm to capz-conf-b9w8m3-md-0-p2z5x Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:14 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:14 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:14 +0000 UTC - event for kube-proxy-2wbqm: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:14 +0000 UTC - event for kube-proxy-76gdr: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:21 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Created: Created container upgrade-ipam Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:21 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.644364814s (6.644416216s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:21 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Started: Started container upgrade-ipam Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:21 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Created: Created container upgrade-ipam Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:21 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Started: Started container upgrade-ipam Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:21 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.026441653s (7.026530155s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:23 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:23 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Created: Created container install-cni Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:23 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Started: Started container install-cni Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:24 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:25 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Started: Started container install-cni Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:25 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Created: Created container install-cni Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:28 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:28 +0000 UTC - event for kube-proxy-2wbqm: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7" in 7.170464195s (14.184164478s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:28 +0000 UTC - event for kube-proxy-76gdr: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Started: Started container kube-proxy Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:28 +0000 UTC - event for kube-proxy-76gdr: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7" in 7.546894453s (14.158519459s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:28 +0000 UTC - event for kube-proxy-76gdr: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Created: Created container kube-proxy Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:29 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:29 +0000 UTC - event for kube-proxy-2wbqm: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Started: Started container kube-proxy Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:29 +0000 UTC - event for kube-proxy-2wbqm: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Created: Created container kube-proxy Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:37 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Started: Started container calico-node Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:37 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Created: Created container calico-node Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:37 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.111995397s (9.112009698s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:38 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} 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 19 17:55:41.227: INFO: At 2023-01-19 17:45:38 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.140173733s (9.140188533s including waiting) Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:38 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Created: Created container calico-node Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:39 +0000 UTC - event for calico-node-5fj2p: {kubelet capz-conf-b9w8m3-md-0-xfjrf} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:39 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Started: Started container calico-node Jan 19 17:55:41.227: INFO: At 2023-01-19 17:45:39 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} 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 19 17:55:41.227: INFO: At 2023-01-19 17:45:40 +0000 UTC - event for calico-node-l2rd6: {kubelet capz-conf-b9w8m3-md-0-p2z5x} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Jan 19 17:55:41.392: INFO: POD NODE PHASE GRACE CONDITIONS Jan 19 17:55:41.392: INFO: calico-kube-controllers-657b584867-h8qzj capz-conf-b9w8m3-control-plane-p2gps Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:07 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:07 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC }] Jan 19 17:55:41.392: INFO: calico-node-5fj2p capz-conf-b9w8m3-md-0-xfjrf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:28 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:40 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:40 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:01 +0000 UTC }] Jan 19 17:55:41.392: INFO: calico-node-l2rd6 capz-conf-b9w8m3-md-0-p2z5x Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:29 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:41 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:41 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:06 +0000 UTC }] Jan 19 17:55:41.392: INFO: calico-node-nx9bl capz-conf-b9w8m3-control-plane-p2gps Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:01 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:01 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:30 +0000 UTC }] Jan 19 17:55:41.392: INFO: coredns-56f4c55bf9-6v6j8 capz-conf-b9w8m3-control-plane-p2gps Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:02 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:02 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC }] Jan 19 17:55:41.392: INFO: coredns-56f4c55bf9-wbxsm capz-conf-b9w8m3-control-plane-p2gps Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:02 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:02 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC }] Jan 19 17:55:41.392: INFO: etcd-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:14 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:14 +0000 UTC }] Jan 19 17:55:41.392: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:41.392: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] Jan 19 17:55:41.392: INFO: kube-proxy-2wbqm capz-conf-b9w8m3-md-0-p2z5x Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:10 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:06 +0000 UTC }] Jan 19 17:55:41.392: INFO: kube-proxy-76gdr capz-conf-b9w8m3-md-0-xfjrf Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:09 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:45:01 +0000 UTC }] Jan 19 17:55:41.392: INFO: kube-proxy-wc4dr capz-conf-b9w8m3-control-plane-p2gps Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:18 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:18 +0000 UTC }] Jan 19 17:55:41.392: INFO: kube-scheduler-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:42:51 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:42:51 +0000 UTC }] Jan 19 17:55:41.393: INFO: metrics-server-c9574f845-jpdxx capz-conf-b9w8m3-control-plane-p2gps Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:36 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:44:36 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-19 17:43:45 +0000 UTC }] Jan 19 17:55:41.393: INFO: Jan 19 17:55:42.083: INFO: Logging node info for node capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:42.193: INFO: Node Info: &Node{ObjectMeta:{capz-conf-b9w8m3-control-plane-p2gps 8321e48e-c860-462f-9edf-244b8f39bf9c 1709 0 2023-01-19 17:43:10 +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-2 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-b9w8m3-control-plane-p2gps 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-2] map[cluster.x-k8s.io/cluster-name:capz-conf-b9w8m3 cluster.x-k8s.io/cluster-namespace:capz-conf-b9w8m3 cluster.x-k8s.io/machine:capz-conf-b9w8m3-control-plane-j75hn cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-b9w8m3-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.147.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-19 17:43:09 +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-19 17:43:13 +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-19 17:43:24 +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-19 17:43:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2023-01-19 17:43:56 +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-19 17:54: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-b9w8m3/providers/Microsoft.Compute/virtualMachines/capz-conf-b9w8m3-control-plane-p2gps,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/control-plane,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8344743936 0} {<nil>} 8149164Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-19 17:43:56 +0000 UTC,LastTransitionTime:2023-01-19 17:43:56 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-19 17:54:29 +0000 UTC,LastTransitionTime:2023-01-19 17:42:51 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-19 17:54:29 +0000 UTC,LastTransitionTime:2023-01-19 17:42:51 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-19 17:54:29 +0000 UTC,LastTransitionTime:2023-01-19 17:42:51 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-19 17:54:29 +0000 UTC,LastTransitionTime:2023-01-19 17:43:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-b9w8m3-control-plane-p2gps,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:633fa43964a54c3e9cc5ca61c759fce6,SystemUUID:c4ce7661-192e-8144-86c7-dff109a5da6b,BootID:d7b8d22f-ac09-4321-91d6-477d4138d016,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1114+8dbb4f6507ccc7,KubeProxyVersion:v1.27.0-alpha.0.1114+8dbb4f6507ccc7,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:9a9ec6a2a1fbd085d78473d435e6e930731bd6d633b2de6197e3bb751c2428d0 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.1103_1ca2180f300bb8],SizeBytes:35458081,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:a7a702b08b4feb2f95224d85c40fd353583d6b283f77f43da1c2016d6405be46 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.1103_1ca2180f300bb8],SizeBytes:32314211,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:5f35ea8930e886caba0542e5e64e241ac15fede2b8c093871d61739840ed3f9e capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7],SizeBytes:21490916,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:6fefe9fa59359f89bdd14e3872c62239fc7b98637e931677e13abaf3b5784ebd gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.1103_1ca2180f300bb8],SizeBytes:21482259,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:d5d4bd9d97a5c8993476ac52a0e05ab3652bc12c300b92d9f8b18c53d7c17017 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.1103_1ca2180f300bb8],SizeBytes:17470581,},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 19 17:55:42.193: INFO: Logging kubelet events for node capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:42.300: INFO: Logging pods the kubelet thinks is on node capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:42.436: INFO: calico-node-nx9bl started at 2023-01-19 17:43:30 +0000 UTC (2+1 container statuses recorded) Jan 19 17:55:42.436: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 19 17:55:42.436: INFO: Init container install-cni ready: true, restart count 0 Jan 19 17:55:42.436: INFO: Container calico-node ready: true, restart count 0 Jan 19 17:55:42.436: INFO: coredns-56f4c55bf9-6v6j8 started at 2023-01-19 17:43:45 +0000 UTC (0+1 container statuses recorded) Jan 19 17:55:42.436: INFO: Container coredns ready: true, restart count 0 Jan 19 17:55:42.436: INFO: metrics-server-c9574f845-jpdxx started at 2023-01-19 17:43:45 +0000 UTC (0+1 container statuses recorded) Jan 19 17:55:42.436: INFO: Container metrics-server ready: true, restart count 0 Jan 19 17:55:42.436: INFO: kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps started at <nil> (0+0 container statuses recorded) Jan 19 17:55:42.436: INFO: kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps started at <nil> (0+0 container statuses recorded) Jan 19 17:55:42.436: INFO: kube-scheduler-capz-conf-b9w8m3-control-plane-p2gps started at <nil> (0+0 container statuses recorded) Jan 19 17:55:42.436: INFO: kube-proxy-wc4dr started at 2023-01-19 17:43:18 +0000 UTC (0+1 container statuses recorded) Jan 19 17:55:42.436: INFO: Container kube-proxy ready: true, restart count 0 Jan 19 17:55:42.436: INFO: coredns-56f4c55bf9-wbxsm started at 2023-01-19 17:43:45 +0000 UTC (0+1 container statuses recorded) Jan 19 17:55:42.436: INFO: Container coredns ready: true, restart count 0 Jan 19 17:55:42.436: INFO: calico-kube-controllers-657b584867-h8qzj started at 2023-01-19 17:43:45 +0000 UTC (0+1 container statuses recorded) Jan 19 17:55:42.436: INFO: Container calico-kube-controllers ready: true, restart count 0 Jan 19 17:55:42.436: INFO: etcd-capz-conf-b9w8m3-control-plane-p2gps started at 2023-01-19 17:43:14 +0000 UTC (0+1 container statuses recorded) Jan 19 17:55:42.436: INFO: Container etcd ready: true, restart count 0 Jan 19 17:55:42.901: INFO: Latency metrics for node capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:42.901: INFO: Logging node info for node capz-conf-b9w8m3-md-0-p2z5x Jan 19 17:55:43.008: INFO: Node Info: &Node{ObjectMeta:{capz-conf-b9w8m3-md-0-p2z5x 3e239dc3-e01a-40a2-8f73-8615aa25e2af 1399 0 2023-01-19 17:45:06 +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-b9w8m3-md-0-p2z5x 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-b9w8m3 cluster.x-k8s.io/cluster-namespace:capz-conf-b9w8m3 cluster.x-k8s.io/machine:capz-conf-b9w8m3-md-0-5888fff6f-tclt2 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-b9w8m3-md-0-5888fff6f 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.159.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-19 17:45:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-19 17:45:06 +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-19 17:45:19 +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-19 17:45:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-19 17:45:39 +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-19 17:51:03 +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-b9w8m3/providers/Microsoft.Compute/virtualMachines/capz-conf-b9w8m3-md-0-p2z5x,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8344743936 0} {<nil>} 8149164Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-19 17:45:39 +0000 UTC,LastTransitionTime:2023-01-19 17:45:39 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-19 17:51:03 +0000 UTC,LastTransitionTime:2023-01-19 17:45:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-19 17:51:03 +0000 UTC,LastTransitionTime:2023-01-19 17:45:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-19 17:51:03 +0000 UTC,LastTransitionTime:2023-01-19 17:45:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-19 17:51:03 +0000 UTC,LastTransitionTime:2023-01-19 17:45:28 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-b9w8m3-md-0-p2z5x,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:2514cf6b9ebd4356bcb11928c4ce8087,SystemUUID:743b66d9-9e85-c745-86fc-2654f3a3fd58,BootID:5ab31fd2-5738-4b0d-95c7-db19004ddcf6,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1114+8dbb4f6507ccc7,KubeProxyVersion:v1.27.0-alpha.0.1114+8dbb4f6507ccc7,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:5f35ea8930e886caba0542e5e64e241ac15fede2b8c093871d61739840ed3f9e capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7],SizeBytes:21490916,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 19 17:55:43.008: INFO: Logging kubelet events for node capz-conf-b9w8m3-md-0-p2z5x Jan 19 17:55:43.114: INFO: Logging pods the kubelet thinks is on node capz-conf-b9w8m3-md-0-p2z5x Jan 19 17:55:43.229: INFO: calico-node-l2rd6 started at 2023-01-19 17:45:10 +0000 UTC (2+1 container statuses recorded) Jan 19 17:55:43.229: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 19 17:55:43.229: INFO: Init container install-cni ready: true, restart count 0 Jan 19 17:55:43.229: INFO: Container calico-node ready: true, restart count 0 Jan 19 17:55:43.229: INFO: kube-proxy-2wbqm started at 2023-01-19 17:45:10 +0000 UTC (0+1 container statuses recorded) Jan 19 17:55:43.229: INFO: Container kube-proxy ready: true, restart count 0 Jan 19 17:55:43.636: INFO: Latency metrics for node capz-conf-b9w8m3-md-0-p2z5x Jan 19 17:55:43.636: INFO: Logging node info for node capz-conf-b9w8m3-md-0-xfjrf Jan 19 17:55:43.743: INFO: Node Info: &Node{ObjectMeta:{capz-conf-b9w8m3-md-0-xfjrf c241c594-a795-4456-bdab-cd3d4019d2f9 1391 0 2023-01-19 17:45:01 +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-b9w8m3-md-0-xfjrf 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-b9w8m3 cluster.x-k8s.io/cluster-namespace:capz-conf-b9w8m3 cluster.x-k8s.io/machine:capz-conf-b9w8m3-md-0-5888fff6f-cvxnq cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-b9w8m3-md-0-5888fff6f 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.17.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-19 17:45:01 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-19 17:45:01 +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-19 17:45:18 +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-19 17:45:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-19 17:45:38 +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-19 17:50:58 +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-b9w8m3/providers/Microsoft.Compute/virtualMachines/capz-conf-b9w8m3-md-0-xfjrf,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8344743936 0} {<nil>} 8149164Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-19 17:45:38 +0000 UTC,LastTransitionTime:2023-01-19 17:45:38 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-19 17:50:58 +0000 UTC,LastTransitionTime:2023-01-19 17:45:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-19 17:50:58 +0000 UTC,LastTransitionTime:2023-01-19 17:45:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-19 17:50:58 +0000 UTC,LastTransitionTime:2023-01-19 17:45:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-19 17:50:58 +0000 UTC,LastTransitionTime:2023-01-19 17:45:28 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-b9w8m3-md-0-xfjrf,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:2bb86ff40fc743deb5c05fdefdf92be6,SystemUUID:fd848d03-6047-014a-a52e-ad64b82b3f12,BootID:ddd752ea-3ef1-441a-92b1-a0c0a27c2384,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1114+8dbb4f6507ccc7,KubeProxyVersion:v1.27.0-alpha.0.1114+8dbb4f6507ccc7,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:5f35ea8930e886caba0542e5e64e241ac15fede2b8c093871d61739840ed3f9e capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1114_8dbb4f6507ccc7],SizeBytes:21490916,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 19 17:55:43.743: INFO: Logging kubelet events for node capz-conf-b9w8m3-md-0-xfjrf Jan 19 17:55:43.850: INFO: Logging pods the kubelet thinks is on node capz-conf-b9w8m3-md-0-xfjrf Jan 19 17:55:43.967: INFO: kube-proxy-76gdr started at 2023-01-19 17:45:09 +0000 UTC (0+1 container statuses recorded) Jan 19 17:55:43.967: INFO: Container kube-proxy ready: true, restart count 0 Jan 19 17:55:43.967: INFO: calico-node-5fj2p started at 2023-01-19 17:45:09 +0000 UTC (2+1 container statuses recorded) Jan 19 17:55:43.967: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 19 17:55:43.967: INFO: Init container install-cni ready: true, restart count 0 Jan 19 17:55:43.967: INFO: Container calico-node ready: true, restart count 0 Jan 19 17:55:44.435: INFO: Latency metrics for node capz-conf-b9w8m3-md-0-xfjrf Jan 19 17:55:44.663: INFO: Running kubectl logs on non-ready containers in kube-system Jan 19 17:55:45.006: INFO: Failed to get logs of pod kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps) Jan 19 17:55:45.006: INFO: Logs of kube-system/kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps:kube-apiserver on node capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:45.006: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps:kube-apiserver Jan 19 17:55:45.397: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps) Jan 19 17:55:45.397: INFO: Logs of kube-system/kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps:kube-controller-manager on node capz-conf-b9w8m3-control-plane-p2gps Jan 19 17:55:45.397: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps:kube-controller-manager [FAILED] Error waiting for all pods to be running and ready: 2 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s POD NODE PHASE GRACE CONDITIONS kube-apiserver-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] kube-controller-manager-capz-conf-b9w8m3-control-plane-p2gps capz-conf-b9w8m3-control-plane-p2gps Pending [] In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/19/23 17:55:45.398 < Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/19/23 17:55:45.398 (10m6.445s)
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/19/23 17:55:45.462from 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/19/23 17:55:45.462
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/19/23 17:55:45.453from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.453
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.452from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.452
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/19/23 17:55:45.462from 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/19/23 17:55:45.462
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/19/23 17:55:45.463from 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/19/23 17:55:45.463
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/19/23 17:55:45.468from 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/19/23 17:55:45.468
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